Promoted on Friday, managing on Monday: the first 90 days
Your best engineer now runs the team and nobody told them how. What the first ninety days should actually contain, and what the business owes them.
Read the articleGanesh HS ·
A sales head interviewed nine candidates for two roles and picked the two he described as obvious. Both left inside eight months. Asked afterwards what had stood out about them, he said they were sharp, they got it, and he had known within ten minutes. He had thirty years of experience and a genuine instinct for people, and he had just made two expensive mistakes in a row.
The uncomfortable finding, consistent across decades of research and every business that has bothered to look at its own data, is that confidence in an interview judgement has almost no relationship to its accuracy. Experienced interviewers are more confident. They are not reliably more correct.
An interview with no fixed questions, where the conversation goes wherever it goes, measures something real. It is just not the thing anybody intends to measure.
None of this makes interviewers bad people. It makes them people. The point of structure is not to distrust the interviewer; it is to give a normal human judgement something reliable to work on.
1 SAME QUESTIONS, SAME ORDER, EVERY CANDIDATE
Four to six questions tied to the role. Follow-ups
can vary; the core questions do not.
2 AGREED RATING SCALE, WRITTEN BEFORE YOU START
What a 1 sounds like, what a 3 sounds like, what a 5
sounds like - in words, for each question.
3 SCORE INDEPENDENTLY, THEN DISCUSS
Each interviewer writes their scores before anyone
speaks. Non-negotiable.
4 EVIDENCE, NOT IMPRESSION
A score has a note attached saying what the candidate
said that produced it.That is the entire method. It is not sophisticated, it takes about two hours to set up for a role — which is the practical core of what interviewing skills for managers training covers, and it reliably outperforms the instinct of someone who has been hiring for three decades. The resistance it meets is almost never about efficacy — it is about the implication that experience is not enough.
Of the four parts, the third is the one businesses skip and the one that carries the most weight.
In an ordinary debrief, the most senior person speaks first. Everyone else's view then adjusts, mostly unconsciously, and the panel arrives at a consensus that feels robust and is in fact one person's opinion with three signatures on it. If the senior person is right, the panel added nothing; if they are wrong, the panel added nothing and removed the check.
Writing scores down before the discussion costs ninety seconds and preserves the disagreement. Disagreement is the useful part — two interviewers who scored the same answer 2 and 5 have heard different things, and finding out why is where the real information is.
The best predictor available in an interview is a specific account of something the candidate has actually done, probed for detail. Hypotheticals — what would you do if — measure how well someone reasons about a situation they are not in, which is a weaker signal and easier to rehearse.
"Tell me about a time a delivery was going to miss its date. What did you do?" Then insist on one occasion rather than a general description of approach. "Usually I would..." is the answer to a different question.
"We" is the most common evasion in interviews, often unintentional. "What did you personally do?" and "what would have happened if you had not been there?" separate the contributor from the bystander without hostility.
Every real account has a difficulty. A candidate who describes only smooth successes is either describing someone else's work or has not reflected on their own.
The single most informative question in most interviews. It reveals whether the person learns, and it is very hard to answer convincingly without having genuinely done the thing.
A scorecard only helps if the scale means something. "Rate communication 1 to 5" produces five interviewers using five private definitions, and the numbers that result are less useful than a conversation would have been.
Writing the anchors is the work. For a question about handling a missed deadline, a 5 might be: named a specific instance, described what they personally decided, said who they told and when, and identified what they would change. A 2 might be: described a general approach with no instance, or described the situation without their own role in it. Written like that, two interviewers who have never met tend to score the same answer within a point of each other — which is the entire objective.
Keep the notes short and factual: what the candidate said, not what you concluded about them. "Said he escalated to the client on day two" is evidence. "Seemed proactive" is the impression the evidence was supposed to support, and it is what makes debriefs unresolvable when two people disagree.
A structured process also makes it easier to notice questions that should not be asked at all — about marriage or family plans, about religion or caste, about age where it is not a genuine requirement of the role. These come up in unstructured interviews as small talk, usually without ill intent, and they create both an unfair process and an avoidable risk.
A fixed question set removes the opportunity almost entirely, which is a side benefit worth having. Where a business wants to be confident its hiring practice is defensible as well as effective, that is worth confirming with a qualified professional rather than settled from a blog post — but the structural fix is the same either way, and it also does most of the work that diversity, equity and inclusion commitments require in practice rather than in a policy document.
The method fails in adoption rather than in design. Managers agree it is sensible, use it for the first two candidates, and then revert under time pressure — particularly the senior ones, who experience it as a constraint on judgement they have earned.
Three things help. Build the question set with them rather than handing it over, because a scorecard someone helped write is one they defend. Keep it to five questions, because a fifteen-question form will be abandoned. And show them their own data after two quarters — the correlation between interview scores and how the hire actually performed is the argument that lands, and it is the one nobody can make for them.
Beyond that it is a teachable skill like any other, and interviewing skills for managers is one of the few training investments with a directly traceable return, because the cost of a wrong hire is already known to the business. It is also worth checking that the rest of the funnel is not undoing the work: a strong interview process attached to a vague brief and an inconsistent shortlist still produces bad outcomes, which is where recruitment process consulting usually starts.
Only if the interviewer reads questions aloud without listening. The questions are fixed; the follow-ups, the warmth and the conversation are not. Most candidates report structured interviews as fairer, because everyone is asked the same things.
Two or three scoring independently is the useful range. More than that adds scheduling cost and coordination without adding signal, and tends to increase deference to the most senior view rather than reduce it.
You can, but write down what produced the feeling first. Often it turns out to be something legitimate and specific that belongs on the scorecard. Sometimes it turns out to be that the person was unlike the interviewer, which is exactly what the process exists to catch.
Define it as specific behaviours and score it like anything else — how someone handles disagreement, how they work with people outside their team. Left undefined, culture fit is the most common route by which similarity bias re-enters a structured process.
About two hours for the first role: agree the four or five things that matter, write the questions, and describe what a strong and weak answer sounds like. Subsequent roles reuse most of it.
Workplace behaviour and the management capability a growing business runs on.
Discuss a Custom Training ProgrammeYour best engineer now runs the team and nobody told them how. What the first ninety days should actually contain, and what the business owes them.
Read the articleGood trainer, engaged room, excellent feedback forms — and no observable difference six weeks later. What went wrong, and what a training day needs around it.
Read the articleFour people were copied, everyone read it, nobody moved. What separates an email that produces action from one that produces a thread.
Read the articleAttendance, onboarding and policy all run on the same handful of manual steps. A free HR audit tells you which of them is costing you most.
Prefer the full picture? Request a free 360-degree HR audit.