McKinsey’s latest research on Strategy Champions contains a number that should stop any executive cold. Only 21 percent of companies believe their strategies are high quality. That figure has collapsed by 40 percent since 2010. Strategy is deteriorating at precisely the moment uncertainty has more than doubled and volatility spikes have grown more severe.

The research, which analyzed more than 400 companies with over $1 billion in revenue from 2019 to 2024, reveals a stark power curve. The top 20 percent of companies capture nearly 90 percent of all economic profit. The bottom 20 percent destroy value. And the gap between winners and losers has doubled over two decades. This is not a gentle distribution. It is a winner-take-all economy where mediocre strategy is a recipe for value destruction.

But the most revealing finding is not about outcomes. It is about what separates the winners from the rest. Strategy Champions, those that moved up to or maintained top-quintile economic profit performance, are not necessarily bolder in their strategic design, though they are stronger there too. The biggest differentiator is not in the quality of the plan. It is in what happens after the plan exists. Champions outperform stragglers by 20 percentage points on mobilization: the phase where strategy stops being a PowerPoint deck and becomes a way of working.

Mobilization means turning bold choices into specific initiatives with clear ownership. It means reallocating financial and human capital to match stated priorities. It means embedding strategic choices into plans and budgets rather than letting the budgeting process override them. Most companies do none of this well. They set priorities, then fund incremental initiatives. They talk transformation, then invest in the status quo. They claim boldness, then retreat to the familiar.

The result is what one can call the grey zone between potential and performance. The plan exists. Activity happens. But at the end of the year, the strategic trajectory of the company has not changed. That is the cost of failed mobilization. It is the cost of treating strategy as a document rather than a discipline.

The Deeper Problem

But the research, for all its diagnostic power, leaves the deeper question untouched. Why is mobilization so persistently difficult? Why do intelligent leaders, armed with clear plans, repeatedly fail to translate ambition into organizational reality?

The answer is that most organizations have built the wrong architecture for strategy. They treat strategy as an event, something that gets designed, approved, and then “rolled out” to an organization that is expected to execute it. Strategy Champions treat strategy as an organizational capability, something the company does continuously, not something it has periodically. This distinction explains the mobilization gap more powerfully than any prescription for better execution ever could.

Understanding this distinction is the first step. Building strategy as a capability is the second. What follows is a practical framework for doing both.

Part One: The Architecture of Strategy-as-Event

To understand why mobilization fails, you first have to see the invisible architecture that produces failure. In most organizations, strategy operates according to a set of embedded assumptions that are so familiar they have become invisible.

The calendar rules everything. Strategy has a season. It begins with a hypothesis-generation phase in the second quarter, intensifies through executive working sessions in the third, crystallizes into a board presentation in the fourth, and is ready for cascading to the organization in the first quarter of the new fiscal year. This rhythm is as predictable as budgeting, and in most companies, the two processes run on parallel tracks that occasionally intersect but never truly integrate.

Thinking is separated from doing. The strategy is designed by a small group: the executive team, supported by strategy professionals and often external consultants. The people who will execute the strategy are not in the room. They inherit conclusions without having worked through the reasoning. They are handed answers without having grappled with the questions. This produces compliance, not commitment. It generates activity, not ownership.

The strategy is a product. It arrives as a finished artifact: a deck, a document, a set of laminated cards with corporate priorities. It has the quality of something complete. The implication, intended or not, is that the hard thinking has been done. What remains is implementation. The organization’s job is to execute what has been decided.

Resource allocation is a separate process. The strategy sets out priorities. The budget allocates resources. And in the overwhelming majority of companies, the budget wins. The strategic plan says invest in digital transformation. The budget protects the legacy business because that is where this year’s revenue comes from. The strategy says build new capabilities. The budget funds incremental improvements to existing ones. The strategy says reallocate capital toward growth. The budget spreads resources across the portfolio in a pattern almost indistinguishable from last year.

The world is assumed to hold still. A strategy designed in September for the following fiscal year begins encountering realities that were not anticipated when it was conceived. A competitor makes a move. A technology shifts. A regulatory change opens or closes a door. But because the strategy is a finished product rather than a living framework, the organization lacks the machinery to adapt. People follow the plan even as the plan diverges from reality. Deviation feels like failure rather than responsiveness.

Every assumption in this architecture is wrong. Not slightly wrong. Fundamentally wrong. And yet this is how the vast majority of large organizations conduct strategy. The architecture is so deeply embedded in corporate calendars, board expectations, executive incentives, and organizational habits that it persists despite decades of evidence that it does not work.

The mobilization gap is not a failure of execution. It is a predictable consequence of an architecture that was never designed to mobilize anything.

Part Two: What Strategy-as-Capability Looks Like

A capability is something an organization can do repeatedly, at increasing levels of sophistication, across different conditions. It is not a deliverable. It is a proficiency. An organization with a genuine strategy capability does not just have a strategy. It is capable of strategizing continuously, at multiple levels, in ways that adapt to changing circumstances while maintaining coherence.

If strategy is an organizational capability, it has four defining characteristics.

It is distributed, not centralized

This does not mean everyone gets a vote on corporate strategy. It means that strategic judgment, the ability to frame problems, weigh trade-offs, make decisions under uncertainty, and learn from outcomes, is cultivated throughout the organization, not concentrated in the executive suite.

In organizations with this capability, people at every level can answer the question: “Given our strategic logic, what should I do in this situation?” They understand not just what the strategy says but why it says it. They know what trade-offs the organization is willing to make and which ones it is not. They have the conceptual tools to make strategically coherent decisions without escalating everything upward.

Nvidia’s “pilot in command” practice is a specific instance of this principle. The company assigns a single accountable leader to every major project or strategic decision, regardless of that person’s role or seniority. The pilot in command owns the outcome. They have the authority to make decisions. They carry the responsibility for results. Strategic authority sits with the person best positioned to exercise it, not necessarily the person highest in the hierarchy.

Most organizations claim to push decision-making down. Few actually do it. The difference is that Nvidia has built the systems to make it work: clear accountability, the right information flows, and leaders who are genuinely equipped to exercise strategic judgment rather than simply execute tasks.

It is continuous, not periodic

An organization with strategy as a capability does not have a strategy season. It has a strategy system that operates year-round. This system continually senses shifts in the environment, interprets their implications, makes resource allocation decisions, and learns from the outcomes of previous decisions.

In practice, this means resource allocation is not an annual event that locks in commitments for twelve months. It is a dynamic process where capital and talent flow toward opportunities as they emerge and away from initiatives that are not delivering. The budgeting process does not override strategic priorities because the two are fused into a single, ongoing activity.

This does not mean the organization has no plan. It means the plan is treated as a current best hypothesis, not a fixed commitment. The organization follows the logic of the strategy, but it updates the specifics as it learns. The difference is subtle but profound. In a strategy-as-event organization, sticking to the plan is a virtue. In a strategy-as-capability organization, sticking to a plan that is clearly wrong is a failure of responsibility.

It is learned, not declared

Strategic judgment is not an innate talent reserved for a few senior leaders. It is a set of disciplines that can be developed. Organizations that treat strategy as a capability invest in building these disciplines across their leadership population.

The core disciplines include: framing strategic questions in ways that open up possibilities rather than foreclosing them; structuring uncertainty so that leaders can act without pretending to know what they cannot know; making decisions with incomplete information without becoming paralyzed; separating decisions that are reversible from those that are not; and learning systematically from outcomes rather than explaining them away.

These are not mystical skills. They can be taught, practiced, and improved. But most organizations have never invested in building them beyond the most senior levels. The result is an organization full of people who can execute but cannot strategize, and a mobilization gap that is really a capability gap in disguise.

It is embedded in systems, not dependent on individuals

A capability does not collapse when a key leader leaves. It is institutionalized in processes, decision rights, information flows, and cultural norms. The organization does not just have a strategy; it has a strategy system.

This system specifies who has the authority to make which kinds of strategic decisions. It defines the information those decision-makers need and ensures they receive it. It creates forums where strategic issues are surfaced, debated, and resolved, not once a year, but as they arise. It links resource allocation to strategic logic in ways that are transparent and contestable. It makes the organization’s strategic reasoning visible so that it can be examined, challenged, and improved.

When this system exists, mobilization is not something you have to do after the strategy is complete. It is something that already happens because the organization is wired for it. The strategy lives in the system, not in the deck.

Part Three: Why This Reframes the Mobilization Problem

The McKinsey research identifies a 20-point mobilization gap between champions and stragglers. The conventional interpretation is straightforward: stragglers need to get better at executing their strategies. They need stronger follow-through, better program management, more disciplined tracking.

The strategy-as-capability interpretation is different. Stragglers are not failing to mobilize their strategy. They are failing to build the organizational capability that makes mobilization possible in the first place.

You cannot mobilize a strategy that was designed in isolation from the people who will carry it out. You can cascade it. You can communicate it. You can mandate compliance with it. But you cannot mobilize genuine commitment, discretionary effort, and adaptive execution around conclusions that people had no role in reaching.

You cannot mobilize resources when your resource allocation system is structurally disconnected from your strategic priorities. The annual budgeting process is a formidable piece of organizational machinery. It has its own logic, its own politics, its own gravitational pull toward the status quo. Unless strategy and resource allocation are integrated into a single system, the budget will win every time.

You cannot mobilize under uncertainty when your organization has never developed the muscle of making decisions without complete information. If the culture punishes the wrong bet more than it rewards the right one, people will wait for certainty that never arrives. They will conduct more analysis. They will seek more consensus. They will do everything except act, because action under uncertainty has never been modeled, taught, or rewarded.

This reframing also explains the grey zone between potential and performance. That zone is not a failure of execution in the conventional sense. It is what happens when an organization with a strategy-as-event architecture tries to operate in a world that demands strategy-as-capability. The plan exists. Activity happens. But the organization lacks the machinery to translate insight into action at scale and speed. The grey zone is the gap between knowing what to do and being organized to do it.

Part Four: Building Strategy as a Capability: An Actionable Framework

The question that follows is practical. If you are a leader who recognizes your organization in the description of strategy-as-event, what do you actually do? How do you begin building strategy as an organizational capability?

The answer is not to blow up your current strategy process and start over. That would be strategy-as-event thinking applied to the problem of strategy-as-event. The answer is to begin building the elements of the capability alongside, and eventually within, the existing architecture. Here is a framework organized around six specific actions, each of which can begin in the next quarter.

1. Redesign the strategy process around questions, not answers

The most immediate shift you can make is to change what your strategy process produces. Most processes are designed to converge on answers: a set of choices, a portfolio of initiatives, a financial plan. The output is a document that declares the organization’s direction. This is strategy as product.

Shift the emphasis to questions. What are the critical uncertainties that will determine our future? What hypotheses are we making about the market, our customers, and our competitive position? What would we need to believe to commit to this course of action? What would cause us to change our minds?

This is not a semantic change. It transforms the nature of the conversation. When the goal is answers, debate is about who is right. When the goal is questions, debate is about what we need to learn. The first produces defensiveness. The second produces inquiry. One closes down thinking. The other opens it up.

Actionable starting point: In your next strategy review, require every major initiative to be presented with an explicit statement of the hypotheses it depends on and the conditions under which you would stop funding it. Make this a standard part of the template, not a one-time exercise.

2. Fuse strategy and resource allocation into a single process

As long as strategy and budgeting operate on separate tracks, the budget will win. The only way to change this is to make them a single conversation. This does not necessarily mean abandoning the annual budget cycle, though that may be too disruptive a starting point. It means ensuring that strategic priorities drive resource allocation decisions, not the other way around.

Concretely, this requires several changes. First, the strategy conversation must happen before the budget is locked, not in parallel with it. Second, the strategic plan must specify resource requirements in enough detail that they can be translated into budget line items. Third, and most importantly, there must be a formal process for challenging budget submissions that are inconsistent with stated strategic priorities. Someone must have the authority to say: “This budget reflects last year’s strategy, not this year’s. Go back and rework it.”

Actionable starting point: Identify the three most significant resource allocation decisions in the current budget that are inconsistent with your stated strategy. Convene a meeting specifically to address them. Make the inconsistency explicit and force a decision: either change the allocation or change the strategy. But do not allow both to stand in contradiction.

3. Build strategic judgment across the leadership population

If strategy is to be distributed, the people making strategic decisions need to be equipped to do so. This requires deliberate investment in developing strategic judgment, not as a byproduct of experience but as a targeted capability-building effort.

What does this look like in practice? It means exposing a broader group of leaders to the strategic issues the company faces, not just the decisions that have been made about them. It means creating forums where leaders practice framing problems, structuring uncertainty, and making trade-offs, with coaching and feedback. It means rotating high-potential leaders through strategy roles, not as staff positions but as developmental experiences. It means rewarding people who demonstrate strategic judgment, not just those who deliver operational results.

This is not a training program. It is a commitment to building a capability across the organization, sustained over years. The companies that do this well treat it the way they treat building any other critical capability: with investment, intentionality, and patience.

Actionable starting point: Identify the next twenty leaders below your executive team, the people running business units, functions, and major geographies. Convene them for a half-day session. Present them with a real strategic dilemma the company faces, not a case study. Give them the same information the executive team has. Ask them to work through the problem and present their reasoning. You will learn two things: how much latent strategic capability exists in your organization, and how little of it you are currently using.

4. Create a strategy system, not just a strategy

A capability requires infrastructure. The infrastructure for strategy includes: a defined set of decision rights specifying who can make which strategic decisions; a rhythm of strategic conversations that operates year-round, not annually; information flows that surface data relevant to strategic choices; and forums where strategic issues are debated and resolved.

The specifics will vary by organization, but the principle is constant. If your strategy lives only in a document and in the minds of the executive team, you do not have a strategy system. You have a strategy that will be progressively diluted by the operational demands of running the business until it becomes indistinguishable from last year’s strategy.

Actionable starting point: Map your current strategy system. Identify every forum, meeting, and process where strategic issues are discussed. Note their frequency, their attendees, their decision rights, and their outputs. Most organizations will find that they have many strategy conversations and little strategic decision-making. The gap will be obvious. Close it.

5. Develop your organization’s conviction muscle

The McKinsey research highlights a critical finding: Strategy Champions act when uncertainty is highest. They invest through downturns. They build capabilities rather than chase headlines. They treat growth as something to be engineered rather than hoped for. This requires conviction, and conviction is not a personality trait. It is a capability that can be built.

Building conviction means learning to act without complete information. It means distinguishing between decisions that are reversible and those that are not, and moving faster on the former. It means treating strategic moves as experiments from which you intend to learn, not as bets you need to be right about. It means creating an environment where the cost of inaction is explicitly weighed against the risk of action.

For finance leaders specifically, this has direct implications. The EY Global DNA of the CFO Survey found that 60 percent of CFOs say they should define and shape how the business creates value, but only 25 percent lead investment decisions where returns are uncertain, indirect, or long-term. Closing that gap requires building the organizational capacity to evaluate and fund uncertain investments, not eliminating uncertainty, which is impossible, but operating effectively within it.

Actionable starting point: For your next major strategic decision, explicitly assess the cost of delay. Most business cases evaluate the cost of action. Few evaluate the cost of waiting. Require every significant investment proposal to include an analysis of what happens if you do not proceed, not just the opportunity cost, but the competitive, capability, and organizational costs of inaction. Make the cost of timidity visible.

6. Embed learning loops into strategic decision-making

A strategy is a set of hypotheses about how the organization will create value. Like all hypotheses, some will prove right and some will prove wrong. An organization with strategy as a capability learns from both outcomes systematically. It does not just review financial results. It reviews the quality of its strategic reasoning.

This requires a discipline that few organizations practice: revisiting past strategic decisions to understand what happened and why. Did we achieve what we expected? If not, was the strategy wrong or was the execution inadequate? Were our assumptions about the market correct? Did we make the right call with the information we had at the time? What would we do differently now?

Most organizations avoid this discipline because it surfaces uncomfortable truths. It reveals that some senior leaders made poor calls. It shows that some dearly held beliefs about the market were wrong. It demonstrates that the organization’s strategic reasoning is not as rigorous as it claims. That discomfort is precisely why the discipline matters.

Actionable starting point: Select two or three significant strategic decisions from three years ago. Convene the leaders who were involved in making them. Conduct an honest post-mortem: What did we assume? What actually happened? What would we decide today with the same information we had then? Do not use this to assign blame. Use it to improve the quality of your strategic reasoning. The goal is not accountability for the past. It is capability for the future.

The Hard Truth

This framework is practical, but it would be dishonest to suggest it is easy. Most organizations will not make the shift from strategy-as-event to strategy-as-capability. Not because the concepts are difficult. Not because the actions are impossible. But because strategy-as-event serves too many organizational purposes that have nothing to do with winning.

Strategy-as-event provides the illusion of control in a world that is fundamentally uncontrollable. It satisfies board expectations for a clear, decisive plan. It structures executive careers around visible moments of leadership. It creates the appearance of rigor through elaborate processes and polished deliverables. It allows leaders to feel that they have done their job, the strategy is set, and can now turn their attention to operational matters.

Replacing this with something messier, more distributed, and more continuous threatens all of those comforts. Strategy-as-capability means admitting that you do not have all the answers. It means giving up the clean narrative of the leader who sets the direction and the organization that executes. It means investing in capabilities whose payoff is years away. It means building systems that will outlast your tenure.

The companies that win will not just be the ones that understand this distinction. They will be the ones willing to give up the comfort of strategy-as-event for the effectiveness of strategy-as-capability. The 21 percent who believe their strategies are high quality are not necessarily smarter than everyone else. They have simply built something the other 79 percent have not: an organization that can strategize, not just one that has a strategy.