The A-Player Scorecard Protocol

The Problem

You posted a job description. You got resumes. You ran interviews. You hired the person who "felt right." Six months later, they're underperforming and you're wondering what went wrong. Here's what went wrong: you hired based on inputs — tasks, qualifications, years of experience — and hoped the outputs would take care of themselves. That's not hiring. That's gambling. And "potential" is a gambling term.

Who This Is For

Founders who are done guessing. You've made at least one hire that crushed the interview and cratered on the job, and you want a repeatable system that predicts performance before the offer letter goes out — and holds people accountable long after.

What You'll Need

• Time commitment: 15 minutes for the Flash Draft. 60 minutes for the full Alignment Cycle. Then 15 minutes per role once you've built the muscle.
• Prerequisites: Clarity on what the business needs to achieve in the next 12-18 months. If you can't articulate that, stop here. Fix your strategy first.
• Tools: A document for the Scorecard itself. A willingness to send it to your boss, your peers, and your direct reports before you interview a single candidate.

The Protocol

Job Descriptions Are Dead. Build Scorecards.

A Job Description lists tasks. Inputs. "Manage the sales team." "Coordinate with marketing." "Report on quarterly numbers." It tells you what someone will do all day. It tells you nothing about whether they'll win.

A Scorecard defines outcomes. Outputs. It's a business plan for a person.

And here's the part most founders miss: the Scorecard does double duty. It's your hiring filter AND your management tool. The same document that tells you who to hire tells you how to review them at the end of the quarter. No more scrambling to invent performance criteria after someone's already in the seat.

Phase 1: The Mission

Distill the role into one sentence. Not a task summary. Not a paragraph of responsibilities. One sentence that captures why this role exists and what victory looks like.

The test: if a candidate reads it and can't say "I have done exactly this before," they're a gamble.

Wrong: "The Sales Manager manages the sales team and reports numbers."

Right: "The Sales Manager constructs a predictable revenue engine that scales from $5M to $10M ARR within 18 months."

The first version describes an activity. The second version describes a transformation. That gap is where bad hires live.

Phase 2: The Outcomes

Write 3-5 binary victories. At the end of the review period, there is no debate. They hit the number or they didn't. Yes or No.

The structure for each outcome: From [Current Reality] to [Desired Reality] by [Date].

Two rules:

One — every Scorecard must include at least one System Improvement outcome. You're not just hiring someone to maintain the status quo. You're hiring someone to build something that didn't exist before. "Reduce onboarding time from 6 weeks to 2 weeks by Q3" is a system improvement. "Onboard new hires" is an activity.

Two — avoid activities disguised as outcomes. "Make 50 cold calls per day" is an input. "Generate $2M in net new pipeline by end of Q2" is an output. You're buying results, not motion.

Phase 3: The Competencies

Split into two categories.

Hard Skills are table stakes. The technical qualifications you need to play the game. These aren't differentiators — they're entry requirements. Can they use the tools? Do they know the domain? Have they operated at this scale before?

Cultural DNA is where most hiring goes wrong. This is values alignment, and it requires the Near Enemy filter.

Every virtue has a shadow — a trait that looks almost identical but operates in the opposite direction. Buddhist psychology calls these "near enemies." In hiring, they're the reason your best-looking candidates become your worst performers.

You want Ownership. The near enemy is the Control Freak — someone who hoards information, refuses to delegate, and builds a kingdom instead of a system.

You want High Standards. The near enemy is Perfectionism that becomes Paralysis — someone who polishes every detail while deadlines burn.

You want Empathy. The near enemy is Pleasing — someone who avoids hard conversations, lowers the bar to keep people comfortable, and lets conflict fester.

Your Scorecard must name these enemies explicitly. Write down the trait you're hiring for AND the shadow you're filtering against. If you can't articulate the distinction before the interview, you won't spot it during the interview.

The Draft-to-Craft Workshop

Step 1: The 15-Minute Flash Draft. The hiring manager writes the "shitty first draft" alone. Set a timer. Don't edit. Don't wordsmith. Get the Mission, Outcomes, and Competencies on paper in their roughest form. Perfection kills momentum here — you're capturing signal, not crafting prose.

Step 2: The Alignment Cycle. Before you interview anyone, send the draft Scorecard to three people: your boss (or board member), a peer in a related function, and someone who'd report to this role. Each one sees blind spots you can't. Your boss catches strategic misalignment. Your peer catches overlap and gaps. Your future direct report catches whether the outcomes are actually achievable.

This step is where founders push back hardest. "I know what I need." Maybe. But alignment before interviewing saves you from hiring the right person for the wrong Scorecard.

Step 3: Calibration. Sharpen every line with the "So What?" test. Read each outcome aloud. If someone could respond "So what? Anyone could do that," the bar is too low. If someone responds "So what? That's impossible," the bar needs context. The sweet spot is specific enough to measure and ambitious enough to matter.

Worked Example: Head of Sales

Mission: Build a repeatable, scalable sales engine that takes annual revenue from $3M to $8M within 24 months — without the founder on every call.

Outcomes:

• From founder-led sales (80% of deals) to team-closed revenue (80% of deals) by Month 12.
• From unpredictable monthly revenue (±40% variance) to forecast accuracy within 15% by Q3.
• From zero sales playbook to a documented, trainable sales process that a new hire can execute within 30 days by Month 6.

Near Enemy Watch:

• Ownership vs. Hero Complex. You want someone who builds a machine, not someone who becomes the machine. If their track record is "I personally closed $X," ask who closed deals when they were on vacation.
• High Standards vs. Churn-and-Burn. A great sales leader raises the bar. A toxic one burns through reps quarterly and blames "talent quality."

Worked Example: Chief of Staff

Mission: Multiply the CEO's output by owning the operating rhythm, clearing decision bottlenecks, and running cross-functional projects the CEO doesn't have time to lead.

Outcomes:

• From CEO attending 30+ hours of meetings per week to fewer than 15 hours by Month 3 — without dropping any critical decisions.
• From ad hoc project management (Slack threads, forgotten follow-ups) to a documented weekly operating cadence with tracked commitments by Month 2.
• From zero cross-functional visibility to a live dashboard showing every active initiative, its owner, its status, and its next decision point by Q2.

Near Enemy Watch:

• Proactivity vs. Overreach. A great CoS anticipates what the CEO needs and handles it. A dangerous one starts making decisions the CEO didn't delegate — and the team stops knowing who's actually in charge.
• Discretion vs. Gatekeeping. The CoS manages access to the CEO's time. The near enemy builds a moat around the CEO and becomes a political bottleneck.

Worked Example: Senior Product Manager

Mission: Turn customer pain into shipped product that moves the North Star metric — on a 6-week release cycle, with engineering, design, and data aligned before a single line of code gets written.

Outcomes:

• From feature-request-driven roadmap to outcome-driven roadmap (every item tied to a measurable metric) by Month 2.
• From average cycle time of 14 weeks to 6-week release cadence for 80% of shipped features by Q3.
• From zero structured discovery process to a repeatable research-to-spec pipeline that produces one validated problem statement per sprint by Month 3.

Near Enemy Watch:

• Customer Obsession vs. Customer Obedience. A great PM synthesizes customer input into insight. A weak one builds exactly what customers ask for — which is rarely what they need.
• Decisiveness vs. Bulldozing. Speed matters. But a PM who ships fast by overriding engineering concerns isn't decisive — they're creating technical debt and resentment.

What You'll Find

The first time you write a Scorecard, two things will hit you.

You'll realize how vague your expectations actually are. "Manage the team" and "drive growth" sound clear in your head. When you try to write a binary outcome — From X to Y by Date — the fog becomes obvious. Most founders discover they've been managing to feelings, not standards. The Scorecard doesn't let you hide from that.

The second thing is harder. The Near Enemy filter will rewrite the story of your past hires. That "driven" salesperson who flamed out wasn't driven — they were reckless. That "detail-oriented" ops hire who ground everything to a halt wasn't precise — they were paralyzed. You'll start seeing the shadows everywhere. It changes how you interview. It changes how you coach. It changes which "red flags" you actually pay attention to versus the ones you've been ignoring because the candidate seemed impressive.

Adaptations

You're hiring your first employee. Skip the Alignment Cycle — there's no boss or peer to send it to. But write the Scorecard anyway, especially the Near Enemy filter. When your team is one person, a bad hire isn't a setback. It's an existential threat. The 15-Minute Flash Draft plus two named near enemies will do more for your hiring accuracy than any recruiter or job board.

You already have a team and want to use this for performance management. Take each current role and reverse-engineer a Scorecard from what the person is actually doing versus what you wish they were doing. The gap between those two documents is your next performance conversation. Share the Scorecard with the employee. Let them react. The best people will welcome the clarity. The wrong people will resist it. Both responses are information.

You're scaling fast and hiring 5+ people per quarter. Build a Scorecard library. Every role gets a living document that updates after every performance cycle. When someone exceeds expectations, reverse-engineer why and add those patterns to the Scorecard. When someone fails, identify which near enemy slipped through the filter. The Scorecard sharpens with every hire and every exit.

Where This Came From

The Scorecard methodology comes from Geoff Smart and Randy Street's Who — built on thousands of data points showing that structured, outcome-based hiring outperforms gut-feel hiring by a wide margin. The Near Enemy concept comes from Buddhist psychology, where it describes a quality that mimics a virtue but operates as its opposite (sympathy masquerading as empathy, perfectionism disguised as high standards). Combining the two came from watching the same pattern across dozens of founder clients: they kept hiring the shadow of what they wanted, and no amount of "culture fit" interviewing caught it.

Related Protocols

• The Herb Brooks Protocol — The story behind the philosophy. Why Herb Brooks cut the most talented players in America to build the greatest team in Olympic history — and what that means for how you select your people.
• The Values Discovery Protocol — Before you can write the Cultural DNA section of a Scorecard, you need to know what your values actually are. This protocol mines them from reality instead of aspiration.
• The Context Transfer Protocol — Once you've hired the right person, this is how you transfer the knowledge in your head into theirs without losing six months to trial and error.