Why Strategies Fail at Scale: Six Things a Strategy Needs to Survive Contact

Most strategies are not killed by a competitor or a market shift. They are killed quietly, in the gap between the people who wrote them and the hundreds who have to enact them. A strategy can sound airtight in the boardroom and still fall apart the moment it meets an organisation that never co-built it. That is the real test. Not whether a strategy is brilliant, but whether it survives contact.

A well-designed strategy still fails when it cannot withstand interpretation by people who weren’t in the room. Below are the six things a strategy needs to survive that contact and stay executable at scale, and the specific way each one fails when it’s missing.

What does “at scale” actually mean here?

“At scale” is not a vanity word for big companies. It marks the precise moment a strategy stops being carried by the people who wrote it and starts being carried by people who didn’t.

In a team of ten, that moment never really arrives. The author of the strategy is in most of the rooms, fields the questions directly, and corrects a drifting interpretation before it hardens. The strategy and the person are effectively the same thing. Ambiguity is cheap because it gets resolved in conversation, in real time.

The break point is roughly the org that has grown past a single layer of management. Once there is a layer of people between the strategy’s authors and the people doing the work, call it somewhere around 50 to 150 people, the strategy has to travel without its authors attached. Every additional layer multiplies the problem, because each translation step adds its own interpretation on top of the last. By the time a strategy reaches the front line of a thousand-person organisation, it has been retold and re-summarised through four or five layers, and the version that lands can be unrecognisable from the one that was signed off.

So “fails at scale” is not about company size in the abstract. It’s about the number of interpretation hops between the strategy as written and the strategy as enacted. The more hops, the more the document has to do on its own. Everything that follows is about writing a strategy that holds its meaning across those hops.

What does “survives contact” actually mean?

A strategy survives contact when a mid-level manager who never attended a single planning session can read it, retell it accurately, and act on it without escalating. The room that built the strategy has an unfair advantage: they’ve heard it fifty times, debated the trade-offs, and unconsciously fill every ambiguous gap with shared context. Everyone downstream reads the same words with none of that context, and reconstructs the strategy from whatever local logic they have to hand.

That reconstruction is where strategies dilute. Not through resistance or incompetence, but through the honest application of different readings of the same document. The six points below are the places that gap opens widest.

1. A direction that is recognisably yours

The first failure is the most common and the easiest to miss: a strategy that could belong to anyone. “Market leadership”, “best-in-class experience”, “innovation-driven growth”. It’s a business buzzword salad, vague enough to apply to any company in any industry, and so committing to nothing. It reads as ambition. It functions as fog.

There’s a second version of the same failure, harder to spot because it sounds concrete: a strategy that is recognisably yours but isn’t recognisably new. If the direction is more of the same, a continuation of what you were already doing, then it isn’t a strategy. It’s maintenance dressed in strategy language. A real strategy marks a visible break from before. A reader should be able to point to what changes. When Netflix moved from posting DVDs to streaming, it deliberately undercut its own profitable business to back a different future. That is what a break looks like: a choice that costs you something you were already winning at.

A strategy survives contact when it commits to a small number of explicit choices: what you will do, at what scale, for whom, and through which distinctive capabilities. The test is uncomfortable but clarifying. Could a competitor lift your strategy statement and use it without changing a word? If yes, you haven’t written a strategy. You’ve written a mood.

2. One story, so everyone backs the same thing

A strategy can be clear on page one and quietly fracture by page twenty. Each section introduces a slightly different emphasis; the language drifts; financial return, market position, operational excellence and cultural transformation all get described as equally central, with no unifying thread to choose between them when they collide.

The job of a strategy is to get everyone focused on the same thing, the right thing, at the right time. That’s the test it has to pass: when budgets are tight and two good initiatives compete for the same money, the strategy should resolve the tension, not add to it. A strategy that can be read as backing both is not aligning the organisation. It’s licensing the fight.

A strategy that survives contact carries one governing idea that recurs in every section, with context, choices, initiatives and metrics all visibly serving the same story. The discipline here is subtraction: internal coherence is worth more than comprehensiveness. A strategy that says one thing clearly beats one that says five things well.

3. An explicit account of what you will not do

Most strategies are generous about what to start and silent about what to stop. They add priorities without acknowledging that existing commitments have to be reduced, retired or defunded to make room. The result is a scope written so broadly that virtually any activity can be framed as aligned with it, which means the strategy can never reject anything, and a strategy that can’t say no can’t allocate.

Naming what you’ll exit, decline or deprioritise, with enough specificity that a manager could use it to reject a project proposal, is one of the strongest signals that real choices have been made. Southwest Airlines is the textbook case: its low-cost, point-to-point direction was defined as much by what it refused as by what it did, no assigned seats, no meal service, no premium cabins, a single aircraft type. Each “no” came straight from the strategy, and any manager could apply it without asking. Trade-offs that stay implicit don’t stay resolved. They migrate upward, and every conflict between two legitimate priorities lands back on the leadership team’s desk, consuming exactly the attention that should be pointed at the future.

4. A causal chain you can actually trace

Many strategies move directly from a sharp situation analysis to a portfolio of initiatives, skipping the logic in between: why these initiatives, why in this sequence, why this particular combination will produce the intended outcome. The sections sit as independent modules, a strong diagnosis, a list of priorities, a set of KPIs, that never connect into a single argument.

When the causal chain is missing, execution teams fill it in with their own assumptions. Those assumptions diverge with distance from the authors, and the divergence stays invisible until it surfaces in results, by which point the money is already spent. The most dangerous version is the one where everyone did exactly what they were asked, the metrics didn’t move, and nobody can say whether the strategy was wrong or the execution was weak.

A strategy survives contact when the line from external context to choices to capabilities to actions to outcomes is explicit at every step. The working test: hand it to a manager who wasn’t involved. Wherever they ask “why?”, that’s a link you left to inference, and inference is where strategies drift.

5. Language precise enough to measure

“Strengthen.” “Accelerate.” “Optimise.” “Transform.” Directional verbs communicate energy and intent, and create no basis whatsoever for knowing whether you’re succeeding. A strategy written almost entirely in this register feels motivating and measures nothing, and what cannot be measured cannot be managed, adjusted, or learned from.

The deeper cost isn’t assessment, it’s learning. Without specific outcomes to test against, an organisation can’t tell a strategy that’s working from one that isn’t, can’t isolate which part of the execution system needs adjusting, and repeats the same cycle without accumulating any capability. Each objective should name an outcome, a scope, a timeframe and an order-of-magnitude for scale, specific enough that a neutral observer could assess progress without interpretation. Aspirational language can frame the objective. It can’t be the objective.

Take a line a COO might write into an operations strategy: “improve operational efficiency across the business.” Everyone nods, and nobody can act on it. Efficiency where, measured how, by when? The same intent, made precise: “reduce cost-to-serve per order by 15% in our two highest-volume markets by end of FY26, without lowering on-time delivery below 95%.” Now a plant manager knows which dial to move, can tell whether they’re winning, and can see the constraint they’re not allowed to trade away. The precise version doesn’t ask for more ambition than the vague one. It just survives the trip from the boardroom to the people who have to deliver it.

6. An honest account of what it will cost people

The final failure is the most human. A strategy describes an ambitious transformation, new markets, new capabilities, new ways of working, without ever naming who will have to change, what it will cost them, and why the ask is worth making. The difficulty, if it appears at all, gets confined to a brief change-management section that reads as an afterthought.

This produces compliance, not commitment, and the difference is decisive precisely when execution gets hard. Compliance delivers the minimum on defined tasks. Commitment delivers the discretionary effort, the early flagging of problems, the persistence through setbacks that real execution depends on. A strategy written purely for its evaluative audience, the board, investors, analysts, is optimised for external credibility and humanly inert to the people who actually have to build it. They read it, understand the business case, and find no reason in it to change how they work.

A strategy survives contact when it names honestly what will be genuinely harder for specific groups, frames that difficulty as worth undertaking, and connects the direction to a reason to care that survives beyond the next performance review.

The pattern underneath all six

None of these six is about strategic intelligence. You can have a brilliant strategy that fails on every one of them, and it will still fail, because each failure is a place where the strategy stops being transmissible. Survival isn’t a property of how good the thinking is. It’s a property of how little the strategy depends on its authors being in the room to explain it.

The strategies that scale are the ones built, from the first draft, to be read by people who will never hear the authors defend them. That’s the standard worth writing to: not “is this right?” but “will this still mean the same thing after it’s been retold a hundred times?”

Which of the six do you think your last strategy would have failed on? We’d genuinely like to know. It’s usually not the one leaders expect.