Talent Signal Framework™

A credential is evidence that someone passed the selection process for the institution that granted it. It is not evidence of capability. The two are correlated, and the selection process has some signal, but the correlation is weaker than most hiring decisions assume, and it degrades significantly when the selection process being proxied for is different from the role being filled.

The person who got into a top MBA programme is demonstrably good at getting into top MBA programmes. Whether they are good at building and running a VP-level function at a 200-person SaaS company is a different question, and the credential answers it only partially.

Most hiring processes spend significant evaluation time on credentials and limited time on the signals that are actually predictive. The Talent Signal Framework inverts this. It maps five signals that genuinely predict exceptional performance and explains why each is a better predictor than the proxies that typically dominate hiring decisions.

The five signals

```

SIGNAL 1: FIRST-PRINCIPLES REASONING

↓

[Can the person work from territory

when the map doesn't exist?]

SIGNAL 2: OUTCOME SPECIFICITY

↓

[Can they describe what they personally

did, with evidence, not what the team did?]

SIGNAL 3: CONSTRAINT NAVIGATION

↓

[What have they built or solved under

conditions that weren't ideal?]

SIGNAL 4: CALIBRATED SELF-ASSESSMENT

↓

[Do they know where they're strong

and where they're not, accurately?]

SIGNAL 5: SPEED OF LEARNING

[How quickly do they acquire new domains?

What is the evidence?]

```

Signal 1: First-Principles Reasoning

First-principles reasoning is the ability to work from the actual structure of a problem when established procedures don't apply. It is the capacity to break a problem down to its component parts, reason from those parts, and construct a solution without relying on what has been done before.

This is not the same as creativity or intelligence in a general sense. It is a specific operational capability, distinct from the ability to execute well-established procedures, which is what most formal education systems primarily develop.

How to surface it: Ask the candidate to walk through how they approached a problem they had never seen before. Not how they solved it, but how they approached it. What did they identify as the real problem? What assumptions did they test? What did they rule out and why? The candidate who can describe this process clearly, with specific steps and specific reasoning, is demonstrating first-principles capability. The candidate who describes the solution without the reasoning may have gotten lucky or may have followed a template.

Why credentials don't capture it: The selection processes for most elite institutions test for first-principles reasoning to some degree, the kind that appears in case interviews, standardised tests, and structured problem sets. But they test it in domains that are known in advance, under conditions that are far more structured than real operating environments. The candidate who is exceptional at this in a test environment but has never had to apply it without a framework may not perform at the level the credential implies.

What to look for: The candidate who, when faced with a question they haven't prepared for, slows down and thinks rather than reaching for a prepared answer. The slowing down is a signal, not a weakness.

Signal 2: Outcome Specificity

Outcome specificity is the ability to describe, in precise and verifiable terms, what the candidate personally did and what resulted from it.

Most candidates describe their experience in terms of team outcomes and shared achievements. "We grew revenue from $10M to $40M." "Our team shipped the product in six months." "The company was acquired for $200M." These statements may be true. They tell you almost nothing about what the candidate did.

The candidate with genuine capability in a given domain can describe their specific contribution with precision: what they did, when they did it, what the constraints were, what the result was, and what would have happened differently if they hadn't been there. This specificity is hard to fabricate and easy to verify.

How to surface it: Ask "what specifically did you do?" and then follow up on every vague answer. When the candidate says "we built the sales team," ask: "Who did you hire first? What was your criteria? What did you get wrong in the first round of hires?" The candidate who can answer these questions in detail was actually doing the work. The candidate who retreats to generalities or pivots to team credit may not have been.

Why this matters for executive search specifically: At the VP and C-suite level, candidates have often been part of several high-profile outcomes. The question is not whether they were present for those outcomes but whether they drove them. Outcome specificity is the test that distinguishes the driver from the passenger.

Signal 3: Constraint Navigation

Constraint navigation is what you learn about a candidate from what they built or solved when conditions weren't ideal.

The candidate who has only ever operated in well-resourced environments, large teams, adequate budgets, established playbooks, strong institutional support, has not been tested by constraint. They may be highly capable. But the specific capability that constraint navigation develops, resource substitution, creative problem-solving under pressure, and the ability to prioritise ruthlessly when you can't do everything, is absent from their track record.

This matters most at the VP level in early-to-mid stage companies, where the operating environment is routinely constrained and the playbook doesn't exist yet. The executive who has only ever hired from the playbook has not demonstrated that they can write it.

How to surface it: Ask about the hardest operating environment the candidate has worked in. Not the most prestigious, but the hardest. What were the constraints? How did they work around them? What did they have to give up? The candidate who has a real answer to this question, with specific detail, has been tested by constraint. The candidate whose hardest environment was still well-resourced has not.

A specific variation: Ask the candidate what they built that they're most proud of, and then ask: "What would you have done differently if you'd had twice the budget?" The answer reveals their relationship to constraint: whether it was the environment they learned from or the obstacle they've been trying to get past.

Signal 4: Calibrated Self-Assessment

Calibrated self-assessment is the ability to accurately describe one's own strengths and limitations, without over-claiming in either direction.

Under-claiming is the signal of a capable person who has learned to present modestly. Over-claiming is the signal of someone whose self-image has not been tested against reality, or who has learned to interview well without necessarily performing at the level the interview implies. Accurate calibration, the candidate who can say "I'm genuinely strong at X, adequate at Y, and I need support on Z", is rare and valuable.

How to surface it: Ask the candidate what they're not good at. Not what they're "working on", but what they are actually not good at, in a way that would be relevant to this role. Then watch what happens. The candidate who gives a real answer, with an example, has calibrated self-assessment. The candidate who turns the question into a strength in disguise ("I work too hard," "I care too much") has not.

A follow-up that reveals calibration: After the candidate describes a genuine weakness, ask: "How do you compensate for it?" The compensation strategy reveals whether they have actually worked with the limitation or are still performing awareness of it.

Signal 5: Speed of Learning

Speed of learning is how quickly a candidate acquires competence in a new domain, not how much they currently know in the domains they're already expert in.

This is the hardest signal to evaluate and one of the most predictive, particularly for roles where the operating environment is changing faster than any static knowledge base can keep up with. The candidate who can point to three or four domains they have become genuinely competent in over the course of their career, competent rather than merely familiar, is demonstrating a learning capability that will compound over time.

How to surface it: Ask the candidate about a domain they didn't know when they started a role and had to learn on the job. How did they approach the learning? What was the evidence that they had become competent? How long did it take? The candidate who can answer this with specificity, and who has done it multiple times, is demonstrating learning speed through track record rather than self-report.

What to distinguish: Learning speed is different from general intelligence and different from intellectual curiosity. Someone can be very intelligent and learn slowly in applied domains. Someone can be very curious and learn broadly but shallowly. The signal is domain competence acquired under time pressure, not the speed at which someone processes information in conversation.

How to use these signals in a hiring process

The five signals are most useful as an explicit evaluation framework, agreed by everyone in the process before interviews begin, with specific questions assigned to each signal and specific criteria for what constitutes strong vs. weak evidence.

The candidate who, when faced with a question they haven't prepared for, slows down and thinks rather than reaching for a prepared answer. The slowing down is a signal, not a weakness.

Without this structure, evaluators default to their implicit proxies: the candidate who speaks confidently, who has impressive logos on their CV, who reminds the interviewer of someone who was successful in a previous role. These proxies are comfortable and familiar. They are also the reason research consistently puts executive hire failure at 40–50% within 18 months, a figure that has barely moved in thirty years despite every tool improvement in between.

The signals don't replace judgement. They direct it toward the variables that actually predict performance.

That is a different conversation than the one most interviews have. It is also a more accurate one.

See also: Compounding Failure Loop™, Hiring SLO Framework™, Intelligence Hiring System™

Sources

Harvard Business Review: Structured Interviews Can Help You Choose the Best Candidate (2016)

Tomas Chamorro-Premuzic: Ace the Assessment (Harvard Business Review, 2015)

McKinsey: Talent Wins, The New Playbook for Putting People First