How to Build a Role Scorecard

help wanted sign on glass

Translating Strategy into Talent Clarity for Strategy and Execution Leaders

If strategy lives or dies by execution, then hiring is the first bottleneck. And if you want to scale execution without losing the plot, the scorecard is where it starts.

A role scorecard isn’t a job description dressed up in bullet points – it’s a strategic organizational artifact. It’s what happens when you stop hiring based on vibes and start aligning talent with outcomes. Geoff Smart and Randy Street, in Who: The A Method for Hiring, put it simply: a strategic hire needs a strategic spec.

“Scorecards translate your business plans into role-by-role outcomes and create alignment among your team, and they unify your culture and ensure people understand your expectations.” – Who: The A Method for Hiring, Geoff Smart and Randy Street

But let’s make this real. Say your company is growing, and sales can’t just sit on the CEO’s desk anymore. You need someone to own and scale mid-market growth. Not just manage a sales team. Not just “drive pipeline.” You need someone who actually moves revenue.

This is where the scorecard comes in.


1. Start with the Role’s Mission

You need a one-sentence answer to: Why does this role exist?

Not a task list. Not a vague aspiration. A crisp, outcome-driven statement that makes it immediately obvious what this person is here to achieve.

  • Bad: “Manage the sales team.”
  • Good: “Grow mid-market revenue.”

This isn’t about poetic flair – it’s about clarity at the point of hiring. A strong mission statement does two things: it frames the role within your strategy, and it gives every stakeholder – from the recruiter to the CFO – a shared understanding of success.


2. Define Role Outcomes

Outcomes are where the mission gets teeth. These are the 3–5 things this person must deliver for the mission to be considered fulfilled. Yes, Who says you can go up to 8. No, you probably shouldn’t.

Keep them clean, measurable, and linked to the real impact your strategy execution needs.

For example:

  • Revenue Generation: Hit or exceed annual revenue targets, factoring deal size to ensure efficient use of sales team efforts.
  • Sales Cycle Velocity: Reduce time from lead qualification to close.
  • Client Retention: Improve repeat purchase rates.

Think of it this way: if the mission is the why, these are the what. And they become your future performance bar for A-players.


3. Name the Competencies

This is the how. The behaviors and capabilities that predictably drive the outcomes.

Start with 5–7. Fewer, and you risk under-specifying the role. More, and you’re chasing unicorns.

Here’s an example set for our mid-market sales role:

  • Sales Leadership & Team Development: Hires A-players, sets high bars, builds culture, and coaches performance.
  • Data-Driven Decision Making: Uses pipeline data and performance metrics to drive action, not intuition.
  • Operational & Process Optimization: Fixes bottlenecks, scales workflows, and partners cross-functionally.
  • Customer-Centric Mindset: Designs experiences that drive retention and lifetime value.
  • Opportunity Prioritization & Execution: Focuses the team on high-leverage work aligned to company strategy.

Competencies ground your hiring process in the actual skills and traits required to succeed – not just shiny credentials or buzzwords.


4. Assign Metrics

You can’t optimize what you don’t measure. Metrics are the proof points that tell you whether the outcomes are being hit.

From our example:

  • Committed revenue
  • Sales cycle length
  • Average deal size
  • Client retention rate
  • Team performance (if managing others)

You don’t need a dashboard on day one. But you do need to know what success looks like in numbers.


PUTTING IT ALL TOGETHER

Role:Sales Manager
MissionGrow mid-market revenue
Outcomes– Revenue Generation
– Sales Cycle Velocity
– Client Retention
Competencies– Sales Leadership & Team Development
– Data-Driven Decision Making
– Operational & Process Optimization
– Customer-Centric Mindset
– Opportunity Prioritization & Execution
Metrics– Committed revenue
– Sales cycle length
– Average deal size
– Client retention rate

What Happens Before You Recruit

A scorecard isn’t just for the candidate – it’s a forcing function for internal clarity. That internal clarity is a process undertaken during and after you build a scorecard.

1. Align with Your Org Design

Scorecards create internal SLAs between roles and strategy. They:

  • Make sure all roles in your org are rowing in the right direction.
  • Avoid role overlap, expose accountability gaps, and clarify decision boundaries.
  • Standardize what performance looks like across teams.

Already mapping your org structure? Great – the scorecard slots right in. Still figuring it out? Start with one. Don’t over-engineer. Clarity compounds.

2. Pressure-Test It

Before you post a job, stress-test the scorecard with others in your organization:

  • Would hitting these outcomes actually move the company forward?
  • Are the metrics objective and trackable?
  • Do the competencies align with how your org really operates – not just how you wish it did? If it’s a wish, what else needs to happen in order to for this role to integrate successfully?

This alignment step saves time later. It turns the scorecard into a shared reference point between the hiring manager, the recruiter, and the leadership team.


Final Thoughts: Scorecards as System Inputs

Most companies hire reactively. A need arises, someone writes a job description, and the interview loop becomes a game of “do we like them?”

A scorecard flips the model. It makes hiring an input to strategy execution, and forces clarity upfront. When you treat hiring as a first-order system input, the scorecard becomes a powerful tool: one that lets you reverse-engineer your org chart based on strategic goals, not just current needs.

A well-built scorecard helps you find not just someone who can do the job, but someone who will move the mission forward.

Alex Avatar