What Changes

The argument in the preceding chapters is not an argument against capability assessment. It is an argument about what capability assessment is for and what it cannot do when used without the contextual analysis that should precede it. Individual capability matters. The leader who cannot think strategically, build a team, drive execution, or communicate under pressure will fail in any organizational context. The tools that assess these capabilities (structured interviews, psychometric instruments, reference processes conducted with rigor) produce information that is genuinely useful. None of that changes.

What changes is the question those tools are organized around. The dominant model uses them to answer: who is most capable? Contextual assessment uses them to answer: whose capability profile best matches what this situation requires? The distinction sounds simple. In practice it is consequential.

The objection most commonly raised against contextual assessment by the people who use the dominant model is a reasonable one. Trait-based assessment claims objectivity through consistent measurement: the same competency framework, applied through the same structured process, produces scores that can be compared across candidates without the distortion of individual judgment. Contextual calibration introduces judgment at the criteria-setting stage: in the specification of the demand profile, in the weighting of different capabilities, in the determination of what counts as sufficient evidence for contextual fit. Is that a loss of rigor?

It is not. The apparent objectivity of the dominant model is achieved by measuring consistently, not by measuring the right thing for this decision. A process that applies the same framework to every senior leadership appointment will produce comparable scores. It will not produce scores that are valid for the contextual demand of each appointment, because the framework was not designed to capture that demand. Consistency in measurement is a virtue. Consistency in measuring the wrong thing is not the same as rigor.

Consistency in measuring the wrong thing is not the same as rigor.

The judgment that contextual assessment introduces is not new judgment. It is judgment that was always required: in specifying what the role actually demands, in weighting the evidence from assessment against what the context will require, in making the final appointment decision. In the dominant model, that judgment is made implicitly, after the formal assessment process, by the people who sit on the selection panel. Contextual assessment makes it explicit, structures it, and applies it before the assessment criteria are set rather than after they have been answered. That is not a loss of objectivity. It is an honest account of where the judgment in selection decisions actually resides.

The same argument extends beyond the selection moment, and this is where the implications of taking context seriously reach further than the appointment process.

Leadership development operates on the same portability assumption as leadership selection. Generic development programs, designed to build the capabilities that predict strong leadership performance across organizational contexts, are the development equivalent of generic competency frameworks. They build real capabilities. They build them in abstraction from the demand the leader is operating within, which means the investment is calibrated to what capable leadership looks like generally rather than what this leader needs to be able to do better in this situation at this point. Contextual thinking in development does not require building bespoke programs for every leader. It requires specifying the contextual demand clearly enough to identify which development investments will produce the greatest return for this leader in this role, and which represent generic capability building that looks valuable in the abstract and produces limited return in the specific situation.

Succession planning runs into the same problem from a different direction. Most organizations evaluate internal candidates against the requirements of the role as it currently exists, the same competency framework used for external selection, applied to an internal population. What this misses is the contextual demand of the role as it will exist when the succession actually occurs. The organizational context changes. The business cycle position at the point of succession may differ from the current position. The ownership dynamics may have shifted. The inflection point the incoming leader will face may be entirely different from the one the current leader navigated. Succession planning that does not account for the contextual demand at the point of transition is identifying the leader who is ready for the role as it is, not the role as it will be. The elements of contextual thinking exist in most succession processes: they appear in talent reviews, in development conversations, in the informal judgments senior leaders make about who is ready for what. Their status is the problem: context shapes the conversation without determining the criteria.

Onboarding and integration are where the demand profile, if it has been drawn, should generate the most direct return, and where it is most consistently unused. If the analysis has established that the most consequential risk in a given transition is the incoming leader's ability to establish relational legitimacy in a succession context, the integration plan should address that risk precisely. If the risk is holding investor confidence through a period of delayed evidence, the early warning indicators should track the external narrative, not just the operational milestones. A specified demand profile is a risk profile for the transition. That profile is almost never used to design the support structure for the incoming leader, because the work that would produce it was not done.

What changes most fundamentally is not the process but the conversation that precedes it. The board conversation about leadership has historically been organized around capability: who is available, who has the relevant experience, who has the strongest track record. Contextual assessment requires a different prior conversation, one organized around the demand: what does this situation actually require, what profile of leader can meet it, and how do we evaluate candidates against that profile rather than against a generic standard of leadership excellence?

That conversation is harder to have. It requires the board to be honest about the organizational condition, to specify what the incoming leader will actually face, and to own that specification as the basis for the appointment decision. It requires people in the process who understand the context well enough to evaluate fit within it. It requires the search firm to work from a demand profile rather than a role category.

None of this is technically demanding. It does not require specialized tools. It requires drawing the target before taking aim, and owning the demand profile as the basis for the decision, work the standard process makes no room for and the board is rarely asked to do.

The work is not hard to describe. It is hard to do in the open, where the target it draws can be judged.