Debriefs that produce decisions, not opinions

The debrief is where a structured process usually collapses back into a conversation about who liked whom. Three rules prevent it.

A team can run a well-designed interview loop with defined criteria and calibrated interviewers, and then undo all of it in a thirty-minute meeting where the most senior person says "I liked her" and everyone agrees.

The debrief is where structure most often collapses. Three rules hold it together.

Rule 1: Scores in before the meeting

Every interviewer submits scores and written evidence before the debrief, without seeing anyone else scores. No exceptions, including for the hiring manager.

This is the single highest-value rule in the whole process. Scores formed after discussion are contaminated by whoever spoke first and whoever is most senior. Independent scores make genuine disagreement visible, and disagreement is the most informative signal in the room.

If someone has not submitted, the debrief moves. Running it anyway teaches the team that the deadline is optional, and within two months nobody submits in advance.

Rule 2: Start with the disagreements

Open the scores. Skip everything the panel agreed on — agreement carries no new information. Go straight to the criteria where scores differ by two or more points.

The question is not "who is right". It is "what did you see that I did not?" Usually one of three things is true, and each has a different implication:

  • The interviewers saw genuinely different behaviour, because they asked different questions. Real signal about the candidate consistency.
  • They saw the same behaviour and weighted it differently. A calibration problem, and it will recur on every candidate until it is settled.
  • One interviewer was assessing something outside their assigned criteria. A loop design problem.

All three are worth ten minutes. None of them surface if the meeting opens with "so, what did everyone think?"

Rule 3: Decide with a stated rule

Agree the decision rule before you interview anyone, not while looking at a candidate you like. Common options, each defensible:

  • Consensus with a hiring manager veto. Works in small teams, slows down at scale.
  • Threshold on required criteria. No score below 3 on any must-have criterion, whatever the average. Prevents a spiky candidate passing on total score alone.
  • Majority with a written dissent. The dissenting view is recorded rather than argued away — useful if the hire is reviewed later.

What does not work is deciding the rule after seeing the scores. That is how a candidate with three 2s gets hired because the room liked them.

Four failure patterns

The seniority cascade

The most senior person speaks first and everyone converges. Fixed by pre-submitted scores and by having the most senior person speak last.

Relitigating the criteria

Someone argues the criteria were wrong for this candidate. Perhaps they were — note it and change them for the next role. Changing the bar for the candidate in front of you is how bias enters a structured process wearing a reasonable argument.

The absent veto

Someone who did not interview the candidate blocks the hire on impression. If their judgement matters, put them in the loop with assigned criteria. If it does not, they do not get a vote.

Comparing to the last candidate instead of the bar

"Better than the last one" is not a hiring standard. The comparison is against the criteria, not against the sample you happen to have seen.

What to record

Four things, and they take two minutes:

  1. The decision.
  2. The criteria that drove it — which specific scores, not a summary sentence.
  3. Any unresolved disagreement, with the dissenting view.
  4. Anything the panel wants the manager to know if the person is hired.

The fourth is the one teams skip and later wish they had. If two interviewers flagged the same development area, the manager should know in week one rather than at the first review.

Keeping it short

A debrief for a single candidate should take fifteen to twenty minutes. If it runs to an hour, the loop is producing weak signal and the meeting is compensating. That is a loop design problem — see running a structured loop and the scorecards themselves.

Long debriefs are also the most common hidden cause of slow hiring: the interviews finished on Tuesday and the decision waited until the panel could all meet on Friday.

Get hiring insights in your inbox

One email a week — the best playbooks, benchmarks and product updates. No spam.

More from Resources

Everything you need to hire better — in one place.