Scorecard or gut? Making a defensible hiring call — a live classroom session

▶ Present these slides — opens the deck in your browser. Arrow keys advance; press S for speaker notes, F for fullscreen.

1. For the instructor

This is a ready-to-run, 75-minute classroom session on a decision almost everyone eventually makes: you are hiring one person, two finalists are in front of you, and the candidate the room likes is not the candidate the scores favour. Do you trust the scorecard or your gut — and how do you make the call when they point in opposite directions? Students run a simple hiring scorecard on one composite company, argue the call in small groups, and defend a hire / no-hire decision.

You need no prep. Everything to teach this cold is in this pack: a case (section 3), a minute-by-minute run of show (section 4), the few concepts the decision needs (section 5), a group exercise (section 6), a facilitator answer key you can run without any HR background (section 7), discussion prompts (section 8), a printable student handout with the scorecard on it (section 9), a stretch task for fast tables (section 10), and a slide outline (section 11).

How to run it in a mixed room. No HR or business background is assumed, and none is needed — everyone has an intuition about hiring, which is exactly the intuition this session pressure-tests. Every term is defined the first time it appears, and the only arithmetic is averaging four small numbers. Put students in groups of three or four so quieter voices get heard, and let the tables do the scoring and argue the call before you reveal anything. This case has one more defensible answer, but the reasoning is the prize — reward a table that argues its way there, not a guessed letter.

One honest line to say out loud at the start: this is teaching material, not a certification, not credit-bearing, and it does not promise any outcome. It is practice at making and defending a hard hiring call.

A note on the clock. The run of show below is a tight 75 minutes with little slack — in a 30–40 student room budget ~85 minutes in practice (set-up, table-forming, and report-backs always run long). If you fall behind, cap report-backs at two tables and cover two of the discussion prompts. Protect the group exercise and the answer-key debrief — those are the session.

2. Session at a glance


Audience	Any future manager; no HR background assumed; hiring is universally relatable
Class size	12–40 (works in groups of 3–4)
Total time	75 minutes
What students bring	Nothing but the handout; no laptops; only light mental arithmetic

By the end students can:

Run a simple hiring scorecard — apply a fixed 1–4 scale and a pass bar to two candidates, and say who clears it and who does not.
Name why a structured score predicts the job better than a gut feeling, and name the biases (halo, affinity, anchoring) that a gut feeling quietly smuggles in.
Defend a hire / no-hire call when the scores and the gut disagree — and name the one piece of evidence that would flip it.

Further reading (for you or keen students): the self-paced “Decide” course this session builds on — Score the candidate: why a hiring scorecard beats a gut feeling (projects/score-the-candidate) — covers the same ideas in more depth, including the research on why structured interviews predict performance.

3. The case

Meridian Home Services is a composite home-repair company — invented for this class. Every name, role, and number below is illustrative, chosen for clean reasoning, and is not drawn from or claimed about any real company or person.

You have just been made a team lead at Meridian, and your first job is to hire one Customer Support Specialist — the person who answers calls and emails from customers, calms them down when a technician runs late, and books the right job into the right slot without double-booking anyone. Two finalists made the final round. A three-person panel interviewed both and filled in a scorecard for each.

Before anyone interviewed, the panel agreed on the four skills the job actually needs and a fixed 1–4 scale — 1: well below the bar, 2: below the bar, 3: meets the bar, 4: clearly exceeds it. Two skills are core (the job turns on them day to day); two are secondary (they matter, but less). The agreed pass bar: a candidate must score 3 or above on both core skills and average 3 or above overall.

Here is what the panel recorded — each interviewer scoring on their own first, then the panel talking (all scores illustrative):

Skill	Type	Dana (the panel’s favourite)	Owen (the quiet one)
Handling an upset customer	core	2	3
Getting the details right (no double-bookings)	core	2	4
Clear writing (emails, chat)	secondary	4	3
Learning the scheduling system	secondary	3	3
Average		2.75	3.25

Here is the trap. Dana was a joy to interview — warm, funny, quick, and a genuinely lovely writer; the panel came out of her interview smiling and has talked about her ever since. Owen was quiet, a little stiff, easy to forget in the debrief. But the scores tell the opposite story: Dana is below the bar on both core skills, and Owen meets or beats the bar on both. The gut is loud and points at Dana; the scorecard is quiet and points at Owen. You have to make the call — and one of your panelists is already lobbying hard for Dana.

4. Run of show

Total planned time: 75 minutes. If you run long, trim the report-out and debrief blocks first.

8 min — Hook. Pose Meridian’s hire from section 3 out loud (or project Slide 2). Ask for a quick show of hands: Dana or Owen? Note the split — you will return to it. Do not explain anything yet.
12 min — Teach the few ideas the call needs (section 5): what makes an interview structured, why structure predicts the job better, and the three biases a gut feeling hides. Keep it to the slides; the case does the rest.
5 min — Set up the exercise. Hand out the worksheet (section 9), form groups of 3–4, read the task aloud, and confirm every group knows the pass bar and the question.
20 min — Group work. Tables average the scores, apply the bar, decide who clears it, and write a hire / no-hire call plus the one fact that would flip it. Circulate using the “stuck table” prompts in section 7.
15 min — Report-outs and debate. Take one or two “hire Dana” tables and one or two “hire Owen” tables. Make each name what their choice costs. Let them argue it out.
10 min — Reveal and debrief. Walk the answer key (section 7), then run two or three prompts from section 8.
5 min — Close and stretch. Give the one-sentence takeaway and point fast finishers at the stretch (section 10).

5. Teaching points

Teach only these. They are all the decision needs.

Scorecard vs gut feeling. A hiring scorecard is an agreement made before you interview: you write down the handful of skills the job needs, ask every candidate about the same things, and each interviewer rates each skill on a fixed scale, writing their score down on their own before the group talks. A gut feeling is the opposite — no fixed skills, no fixed questions, just the overall impression a candidate leaves. At Meridian the scorecard can say exactly where Dana falls short (both core skills); the gut can only say the room liked her.

What makes an interview “structured.” Three things, and all three matter: (1) fixed, job-relevant skills decided up front — for Meridian, handling upset customers, getting details right, writing, and learning the system, not a vague sense of “fit”; (2) the same questions and the same scale for everyone, so a 3 means the same thing for Dana as for Owen — that is what makes them comparable; (3) independent scores written before the group talks. A single overall “would I want them here?” number is not a scorecard — it is the gut feeling wearing a uniform.

Why structure predicts the job better. A structured score is tied to the thing you actually care about — can this person do the work — while a gut feeling is tied to the conversation. Structured interviews are known to forecast on-the-job performance more reliably than free-form ones; the idea has a name, predictive validity (how well a measure taken before hiring lines up with performance after). Dana’s warmth predicts she is pleasant to interview; it does not predict she can calm an angry customer, and the scorecard caught the gap the warmth hid. Two honest limits: “predicts better” means more reliable on average, not never wrong; and a scorecard is only as good as the skills you put on it — score the wrong things, or score “feels like us,” and you have built a tidy way to make the same old mistake.

The three biases a gut feeling hides.

Halo effect — one strong trait bleeds into everything. Dana writes beautifully (a 4), so the panel is tempted to assume she must be strong everywhere. Scoring each skill on its own line breaks the halo: her writing 4 cannot lift her upset-customer 2.
Affinity bias — we rate people who remind us of ourselves higher, for reasons that have nothing to do with the work. “I clicked with them” is exactly where affinity does its damage.
Anchoring — the first opinion in the room drags everyone toward it. This is why scoring before the group talks matters: once the loudest voice says “I loved Dana,” later scores bend to match. Independent-then-discuss is the cheap, powerful part of structure — and discussing first quietly throws the benefit away.

Making the call when they disagree. A working rule: (1) Read the scorecard first, skill by skill — who clears the bar on what matters? (2) Treat a strong contrary gut as a flag, not a verdict — it is worth investigating, because the panel might have missed something the scorecard does not capture, but “I liked her” is not evidence about the core skills. (3) Name the one thing that would flip the call — the call flips on new, job-relevant evidence scored the same way as everything else, never on the volume of enthusiasm.

6. Group exercise

The task. In your group, run the scorecard and decide who Meridian should hire — Dana, Owen, or neither — and be ready to defend it. This is a hire / no-hire call: for each candidate, decide whether they clear the bar.

Handout. Use the worksheet in section 9. It has the case facts, the pass bar, and the panel’s scores with space to work.

Steps (about 20 minutes):

Score it (5 min). For each candidate, confirm the average and check the two core skills against the bar (3+ on both cores, and 3+ average). Write down who clears the bar and who does not. This is the arithmetic — everyone can do it.
Read the disagreement (6 min). The panel feels strongly about Dana. Name what that feeling is measuring, and name any of the three biases you can see at work in the case. Is the gut here a reason to look harder, or a reason to overturn the scores?
Call it (6 min). Write one sentence: hire Dana, hire Owen, or hire neither — and why. If you would not hire your gut favourite, say plainly why the scores win.
Flip it (3 min). Write the single piece of evidence that, if you learned it tomorrow, would change your call. This is the most important line on the page.

7. Facilitator answer key

The defensible call is to hire Owen — and to treat Dana as a no-hire despite the room’s warmth. Run the bar: Owen scores 3 and 4 on the two core skills and averages 3.25, so he clears both parts of the bar. Dana scores 2 and 2 on the two core skills and averages 2.75 — she fails the bar twice over, on exactly the skills the job turns on. On the measure the panel built to predict the job, this is not close. The only thing on Dana’s side is a feeling that measures the interview, not the work — and that feeling is riding on a halo (her lovely writing, a 4, colouring everything) and probably affinity (the panelist lobbying for her “clicked” with her). Naming those is the point of the lesson.

What each option would cost. Hiring Owen (recommended) costs you Dana’s real strengths — her writing and warmth — and Owen only meets the bar on handling upset customers (a 3), so you should plan to coach that; the cost is a development need you go in with eyes open. Hiring Dana on gut costs you a specialist who is below the bar on both core skills: predictable early trouble calming angry customers and avoiding double-bookings, plus a quieter cost — you would be teaching the panel that the scorecard is theatre, so next time no one scores honestly. Hiring neither / re-opening the search costs weeks of delay and risks losing Owen to another offer, when you already hold valid, comparable evidence that one finalist clears the bar. The trade-off comes out clearly on Owen’s side.

What would flip the call: real, job-relevant evidence — scored the same way as everything else — that Owen’s quiet stiffness is an actual de-escalation problem and not just interview nerves (then you would test that skill harder before committing), or evidence that the interview was not consistent — say the panel asked Dana far harder scenario questions than Owen — which would break comparability and mean the scores cannot be trusted as they stand. Common wrong turns: letting Dana’s writing 4 (the halo) stand in for her core skills; treating the lobbying panelist’s enthusiasm as evidence rather than as the bias to discount; and “averaging in” the gut by blending a global impression with the skill scores — that just smuggles the feeling back in wearing a number. Stuck table? Ask them one question: “Forget who you liked — on the two skills the job actually turns on, who clears the bar?” Once they say “only Owen,” the call makes itself, and the rest of the work is naming honestly why the gut pulled the other way.

8. Discussion & debrief

Run three or four of these after the report-outs:

The room loved Dana and forgot Owen. What was that feeling actually measuring — and which of the three biases do you think did the most work here?
A panelist says: “Dana’s below the bar on paper, but I’ve hired people for years and my gut says she’s the one.” How do you weigh experienced gut against the scores without just dismissing the person?
When should a strong gut feeling change a hiring call? What would the feeling have to point at for you to act on it?
Owen only meets the bar on handling an upset customer. Does “just clears it” worry you — and if so, what would you do about it without flipping to Dana?
Someone proposes scrapping the four scores and having each interviewer give one overall “would I want them on the team?” number instead. What is wrong with that, in one sentence?

One-sentence takeaway: Score the skills the job needs before you weigh how much you liked anyone, and let a contrary gut send you looking for evidence — not overturn the scores.

9. Student handout

(Printable. One per student or one per group.)

The situation. You are a new team lead at Meridian Home Services (a made-up home-repair company — all names and figures are illustrative). You are hiring one Customer Support Specialist: the person who answers customer calls and emails, calms people down when a technician runs late, and books the right job into the right slot. A three-person panel interviewed two finalists, Dana and Owen, and scored each on the four skills the job needs, using a fixed 1–4 scale — 1: well below the bar, 2: below the bar, 3: meets the bar, 4: clearly exceeds it.

The pass bar (agreed before anyone interviewed): a candidate must score 3 or above on both core skills and average 3 or above overall.

The panel’s scores:

Skill	Type	Dana	Owen
Handling an upset customer	core	2	3
Getting the details right (no double-bookings)	core	2	4
Clear writing (emails, chat)	secondary	4	3
Learning the scheduling system	secondary	3	3
Average		______	______

One more thing you know: the whole panel came out of Dana’s interview smiling — she was warm, funny, and a wonderful writer — and one panelist is lobbying hard to hire her. Owen was quiet and a little stiff, and easy to forget in the debrief.

Your question: Who should Meridian hire — Dana, Owen, or neither?

Work through these in your group:

Score it. Fill in each average above. For each candidate, do they clear the bar (3+ on both cores and 3+ average)? Dana clears the bar: Yes / No. Owen clears the bar: Yes / No.
Read the disagreement. The panel feels strongly about Dana. What is that feeling measuring, and which bias (halo, affinity, anchoring) can you spot?
Call it. Hire Dana, hire Owen, or hire neither — in one sentence, with your reason.
Flip it. The single piece of evidence that would change your mind:

10. Stretch

For tables that finish early:

Break the scorecard. Suppose you learn the panel accidentally asked Owen the easy customer scenarios and Dana the hard ones. Does that change your call — and what does it tell you about the one condition a scorecard needs to be trusted at all? (Hint: what makes two candidates comparable?)
Find the real flag. Invent a fact about Owen that would legitimately outweigh his higher scores — something job-relevant, not just “he was quiet.” Then say exactly how you would turn that hunch into evidence: what would you add to the scorecard, and how would you score it the same way for both candidates, so the call still rests on structure?
Audit for bias in disguise. One of Meridian’s four skills could quietly become a bias. Which one is most at risk of drifting into “reminds us of us,” how would you catch it, and what anchored wording would you replace it with so it measures the job and not the person?

11. Slides

Slide 1 — Scorecard or gut?

Title slide: making a defensible hiring call
A 75-minute working session — you will score two real candidates and defend a call
Presenter note: Set the tone — this is not a lecture; they will score, argue, and defend.

Slide 2 — Meet the two finalists

You are hiring one Customer Support Specialist at Meridian Home Services (made-up; figures illustrative)
Dana — warm, funny, a lovely writer; the whole room liked her
Owen — quiet, a little stiff, easy to forget
Presenter note: Read it, then ask for a show of hands — Dana or Owen? Note the split.

Slide 3 — The scorecard (before any feelings)

Four job skills, fixed 1–4 scale; two core (the job turns on them), two secondary
Bar: 3+ on both core skills, and 3+ average
Dana averages 2.75 (core: 2, 2). Owen averages 3.25 (core: 3, 4)
Presenter note: The gut points at Dana; the scores point at Owen. That gap is the whole session.

Slide 4 — What makes it a scorecard (not a gut feeling)

Fixed, job-relevant skills — decided before anyone interviews
Same questions, same scale for everyone — so a 3 means the same thing for both → comparable
Independent scores, written before the group talks
Presenter note: A single “would I want them here?” number is the gut feeling in a uniform.

Slide 5 — Why the scores beat the feeling

A structured score measures the job; a gut feeling measures the conversation
Structured interviews forecast performance more reliably — predictive validity
Warmth predicts a pleasant interview, not a calm phone call with an angry customer
Presenter note: “Predicts better” = more reliable on average, not never wrong.

Slide 6 — Three biases the gut hides

Halo — Dana’s writing 4 tempts you to assume she’s strong everywhere
Affinity — “I clicked with them” rates people who remind us of us higher
Anchoring — the first loud opinion drags the rest → score before you talk
Presenter note: Ask which bias they can spot in the case.

Slide 7 — Your task

In your group: score it → read the disagreement → call it → flip it
Hire Dana, Owen, or neither — one sentence, plus the one fact that would flip it
20 minutes. Defend it, don’t guess it.
Presenter note: Hand out the worksheet; form groups of 3–4.

Slide 8 — The call, and the takeaway

Owen clears the bar on both core skills; Dana fails both — hire Owen
A contrary gut is a flag to investigate, not a verdict — flip only on scored evidence
Score the skills the job needs before you weigh how much you liked anyone
This is practice at a hard call — not a certification, not a promise
Presenter note: Point fast finishers at the stretch task.

12. Sources & license

Sources. See SOURCES.md in this folder for the full provenance. In short: Meridian Home Services, the two finalists Dana and Owen, and every figure attached to them — the role, the panel, the 1–4 scale, and all the scores — are composite: invented from ordinary, realistic hiring dynamics for clean teaching, and not drawn from or claimed about any real company or person. The ideas used to reason about them (structured vs unstructured interviews, predictive validity, and the named biases — halo, affinity, anchoring) are standard, publicly documented concepts, cited in SOURCES.md.

License & disclaimer. This module is offered for free classroom use under the canonical terms maintained in company/legal/classroom-license.md — refer to that file for the exact wording; the license text is not restated or altered here. In plain terms: this material is provided as is, for teaching and practice only. It is not a certification, is not credit-bearing, and does not promise any particular result. Nothing here is legal or HR advice; real hiring decisions should follow your own organisation’s policies and applicable law.

Instructor teaching material, provided as-is. Not accredited, not a certification, and not affiliated with or endorsed by any university. Uses composite (invented) companies and illustrative figures.