Why Strategy Execution Fails: The Five Breaks in the Execution Chain
Leadership teams rarely fail at planning — they fail after it. When a strategy stalls three months past the offsite, the cause is almost never the plan. It's structural. The Execution Chain names the five places a company breaks between an approved strategy and the daily decisions meant to deliver it.

The offsite was good. That is what makes this hard to talk about honestly. The market read was sound, the three bets were defensible, the deck was clear enough that everyone in the room could repeat it on the drive home. Then nothing much happened, and by the second quarterly review the conversation had already moved on to what next year's plan should say.
We see this pattern often enough to have stopped treating it as a planning problem. When a strategy stalls three months after it is approved, the explanations offered are almost always soft ones — weak buy-in, poor communication, a team that lost focus. Those are symptoms. The cause is usually structural: something in how the company is built makes the strategy impossible to carry out, no matter how committed the people are.
"We've never once concluded the company couldn't carry it"
A CEO of a professional-services group in the Gulf told us they had shifted the firm toward recurring product revenue and away from project work. Eighteen months later the recurring line was a side experiment run by three people, and the board had concluded the strategy was wrong.
It wasn't. The firm was still built as delivery units measured on billable utilization. There was no product function, nobody accountable for retention, and the fastest route to a promotion still ran through staffing a large project. Every incentive in the building pointed at the old model, and the old model won by default — the way it always does when a new direction needs a capability the org chart does not contain.
What that CEO said next is the sentence we quote most often: "Every time a plan fails, we conclude the strategy was wrong. We've never once concluded the company couldn't carry it."
The Execution Chain
We describe execution to the leadership teams we work with as a chain, because that is how it behaves — including the part where it is only ever as strong as its weakest link.
Organizational DNA → strategy and business model → structure and roles → governance and decision rights → objectives → measures — with culture running underneath the whole thing, deciding which links actually hold under pressure.
Each link converts the one before it into something the next can use. DNA makes strategy coherent. Strategy makes structure decidable. Structure makes decision rights assignable. Decision rights make objectives ownable. Objectives make measures meaningful. Break any link and everything downstream of it becomes decorative.
There are five places it breaks.
Break 1 — the objective has owners, plural
Open almost any annual plan and you will find a line like "expand into three new cities" with an owner column reading "Commercial and Operations." It looks collaborative. In practice Commercial waits for a site decision, Operations waits for a demand signal, the quarterly review records it as "in progress," and by Q3 it has quietly become next year's objective.
Shared ownership is the polite form of no ownership, and a stricter review meeting does not repair it — a leadership team can chase an unowned objective for four consecutive quarters without changing anything. What changes it is one named owner per objective, a small number of measurable results, a fixed cadence for updating them, and a visible line from the company objective down to the department and the individual. That is a system rather than an intention, and its value is that it holds between meetings. Our guide to OKRs covers how to write objectives that survive a real quarter — and departmental ping-pong is what shared ownership looks like from the inside.
Break 2 — the structure still serves the previous model
This is the Gulf firm above, and it is the most expensive of the five because it is invisible on paper. Reporting lines, mandates and incentives decide which work is possible and which work requires heroics. When a new direction needs a capability the structure does not contain, the strategy is not rejected — it is simply outcompeted, every day, by the design that is already there.
Redesigning that is more than moving boxes, which is why we work through mandate and role clarity before touching the chart. Start with the difference between an org chart and an organizational structure.
Break 3 — authority lives in people's heads, not in writing
A regional director needs a pricing exception for a large account. Who signs? Finance thinks the commercial VP owns it. The VP has never approved one that size and prefers to check with the CEO. The CEO is travelling. Three weeks pass, the client moves on.
This is common in fast-growing groups across Saudi Arabia and the wider GCC, where authority was held informally by a founder or a small circle and was never converted into written policy as the company passed fifty people, then two hundred, then five hundred. The company escalates everything upward and mistakes that for control, while execution slows to the speed of the busiest calendar in the building. The remedy is written governance — a delegation-of-authority framework, clear thresholds, defined committee mandates, policies people can actually find. Intent does not distribute authority; documented decision rights do, and without them you get decision drift.
Break 4 — the dashboard measures effort
A transformation programme reports monthly on training hours delivered, workshops held, systems configured. Every number is green. Nobody can say whether the customer experience it existed to improve has moved, because no measure was defined at the start. The programme is measuring itself.
This is the quietest of the five, because it looks like rigour. Activity metrics are easy to collect and comfortable to present; outcome metrics expose whether the strategy is working. A company that measures only effort learns the truth at year-end, well past the point where it could have adjusted — and a spreadsheet an analyst rebuilds before each board pack is reconstruction, not measurement. It is the same failure as the ceremony trap: the ritual survived, the purpose didn't.
Break 5 — the rewarded behaviour contradicts the written values
The values page says speed, ownership and candour. A routine purchase takes six signatures, and the last person to raise a delivery risk early ended up defending themselves for it. Two years on, the team has learned the real rules perfectly. Nobody wrote them down; everybody follows them.
Culture, in execution terms, is simply the set of behaviours a company actually rewards. When those contradict the declared direction, the declared direction loses — quietly, without a meeting. It is why strategies fail in companies where every other element looks correct on paper, and why slogans on the wall are the least reliable evidence of what a company believes. Closing this gap starts with being able to see it: a short monthly pulse turns a vague sense that something is off into a signal you can track, and a defined organizational DNA gives leaders something concrete to hold decisions against.
Here's the contrarian part
When execution fails, almost every leadership team responds by rewriting the strategy. It is the cheapest available move and it feels productive — a new offsite, a sharper deck, renewed energy. It is also, most of the time, treatment aimed at the one part of the system that was working.
The second half of that take is less comfortable: don't try to fix all five at once. The chain runs in order, and a downstream link cannot be repaired while an upstream one is broken. Sharper measures on an objective nobody owns produce a better-instrumented failure. Cleaner decision rights inside a structure that contradicts the strategy just accelerate the wrong work. Find the first broken link and fix that one. The links after it are often looser than they looked.
Why it works
None of this is new thinking; it is thinking that rarely survives contact with a planning calendar. Chandler's observation that structure follows strategy is over sixty years old, and organizations still redesign the strategy far more readily than the structure. Goal-setting research has been consistent for decades that specificity and ownership drive attainment, which is exactly what a plural owner column removes. And the governance literature keeps arriving at the same place we do in the room: informal coordination that works beautifully at thirty people does not survive to three hundred, and consistency has to be deliberately rebuilt as authority is distributed. Fixing execution is organization development applied to the hardest thing a company does — carry a decision all the way to the ground.
A practical checklist
- Test every objective for a single name. Any owner column containing "and" is Break 1 until proven otherwise.
- Ask what capability the strategy assumes and check whether the structure contains it. If it doesn't, the strategy is a hiring and redesign plan wearing a different title.
- List the five decisions that escalate to the CEO most often and write the rule for each. That is your delegation-of-authority draft.
- For each objective, name one outcome measure and one leading indicator — with an owner, an update frequency, and a target set before the period starts.
- Read the culture on a cadence, not once a year. A short monthly pulse beats an annual engagement report you receive after the quarter it describes has closed.
- Diagnose the first broken link before you rewrite anything. Then fix that one, and only that one, for a quarter.
Ask yourself
- If we made every objective owner a single named person tomorrow, which objectives would suddenly have nobody willing to take them?
- What capability does this strategy assume we have — and where does it live on the org chart?
- Which routine decision reached me this month that should have had a written rule?
- Can we say, today, whether the outcome we promised has moved — or only how much work we've done?
- What behaviour got someone quietly punished here in the last six months, and does it appear on our values page as something we claim to reward?
The takeaway
Strategy execution rarely fails because the plan was wrong. It fails because ownership was shared, the structure still served the previous model, authority stayed unwritten, progress was measured as activity, and the practised behaviour contradicted the written values. Each has a structural remedy in how the company is defined, governed and measured. Naming which link broke is what makes the next step specific instead of general — and it is almost always cheaper than another offsite.
Frequently asked questions
- Why do most strategies fail to be implemented?
- Because the organization around the strategy was never changed to carry it. Ownership stays shared, the structure still serves the previous business model, decision rights are undocumented, progress is measured as activity, and the behaviour that actually gets rewarded contradicts the stated values. Each is a design flaw in the operating system, not a shortage of effort.
- What is the execution gap?
- The execution gap is the distance between an approved strategy and the daily decisions of the people expected to deliver it. It shows up as initiatives with owners in the plural, work that continues on the pattern of the previous model, approvals that stall, and dashboards full of activity. It widens quietly, usually a full quarter before anyone names it.
- What is the difference between strategy and execution?
- Strategy is the set of choices about where you play and how you win. Execution is the system that turns those choices into owned objectives, roles, decisions and measures. Most companies debate strategy far more than they design execution, which is why sound strategies still fail. The two only ever meet inside structure, governance and measurement.
- How do I know early that our strategy isn't going to land?
- Three signals appear inside the first quarter. Objectives carry owners in the plural rather than one name. Routine decisions escalate to the CEO because nobody can point to a written rule. And progress reviews report effort — meetings held, systems configured — rather than movement in an outcome measure agreed before the period started.
- Should we fix all five causes at once?
- No. The chain runs in order, and a downstream link cannot be repaired while an upstream one is broken. Adding sharper measures to an objective nobody owns produces a better-instrumented failure. Find the first broken link and fix that one; the ones after it often loosen on their own.



