write-role-scorecard

name	write-role-scorecard
description	Use when defining a role before hiring for it — to specify the outcomes the new person must achieve, the competencies required to achieve them, and the cultural requirements, so that interview questions target evidence of actual job performance rather than proxies like credentials or experience.

Write Role Scorecard

Define a hiring role by its required outcomes, competencies, and cultural fit criteria — so the hiring team evaluates candidates against actual job performance standards rather than resume signals.

Why This Is Best Practice

Adopted by: Smart & Street's "Who: The A Method" is the most widely cited CEO-level hiring methodology, with documented adoption at the Blackstone Group, General Atlantic, and hundreds of private equity portfolio companies; ghSMART's Topgrading methodology — which the scorecard is derived from — has been applied at over 5,000 organizations; the US Navy SEALs use a performance-standard scorecard equivalent in their selection process (Basic Underwater Demolition/SEAL training); SHRM's competency-based hiring framework incorporates scorecard principles as the foundation of structured hiring Impact: Smart & Street's research (313 hiring decisions analyzed) found that managers using scorecards to define and evaluate against role outcomes hired "A players" (performers in the top 10% for the role) 90% of the time, compared to 26% using traditional credential-and-interview methods; McKinsey's 2021 talent research found that organizations with clearly defined role outcomes rather than vague job descriptions reduced time-to-productivity for new hires by 35%; Geoff Smart's follow-on research (500+ executive hires) found that 90% of hiring failures trace to misaligned expectations of what success in the role looks like — a gap the scorecard closes before the hire Why best: Job descriptions are marketing documents — they attract candidates; scorecards are performance standards — they define what success requires; traditional interviews evaluate whether a candidate is likable, impressive, and experienced; scorecard-based interviews evaluate whether a candidate has the track record of accomplishing the specific outcomes the role requires; the scorecard replaces subjective "gut feel" hiring with evidence of past performance on the dimensions that matter

Sources: Smart & Street "Who: The A Method for Hiring" (Ballantine Books, 2008); SHRM "Competency-Based Hiring" knowledge center; Tomas Chamorro-Premuzic "Why Do So Many Incompetent Men Become Leaders?" (Harvard Business Review Press, 2019) on improving hiring standards

Steps

1. Write the mission: one sentence describing what this role is for

The mission is not a job title or a list of responsibilities. It is one sentence describing what a fully successful person in this role will accomplish for the organization:

❌ "The Head of Sales will lead the sales organization and manage the sales team."
(what they do, not what they accomplish)

✅ "The Head of Sales will grow North American ARR from $12M to $30M within 18 months 
by building a repeatable outbound motion and increasing average deal size by 40%."
(what they must accomplish)

If you cannot write the mission in one sentence, you do not yet understand why the role exists. Do not start hiring until you can write it.

2. Define 3–8 outcomes — what must be accomplished in the first year

Outcomes are measurable results the person must deliver. They are not tasks ("manage the team") or responsibilities ("oversee the product roadmap") — they are results with implicit deadlines and measures.

For each outcome, write:

• What will be true by when
• How you will know if it is true (the measure or observable evidence)

Outcomes for a VP of Product (example):
1. Ship a redesigned mobile checkout by Q3, measured by 20% improvement in conversion rate
2. Build a 12-month product roadmap with executive sign-off by end of month 2
3. Hire 3 senior PMs by end of Q2, all clearing the full hiring bar
4. Achieve a product NPS of ≥ 45 by end of year (from current 31)
5. Establish a weekly product-engineering sync that leadership rates as "highly useful" 
   on a post-quarter survey

Shoot for 5–7 outcomes. Fewer than 3 is under-definition; more than 8 creates competing priorities that distort the interview.

3. Define competencies — how the outcomes will be achieved

Competencies are the skills and behaviors required to deliver the outcomes. They are derived from the outcomes, not from generic competency libraries.

For each major outcome, ask: "What kind of person is capable of delivering this?" The answers are the competencies.

Competencies for the VP of Product above:
- Persuasive communication: can align product roadmap across engineering, design, 
  sales, and executive without formal authority
- Data-driven prioritization: makes sequencing decisions from customer data and 
  business metrics, not intuition or stakeholder pressure
- PM coaching and hiring: can identify and develop senior-level product managers
- Execution pace: drives urgency without sacrificing quality; has shipped in compressed timelines

Keep competencies to 5–8. Each competency should map to at least one outcome.

4. Define cultural requirements

Cultural requirements are the values, working styles, and interpersonal behaviors the person must demonstrate to operate effectively in this specific team and organization. These are not universal character traits — they are context-specific.

Cultural requirements (example, fast-paced startup):
- Operates with minimal process — comfortable making decisions in ambiguity
- Gives and receives direct feedback without defensiveness
- Takes ownership of failures rather than attributing them to others
- Prioritizes team outcomes over personal credit

Cultural requirements prevent hiring someone who is technically excellent but creates organizational friction that nets negative.

5. Calibrate the scorecard with all interviewers before the search begins

Share the scorecard with every interviewer before the first candidate is evaluated. The scorecard is the shared standard — each interviewer assesses the same outcomes and competencies.

In the calibration session:

"Here are the outcomes the hire must achieve. When you interview candidates, 
your job is to surface evidence that they have done things like this before — 
not just that they have experience in the domain."

Assign each interviewer to probe specific competencies, avoiding duplication (see run-behavioral-interview for interview execution).

6. Score candidates against the scorecard — not against each other

After each interview, score the candidate against the scorecard:

• For each outcome: does the candidate's track record make you confident they can achieve this? (1–4 scale)
• For each competency: what specific evidence supports or undermines this competency?

The debrief question is: "Does this candidate's history give us evidence that they will achieve our outcomes?" — not "how do they compare to the other candidates?" Comparing candidates produces relative ranking; the scorecard produces an absolute standard.

Hire only when you have a candidate who scores above threshold on all critical outcomes and competencies. Do not compromise on the scorecard to fill the role quickly — a mis-hire costs 50–200% of annual salary.

Rules

• Write the mission before the outcomes — if you cannot state why the role exists in one sentence, you are not ready to define the scorecard
• Outcomes first, then competencies — competencies are derived from what the outcomes require, not from a generic HR library
• No more than 8 outcomes — more than 8 creates an interview that is too diffuse to probe any outcome well
• Every interviewer scores against the same scorecard — if each interviewer uses their own informal criteria, you are running multiple different interviews, not one structured process
• Do not substitute the scorecard with the job description — job descriptions attract; scorecards select; they serve different purposes and must not be conflated

Common Mistakes

• Writing tasks instead of outcomes: "manages the engineering team" is not an outcome; "builds a team capable of shipping 2× the current release cadence within 9 months" is.
• Generic competencies not tied to this role: "strong communication" and "team player" describe almost every job; competencies must be specific to what this role requires.
• Scorecard written by one person without calibration: if the hiring manager writes the scorecard but interviewers evaluate against their own implicit criteria, the scorecard has no effect on the decision.
• Compromising on the scorecard to hire fast: hiring someone who meets 60% of the scorecard fills the seat and fails the team; "we'll see if they can grow into it" is a prediction, not a plan.
• Different scorecard for different candidates: if you modify the outcomes or competencies during the search based on who you've seen, you're optimizing for available candidates rather than the role's actual requirements.

When NOT to Use

• For high-volume, low-complexity roles where the job is well-defined and outcomes are identical across all role-holders — in these cases, a standardized job specification and structured interview rubric is sufficient; the full scorecard framework is best suited for roles where outcomes vary based on organizational context and moment.