Why scenario planning fails and capability planning works

Most strategy offsites end with a deck. It contains three or four named futures: a base case, an optimistic case, a downturn, and the wildcard nobody quite believes in. The work that produced it was serious. The thinking was good. And then, some months later, a future arrives that resembles none of them, and the deck sits in a shared drive that nobody opens. This is not a failure of effort. It is a failure of method.

The problem is not bad prediction. It is prediction itself.

Scenario planning rests on a quiet assumption: that if we describe the plausible futures well enough, we will be ready for the one that comes. The assumption is reasonable and almost always wrong. The futures that actually test an organisation tend to arrive in combinations nobody modelled, on timelines nobody set, and through second-order effects that no scenario captured. A supply shock arrives at the same time as a funding squeeze and a key departure. The named scenario described one of those. The real situation is all three at once, plus something genuinely new.

This is not an argument against thinking about the future. It is an argument against a specific way of doing it. When the value of the work is locked inside a prediction, the work expires the moment the prediction misses. And predictions about a complex, fast-moving environment miss more often than they hit.

There is a deeper issue. Scenario planning produces a document. Documents do not respond to anything. When the unexpected hits, the organisation does not consult its scenario deck. It turns to its people, and watches what those people do under load. The decisive variable is never the quality of the forecast. It is the quality of the response. Yet most planning investment goes into the forecast and almost none into the responder.

That is the reframe this piece argues for. Stop trying to predict the future with more precision. Start building the capability to meet whatever future shows up. The first is a guess that ages badly. The second is an asset that compounds.

Two ways to spend the same planning budget

It helps to put the two approaches side by side, because they consume the same time, attention, and money, and they produce very different returns.

Scenario planning asks: what might happen, and what would we do in each case? It generates named futures, contingency plans, and trigger points. Its output is a document. Its half-life is short, because it is tied to a particular reading of the environment, and the environment moves.

Capability planning asks: whatever happens, what must our leaders and teams be able to do? It generates a clear picture of the judgement, agility, and composure the organisation will need, and a deliberate plan to build them. Its output is people who respond well. Its half-life is long, because the underlying capability holds across conditions the plan never anticipated.

The distinction is not that one looks forward and the other does not. Both are about the future. The distinction is in what they treat as the unit of readiness. Scenario planning treats the future itself as the thing to get right. Capability planning treats the responder as the thing to get right, and accepts that the future is, in the end, unknowable.

This matters most for boards and owners, who carry the real cost of the difference. A scenario deck is cheap to produce and expensive to rely on, because it creates a feeling of preparedness that the first genuine surprise dissolves. Capability is expensive to build and cheap to rely on, because it is there when the surprise arrives, in whatever form it takes. We have written more on the specific durable capabilities in a companion piece on future-ready leadership capabilities.

What capability planning actually involves

Capability planning is not vaguer than scenario planning. It is more concrete, because it deals with something you can observe and develop rather than something you can only guess at. CapabilityFX's work in this area is grounded in Dr Eric Albertini's doctoral research into how leaders actually change, and it organises the work around a clear sequence.

Name the capabilities the conditions will demand

The first move is to be specific about what the organisation will need its leaders to be able to do, regardless of which future arrives. Not vocabulary. Not this year's tools. The structural capabilities: reading a novel situation accurately, holding ambiguity without freezing, learning fast from what goes wrong, and staying settled when the stakes are high. These do not date the way a scenario does, because they are demanded by every kind of disruption, not one named version of it.

Measure where you actually stand

A plan to build capability is speculative until you know the current baseline. This is where measurement earns its place. The most rigorous instrument CapabilityFX works with for this is Tomorrows Compass's future-readiness assessment, which directly measures the capabilities most relevant to performance under novel and complex conditions. CapabilityFX is a licensed distributor of that assessment, not the owner of the underlying methodology. The point of measuring is not a score. It is to replace an anecdotal sense of readiness with an evidence-based one: where the leadership base is strong, where it is thin relative to the demands ahead, and where development investment will do the most good. You can find more on the assessments CapabilityFX uses.

Develop the responder, not the response

The final move is the development work itself, and it is the part scenario planning has no equivalent for. The 4D method that CapabilityFX applies is designed to build capability at the level of the whole leader, not to rehearse answers to hypothetical situations. The distinction is the same one that separates the two planning approaches. Rehearsing a response prepares you for the situation you rehearsed. Building the capability prepares you for the situation you could not have rehearsed, which is the only kind that really tests an organisation. This is what is meant by change that happens at the level of who a leader is, an idea explored more fully through the DUAL model (Discover, Understand, Accept, Lead).

None of this means an organisation should never sketch a scenario. A scenario is a useful prompt for a conversation. It becomes a liability only when it is mistaken for the plan, and the deck becomes the deliverable instead of the development.

What it looks like in practice

A regional operations director at a logistics firm had inherited a thick contingency playbook. It modelled fuel-price spikes, a port closure, and a major customer loss, each with a documented response. When disruption finally came, it was a combination none of the pages anticipated: a smaller customer loss than the worst case, alongside a labour dispute and a sudden regulatory change, all inside the same quarter. The playbook offered three separate responses to three separate problems she did not have. What she actually faced was one entangled problem she had never seen. The observable behaviour under that load was telling. She kept returning to the playbook, looking for the page that fit, and the absence of a matching page left her hesitating where the situation needed a clear, provisional decision. The plan had trained her to match situations to pre-written answers. It had not built the capability to act well when no answer was pre-written.

Contrast that with a divisional managing director at a manufacturing business whose organisation had spent two years on capability rather than contingency. The same kind of multi-stranded disruption arrived. He had no playbook page for it either, and did not look for one. The observable behaviour was different in a way the board noticed. He convened his team early, said plainly that the situation was new and that their first reading was probably incomplete, and set a short cycle of decide, watch, revise rather than waiting for a clarity that was not coming. He was wrong about one important thing in the first week, caught it because he had built in the habit of looking for disconfirmation, and corrected it before it compounded. Nobody had predicted this disruption. He did not need them to have predicted it. The capability to meet an unpredicted situation had been built deliberately, and it held.

The contrast is the whole argument in miniature. The first organisation had invested in describing futures. The second had invested in the people who would meet them. Both faced something nobody saw coming. Only one was ready, and readiness, it turned out, was never about having seen it coming. Readiness is a property of leaders and teams, and it can be built on purpose. We have written more on the collective version of this in a piece on the future-ready leadership team.

Questions for boards and owners

Before the next strategy cycle, it is worth asking a different set of questions than the usual ones about which future is most likely.

On where the budget goes. What proportion of our planning investment produces documents about possible futures, and what proportion produces leaders who can respond to any of them? If the honest answer is heavily weighted towards the former, the spend is going into the thing that expires rather than the thing that compounds.

On what we actually rely on. When the last genuine surprise hit, did we consult a plan, or did we depend on how specific people responded? If it was the latter, and it usually is, how deliberately are we building that response capability rather than leaving it to chance and hiring?

On evidence. Do we know the shape of our senior team's capability, with evidence, or only by reputation and track record? Can we say where readiness is strong and where it is thin, or are we inferring it from how people performed in conditions that no longer apply?

These are not rhetorical. They are the practical starting point for shifting investment from prediction to preparation. The use cases page sets out what that shift has looked like for organisations that have made it.

Plan for the responder, not the future

The future will not arrive as forecast. It never has. The organisations that come through disruption well are not the ones with the best predictions. They are the ones whose leaders and teams can meet a genuinely new situation without fragmenting. That capability is buildable, measurable, and durable, which is more than can be said for any scenario deck.

If your board or leadership team wants to move from predicting futures to building the capability that meets them, the assessments page is the right place to begin, or you can contact us to talk through what a capability-led approach would look like in your context.

The leaders and organisations described here are representative composites drawn from patterns we observe in practice, not identifiable individuals.