Sales Leader Guide· a Bicycle Guide

An on-ramp · for aspiring practitioners building toward this role

Hire the Right People

A method for turning hiring from a gut-feel gamble into a repeatable, evidence-based decision

This guide is for a founder or manager who is about to make hires that matter and knows, honestly, that they don't yet do this well. You may have hired on instinct, on a good conversation, on a strong résumé — and been burned. The through-line here is a causal chain the corpus agrees on: define the role before you look at anyone, build a consistent way to gather evidence, capture what candidates actually said and did, and let that evidence — not your impression of it — drive the decision. Get that chain right and the business outcomes follow: fewer mis-hires, lower turnover cost, higher workforce performance. The three books behind this guide come at the same pathway from two angles — a practitioner's method ('Who') and two measurement-science treatments (Hiring Success; A Practical Guide to Assessment Centres). Where they reinforce each other, this guide states it plainly. Where they genuinely differ — intuition versus psychometrics, single-book claims about fairness and bias — it says so, and tells you how to choose for your situation.

Reconciled from 3 books · 6 core ideas · 3 cited sources

A founder or hiring manager who must make consequential hires and suspects their current approach is closer to guessing than to method.. Mis-hires are expensive — in turnover cost, lost performance, and the drag of carrying the wrong person — and the usual hiring ritual (résumé plus unstructured conversation) does not reliably predict who will deliver. They don't trust their own judgment about people, and they can't tell whether a candidate impressed them because they'll do the job or because they interview well.

Where this takes you. You move from an anxious interviewer trusting your gut to a disciplined evaluator whose confidence in a hire rests on evidence you can point to.

The model

Not a tip list — the system underneath. These are the forces the canon agrees drive the outcome, and how they connect. Each links to its section.

Role Definition & Competence FrameStructured Assessment & Activity DObservable Evidence & Truthful DisAssessment / Criterion ValidityBusiness & Financial OutcomesOUTCOME
enablesproduces

How they connect

  • Role Definition & Competence Framework Clarity→enables→Observable Evidence & Truthful Disclosure
  • Structured Assessment & Activity Design Quality→produces→Assessment / Criterion Validity
  • Structured Assessment & Activity Design Quality→produces→Observable Evidence & Truthful Disclosure
  • Observable Evidence & Truthful Disclosure→produces→Assessment / Criterion Validity
  • Assessment / Criterion Validity→produces→Business & Financial Outcomes

The journey

  1. 1

    FoundationsFlat Roads

    Every open role has a written definition — mission, ranked outcomes, observable competencies — before anyone is interviewed, and you interview against it rather than around it.

  2. 2

    PractitionerUphill Climbs

    You run a consistent, standardized process across candidates, source a real pool rather than settling for the first plausible person, and capture facts about what candidates did instead of how they made you feel.

  3. 3

    AdvancedThe Summit

    You know which of your methods actually predict performance and tenure, you can defend the process on fairness and reliability grounds, and you can tie hiring quality to business outcomes like turnover cost and workforce performance.

The path

  1. 01Role Definition & Competence Framework Clarity — Nothing downstream works without it — you cannot gather relevant evidence or judge a candidate against a target you haven't defined. It is the root of the causal chain.
  2. 02Structured Assessment & Activity Design Quality — Once the role is defined, the next move is building the consistent methods that turn that definition into comparable candidate evidence. It produces both validity and evidence.
  3. 03Systematic Sourcing & Candidate Pool — A good process on a thin pool still fails. You need enough qualified candidates to actually choose, so sourcing sits alongside process design early in the journey.
  4. 04Observable Evidence & Truthful Disclosure — The design exists to elicit and record what candidates actually said and did. This is where the process either captures facts or collects impressions.
  5. 05Assessment / Criterion Validity — Evidence and design only pay off if they predict future performance. Validity is the check on whether your method measures what matters — the measurement-science fulcrum.
  6. 06Business & Financial Outcomes — The end of the chain: valid, evidence-based hiring produces the results that justify the effort — lower turnover cost, higher performance, competitive advantage.

Foundations

Role Definition & Competence Framework Clarity

Before you look at a single candidate, write the role down. Across all three books this is the foundation: a role defined by a plain-language mission (why the job exists), a set of ranked, measurable outcomes (what success looks like, in order of importance), and specific, observable, job-relevant competencies and behaviour indicators tied to the strategy. 'Who' calls this the scorecard; the assessment books arrive at the same place through job analysis. The point is identical — you are converting a vague 'we need someone good' into a concrete target that later evidence can be measured against. The corpus is explicit that this definition enables everything downstream: it is what makes evidence capture possible, because you cannot record job-relevant facts about a candidate until you have said what the job actually requires.

Why it matters. Skip this and the rest of the process floats. If the role isn't defined, every interviewer is measuring the candidate against a private, unstated picture of the job — and you end up debating impressions instead of comparing evidence. The concrete consequence is the mis-hire you can't explain: someone who interviewed well against no fixed standard, then failed to deliver outcomes nobody had written down.

MisconceptionA job description is the same as a role definition, so I already have this covered.

RealityA typical job description lists duties and required experience. What the corpus asks for is different: a mission, ranked measurable outcomes, and observable competencies aligned to strategy. Outcomes ('grow renewals from 70% to 85% in year one') are testable; a list of responsibilities is not.

MisconceptionI'll know the right person when I meet them — defining the role in advance is bureaucratic overhead.

RealityKnowing it when you see it is exactly the failure mode the definition prevents. Without ranked outcomes and observable competencies fixed in advance, 'the right person' becomes whoever most resembles you or interviews most smoothly. The definition is what gives your later judgment something objective to attach to.

How to

  1. 1Write a one-sentence mission for the role: why it exists and what it must accomplish.
  2. 2List the outcomes — the specific, measurable results the person must deliver — and rank them, so it is clear which matter most when a candidate is strong on some and weak on others.
  3. 3Translate the strategy into observable competencies and behaviour indicators: not 'good communicator' but the specific, watchable behaviours that would show it in this job.
  4. 4Ground the competencies in what the job actually requires (job analysis), so you are not importing a generic template that fits no real role.
  5. 5Circulate the definition to everyone who will interview, and hold them to assessing against it — the definition only works if the whole panel uses the same one.

Watch out for

  • —Competencies written as vague traits ('leadership', 'drive') rather than observable behaviours — these invite each assessor to fill in their own meaning.
  • —Unranked outcomes: when everything is equally important, nothing is, and candidates get judged on whatever the interviewer happened to care about that day.
  • —Copying a competence framework from elsewhere without checking it against this specific role's real demands.

Grounded inWho: The A Method for Hiring · Hiring Success The Art And Science Of Staffing Ass · A Practical Guide to Assessment Centres and Selection Methods

Practitioner

Structured Assessment & Activity Design Quality

With the role defined, build a consistent, standardized way to assess candidates against it. All three books converge here: structured interviews with the same questions asked of every candidate, valid work-sample activities that mirror the actual job, and assessments built from the job analysis rather than improvised. The design's job is to produce comparable evidence — data you can hold up side by side across candidates — and, per the relationships in the corpus, it directly produces two things: assessment validity (methods that predict) and evidence capture (facts about what candidates did). The discipline is consistency: everyone goes through the same process so differences you observe are differences in candidates, not differences in how they were treated.

Why it matters. An unstructured process quietly destroys comparability. If each candidate gets a different conversation, you have no basis for saying one is stronger — you're comparing your mood on Tuesday to your mood on Thursday. The consequence is a decision that feels informed but rests on noise, and a process you can't defend or improve because it was never the same twice.

MisconceptionFree-flowing conversation lets me read the real person; a script makes it stiff and artificial.

RealityThe corpus treats standardization as the source of comparable, fact-based evidence, not a constraint on insight. Structure is what lets you compare candidates fairly; the unstructured chat mostly measures rapport, which the person you liked will always win.

MisconceptionAny interview is roughly as good as any other — it's mostly about asking smart questions.

RealityThe books draw a sharp line: methods built from job analysis and applied consistently produce evidence that predicts, while ad-hoc methods produce evidence that doesn't. Design quality is the variable, not interviewer cleverness.

How to

  1. 1Derive every assessment method from the role definition — each interview question, exercise, and work sample should map to a specific outcome or competency.
  2. 2Standardize: same core questions, same activities, same evaluation criteria for every candidate for a given role.
  3. 3Use work-sample activities that resemble the real job — put candidates in situations close to what they'll actually do, so the evidence transfers.
  4. 4Decide in advance how each method will be scored against the competencies, so evaluation is fact-based rather than reconstructed after the fact.
  5. 5Keep the process consistent across evaluators — brief everyone on the same criteria before they assess anyone.

Watch out for

  • —Letting a strong candidate 'take over' the interview so the standard questions never get asked — you lose comparability exactly when it matters.
  • —Adding methods for their own sake; each one should earn its place by measuring a defined outcome or competency, not by looking rigorous.
  • —Designing activities that test general polish rather than the specific job — face-valid theatre that predicts nothing.

Grounded inWho: The A Method for Hiring · Hiring Success The Art And Science Of Staffing Ass · A Practical Guide to Assessment Centres and Selection Methods

Practitioner

Systematic Sourcing & Candidate Pool

A disciplined process applied to a thin pool still produces a weak hire — you can only pick the best of who showed up. Two of the three books ('Who' and Hiring Success) treat sourcing as its own lever: the deliberate generation of high-quality candidate flow through referrals and personal networks, and the size and quality of the eligible pool you actually consider per opening. The move is to stop treating hiring as a passive intake of applicants and start treating it as active generation of qualified candidates, so that when your structured process runs, it runs on a real field of contenders.

Why it matters. If you only ever choose among the two or three people who applied, your beautifully defined role and consistent process are wasted — the ceiling on your hire is set by the pool, not the process. The consequence of neglecting sourcing is the 'least-bad' hire: you followed method and still settled, because there was no one strong to choose from.

MisconceptionPost the job, and the good candidates will apply.

RealityThe corpus emphasizes systematic sourcing — referrals and networks — precisely because the strongest candidates are often not actively applying. Waiting for inbound applications selects for availability, not quality.

MisconceptionMore applicants is the goal.

RealityThe construct is pool size and quality — a large pile of unqualified résumés is not a better pool. The aim is a sufficient number of genuinely eligible candidates per opening, generated deliberately.

How to

  1. 1Ask your best people who they'd hire — referrals from strong performers are the corpus's primary sourcing channel.
  2. 2Work your networks continuously, not only when a seat opens, so you have candidates to consider rather than a cold start each time.
  3. 3Track how many eligible candidates you're actually considering per opening, and treat a thin field as a signal to source harder before deciding.
  4. 4Filter the flow against the role definition early, so you're building a pool of qualified contenders rather than raw volume.

Watch out for

  • —Confusing activity (many applicants) with a strong pool (enough qualified ones).
  • —Only sourcing under time pressure once the role is already vacant, which pushes you toward whoever is available now.
  • —Letting a narrow network reproduce the same profile of candidate every time.

Grounded inWho: The A Method for Hiring · Hiring Success The Art And Science Of Staffing Ass

Practitioner

Observable Evidence & Truthful Disclosure

This is the point of the whole design: eliciting and recording accurate, complete data on what candidates actually said and did — including their weaknesses, failures, and the unflattering parts — rather than inferred internal states or self-serving accounts. 'Who' and the assessment-centre book both insist on the distinction between behaviour and impression: what someone did is evidence; what you sensed about them is not. The corpus places this squarely in the chain — role definition enables it, structured design produces it, and it in turn produces validity. In practice it means pushing past rehearsed answers to get the real record: specific situations, specific actions, specific outcomes, and honest disclosure of what went wrong.

Why it matters. Most interview failure lives here. Interviewers collect impressions ('seemed sharp', 'good energy') and mistake them for evidence, or they accept a candidate's polished narrative at face value. The consequence is a decision built on stories the candidate wanted to tell rather than facts about how they actually perform — which is exactly how confident hiring decisions turn into surprises.

MisconceptionIf I get a good feeling about someone, that intuition is real signal.

RealityThe corpus separates observable behaviour from inferred internal states and treats only the former as evidence. A feeling is not a fact about performance; it's a fact about your reaction. The process exists to record what candidates did, not how they made you feel.

MisconceptionCandidates will tell me their real weaknesses if I ask.

RealityTruthful disclosure has to be worked for — self-serving accounts are the default. The construct explicitly includes surfacing weaknesses and failures, which means asking for specific instances and following up until you have the actual record, not a curated version.

How to

  1. 1Ask for specifics: what was the situation, what did you actually do, what happened — real events over general claims.
  2. 2Probe for weaknesses and failures directly, and don't accept the polished non-answer; the process is designed to elicit the unflattering record, not just the highlight reel.
  3. 3Write down what candidates said and did as facts, keeping your interpretations separate from the observations.
  4. 4Compare candidates on the recorded evidence against the role's competencies, not on remembered impressions.
  5. 5Where you can, corroborate the candidate's account (references, work samples) rather than relying on self-report alone.

Watch out for

  • —Letting a compelling story substitute for verifiable behaviour — charisma reads as competence if you let it.
  • —Recording conclusions ('strong leader') instead of observations ('led a team of six through a reorg, retained five') — the conclusion hides the missing evidence.
  • —Accepting the first weakness the candidate offers, which is usually the safe rehearsed one, and not digging for the real record.

Grounded inWho: The A Method for Hiring · A Practical Guide to Assessment Centres and Selection Methods

Advanced

Assessment / Criterion Validity

Validity is the question the measurement-science books put at the centre: does your selection method actually measure job-relevant attributes and predict future job performance and tenure? This is where the two assessment books (Hiring Success; A Practical Guide to Assessment Centres) diverge in emphasis from 'Who' — they make criterion validity and reliability the explicit fulcrum, whereas 'Who' treats the same predictive quality implicitly through the discipline of its method. In the reconciled chain, structured design and captured evidence both produce validity, and validity in turn produces business outcomes. The practical meaning: a method is only worth running if it predicts. A polished process that doesn't forecast performance is expensive theatre.

Why it matters. You can run a consistent, evidence-based process and still be measuring the wrong thing well. Validity is the check that separates a method that predicts from one that merely feels rigorous. Getting this wrong means you confidently, repeatably hire people who look right on your criteria and then don't perform — the failure is invisible until it compounds across many hires.

MisconceptionIf a method is structured and fair-looking, it must be predictive.

RealityConsistency and validity are different properties. A method can be perfectly standardized and still fail to predict performance. The assessment books insist you check criterion validity — whether scores actually relate to later job performance and tenure — separately from whether the process was consistent.

MisconceptionFace validity — the candidate and manager feeling the assessment was relevant — tells me the assessment works.

RealityLooking job-relevant and being predictive are not the same. The corpus distinguishes face validity (perceived relevance) from criterion validity (measured prediction). An exercise can look convincing to everyone and still not forecast who succeeds.

How to

  1. 1Choose methods with an eye to whether they predict performance and tenure, not only whether they seem relevant.
  2. 2Where you have the volume, track whether your assessment scores actually relate to later job performance — close the loop between prediction and result.
  3. 3Attend to reliability: a method that gives inconsistent results across assessors or occasions can't be valid, so consistency of measurement is a prerequisite.
  4. 4Prefer methods grounded in job analysis, since job-relevance is the basis on which validity is built.
  5. 5Retire or rebuild methods that don't earn their keep in prediction, however professional they look.

Watch out for

  • —Treating standardization as proof of prediction — they're different tests.
  • —Never checking whether your assessments relate to actual performance, so a non-predictive method survives indefinitely.
  • —Assuming the practitioner-method framing means validity doesn't need attention — 'Who' folds it into discipline, but the science books are right that it deserves an explicit check where you can run one.

Grounded inHiring Success The Art And Science Of Staffing Ass · A Practical Guide to Assessment Centres and Selection Methods

Advanced

Business & Financial Outcomes

The end of the chain and the reason for the effort. All three books connect higher-quality hiring to downstream results: value creation and profitability, reduced turnover costs, competitive advantage, and — in the measurement books — utility net of the cost of assessment. Validity produces these outcomes in the reconciled model: methods that predict performance and tenure lead to more high performers hired, fewer failures carried, and lower churn. This is also where the case for the whole discipline gets made — the assessment books' concept of utility asks whether the value gained from better selection exceeds what the process costs to run.

Why it matters. Without connecting to outcomes, hiring discipline reads as overhead — process for its own sake. The corpus's answer is that the payoff is financial and organizational: the cost of a mis-hire (turnover, lost performance, replacement) is what all this machinery is buying down. Ignore the outcomes and you either under-invest in a process that would pay for itself, or over-invest in assessment that costs more than it returns.

MisconceptionBetter hiring is a nice-to-have that HR cares about but that doesn't move the business.

RealityThe corpus ties hiring quality directly to value creation, profitability, reduced turnover cost, and competitive advantage. Mis-hires are a real cost line; higher-quality hiring is how you reduce it.

MisconceptionMore assessment is always better.

RealityThe utility concept says otherwise — the value of better selection has to exceed the cost of the assessment that produced it. There's a point where additional process costs more than the improvement in hire quality returns.

How to

  1. 1Frame the investment in hiring discipline against the cost of a mis-hire — turnover, lost performance, replacement — so the effort has a business justification.
  2. 2Weigh the cost of your assessment process against the value it produces in better hires (utility), and keep the process proportionate to the stakes of the role.
  3. 3Track turnover and performance of hires over time as the outcome signal that tells you whether the process is working.
  4. 4Invest most in getting the highest-stakes roles right, where the return on better selection is largest.

Watch out for

  • —Running heavy assessment on low-stakes roles where the cost outweighs the benefit.
  • —Never measuring turnover or performance, so you can't tell whether the process is producing the outcomes that justify it.
  • —Treating the process as an end in itself rather than as a means to fewer, cheaper mistakes.

Grounded inWho: The A Method for Hiring · Hiring Success The Art And Science Of Staffing Ass · A Practical Guide to Assessment Centres and Selection Methods

Where the canon disagrees

We don’t flatten these into a single answer. Here are the real camps and how to choose for your situation.

Practitioner heuristic vs. measurement science: what is the real fulcrum of good hiring?

  • ▸ 'Who' frames the causal core as scorecard → sourcing/selection → evaluator confidence → A-player hire, treating validity implicitly inside the discipline of the method.
  • ▸ The two assessment books make psychometric criterion validity and reliability the explicit causal fulcrum — the same latent pathway, named as measurement science.

How to choose. These are two descriptions of the same chain, not a real contradiction about what to do — both agree you define the role, gather comparable evidence, and let it predict. Choose by your situation. If you're a founder hiring in low volume and can't run statistics, 'Who's' practitioner framing is directly usable and its discipline gets you most of the validity implicitly. If you hire at volume or must justify methods formally, adopt the assessment books' explicit validity-and-reliability checks — you have the data to close the loop and the exposure that makes it worth doing. Consensus level: wide-consensus on the pathway, contested only on emphasis.

How to operationalize decision accuracy: evaluator confidence vs. measured prediction.

  • ▸ 'Who' operationalizes the decision as evaluator psychological confidence — a threshold (around 90%) that this candidate will deliver the outcomes.
  • ▸ The assessment books model decision accuracy as a mediator/outcome measured against actual performance, not as felt confidence.

How to choose. Reconciled as one construct, but the science-vs-intuition operationalization genuinely differs. The safe practice takes from both: use the assessment books' insistence that the decision rest on evidence that actually predicts, and use 'Who's' confidence threshold as a discipline that stops you hiring while you still have doubt — but only when that confidence is built on captured facts, not on a good feeling. Confidence untethered from evidence is exactly the failure mode this guide warns against. Consensus level: contested on operationalization, agreed on the underlying aim.

Fairness, legal defensibility, assessor bias, and psychometric governance — settled or single-source?

  • ▸ The assessment-centre book asserts these strongly and treats them as central to a defensible process.
  • ▸ The other two books do not develop them.

How to choose. This is a single-book claim, so weigh it by evidence strength: it rests on one source rather than corpus-wide agreement, which makes it a candidate rather than established consensus here. That does not make it wrong — bias, reliability, and legal defensibility are real risks, and the assessment-centre book's treatment is coherent. The honest read: take fairness and reliability seriously, especially where hiring is regulated or high-volume, but recognize that this guide's corpus supports it from one direction only. A stronger claim about how much these move outcomes would need evidence the other books don't supply. Consensus level: outlier (single-book), high centrality within that book.

Which way does candidate experience flow — downstream reaction, or moderator of decision accuracy?

  • ▸ The assessment books treat candidate reactions and face validity as causally downstream — a reaction to how the process was designed.
  • ▸ The same books also treat candidate experience as a moderator of decision accuracy, influencing the quality of the decision.

How to choose. The direction of influence is not fully agreed even within the source material. Practically, treat it as both: design a process candidates perceive as fair, relevant, and not excessively invasive because that's downstream of good design and worth doing on its own terms — and be aware it may also affect how well candidates engage and therefore the evidence you get. Don't let concern for candidate comfort override validity, but don't ignore experience either, since it may be quietly shaping your data. Consensus level: contested (direction unresolved within-source).

The sources

This guide is a cross-source synthesis. Want one source on its own? Each book below stands alone — open its profile to go deeper into a single voice.