Strategy Execution: Where It Breaks Between the Offsite and Monday

Eighty-four percent were clear. Few could name two priorities.

The CEO of a London-based professional services firm opened every monthly management meeting the same way: she recited the firm's strategy and its top priorities for the year. An employee engagement survey then reported that 84% of staff agreed with the statement “I am clear on our organization's top priorities.” It was working ¹.

Then her management team took a different survey, one that asked them to describe the strategy in their own words and list the top five priorities. Fewer than one-third could name even two ¹.

That gap, between feeling aligned and being able to act on the same priorities, is where execution lives. Strategy execution is the work of turning strategic choices into resource shifts, commitments between units and everyday decisions. Donald Sull, Rebecca Homkes and Charles Sull define it as “the ability to seize opportunities aligned with strategy while coordinating with other parts of the organization on an ongoing basis” ¹.

Read that definition again and notice what it leaves out. Cascading goals. Scorecards. Alignment. In Sull's research those parts mostly worked ¹. The thesis of this page is that strategy execution rarely fails on the way down the org chart. It fails sideways: in the promises between units, and in the money and people that never move to the new priorities.

Strategy gets cascaded down. It dies sideways.

What follows are five places it breaks, why each one breaks, and a 90-day sequence for the weeks after an offsite. The evidence comes mainly from Sull's survey of nearly 8,000 managers in more than 250 companies ¹ and from Robert Kaplan and David Norton's work on management systems ². For the general concept, see the execution gap.

First, about the failure statistics

Articles on execution tend to open with a number: “70% of strategies fail,” “90% are never executed.” We have not been able to trace these to a study that defines failure and measures it. Careful authors cite such figures loosely too. Kaplan and Norton's 2008 article refers to studies over the previous 25 years indicating that 60% to 80% of companies fall short of the success predicted from their new strategies, without naming them ². Sull's own article says studies have found two-thirds to three-quarters of large organizations struggle to implement their strategies, also without naming them ¹.

Treat any such number as untraced unless it comes with a sample, a definition of failure and a source. The evidence on this page is narrower. It is also traceable, and it points to specific fixes, which a headline failure rate never does.

Break 1: Too many priorities to remember

Only 55% of the middle managers in Sull's survey could name even one of their company's top five priorities ¹. Fewer than one-third of senior executives' direct reports clearly understood how corporate priorities connected, and the share fell to 16% for frontline supervisors and team leaders ¹. Volume was not the problem: nearly 90% of middle managers believed top leaders communicated the strategy often enough ¹.

The cause is usually clutter. One tech company's executives used their annual offsite to present the strategy, then added 11 corporate priorities that differed from the strategic objectives, a list of core competencies, a set of corporate values and a dictionary of 21 new strategic terms ¹. The managers left baffled about what mattered most. Across the survey, middle managers were four times more likely to blame a large number of priorities and initiatives for their confusion than a lack of clarity in communication ¹.

The mechanism is simple. Every priority added dilutes the others, and executives measure communication by inputs (emails sent, town halls held) rather than by whether anyone can repeat the message ¹. The London CEO's engagement survey measured agreement. Her management team's answers measured understanding.

What to do: ask your top 50 or 100 leaders to write the priorities in their own words and compare the answers, which is close to how the researchers measured it ¹. Cut the list until the answers converge. Retire old priorities out loud. The communicating strategy page goes further on writing a strategy people can act on.

Break 2: The promise across the hallway

Most companies have invested heavily in vertical alignment: objectives cascaded down the hierarchy, measured and rewarded. That part mostly works. More than 80% of Sull's managers said their goals were limited in number, specific and measurable, and 84% said they could rely on their boss and their direct reports all or most of the time ¹.

Now look sideways. Only 9% said they could rely on colleagues in other functions and units all the time ¹. Counting “most of the time,” 59% could rely on colleagues in other departments, against 56% for external partners such as distributors and suppliers ¹. Put plainly: the team down the hall was about as dependable as a vendor. Managers said they were three times more likely to miss commitments because other units did not support them than because their own teams failed to deliver ¹.

Why does the sideways promise break when the vertical one holds? Follow the incentives. A manager's targets, bonus and review come down the hierarchy. The request from another unit arrives with none of those attached. When the two compete for the same week, the vertical commitment wins every time, and nobody is behaving badly. More than 80% of companies had at least one formal system for managing commitments across silos, but only 20% of managers believed those systems worked well all or most of the time ¹.

• For each strategic initiative, list the commitments it needs from other units, with a named person and a date on each side. Track them as promises, not as dependencies noted in a plan. The initiative charter is the natural place to write them down.
• Give each cross-unit initiative a single senior owner. Kaplan and Norton warn that stand-alone cross-unit initiatives often have no clear owner or home and wither for lack of resources and accountability; their fix is a senior executive leading each strategic theme ².
• Put the other unit's commitment into that unit's own targets. A promise that shows up in nobody's scorecard is a favor.

Break 3: Money and people stay where they were

A strategy that changes direction has to change where resources go. In Sull's survey, fewer than one-third of managers believed their organizations reallocated funds to the right places quickly enough, only 20% said their organizations did a good job of shifting people across units to support strategic priorities, and eight in 10 said their companies failed to exit declining businesses or kill unsuccessful initiatives quickly enough ¹. The authors also cite a McKinsey study in which companies that actively reallocated capital expenditure across business units earned an average shareholder return 30% higher than the average company ¹.

At the same time, half the middle managers surveyed believed they could secure significant resources for attractive opportunities outside their strategic objectives, and only 11% believed all their company's strategic priorities had the money and people needed to succeed ¹. Money that will not leave old uses, plus money that drifts to new uses outside the strategy: that combination is what starves a strategy.

The deeper cause is that budgets are built from last year's base, and every reallocation creates a loser who is sitting in the budget meeting. Kaplan and Norton's answer is structural. The executive team authorizes a separate pool of strategic expenditures, which they call StratEx, for the portfolio of strategic initiatives, kept apart from the operating and capital budgets that run current operations ². Ring-fencing makes the strategic money visible, so it cannot be quietly absorbed. The annual planning cycle page covers where in the calendar that decision has to be made.

• Ring-fence the strategic initiative budget before the operating budget is negotiated, not after.
• Set kill criteria for each initiative when it is funded, and review them on a fixed schedule.
• Move people as well as money. Name the critical roles each priority needs and who will fill them, by name.

Break 4: Operations eat the strategy meeting

Kaplan and Norton describe a company (disguised as Conner Corporation) whose monthly management meeting covered operations in the morning and strategy in the afternoon, until pressure to meet quarterly targets let operational items crowd strategy off the agenda ². They call it Gresham's Law applied to meetings: “Discussions about bad operations inevitably drive out discussions about good strategy implementation” ².

The mechanism is urgency. An operational problem has a deadline this week and a person in the room who owns it. A strategic theme has neither. Put them on the same agenda and the urgent item wins, every month, until the strategy review is a heading with nothing under it. Their remedy is to separate the meetings ²:

If the two reviews must happen on the same day with the same people, Kaplan and Norton insist on distinctly different agendas ². They also recommend spending most of a strategy review on a deep dive into one or two strategic themes rather than skimming every measure ². Their book, The Execution Premium, develops these ideas into a closed-loop system linking strategy and operations ³. For what the measures in that review should look like, see KPI examples that track strategy.

Break 5: The culture rewards the safe promise

When execution stalls, many executives blame a weak performance culture. Sull's data points the other way. Performance was rewarded; what execution also needs was not ¹. Past performance was two or three times more likely than a history of collaboration to be rewarded in hiring, promotion and recognition ¹. Asked what would happen to a manager who hit their objectives but failed to collaborate with other units, only 20% believed it would be addressed promptly ¹.

The safe promise follows. Two-thirds of managers would advise a new colleague to make commitments they could be sure to meet; fewer than one-third would recommend stretching for ambitious goals ¹. Half believed their careers would suffer if they pursued novel opportunities and failed ¹. A culture built that way produces exactly the behavior that breaks Break 2: hit your own number, and treat the other unit's request as optional.

What to do: put evidence of cross-unit collaboration into promotion decisions, ask each leader for one stretch commitment alongside the safe ones, and make it normal to stop an initiative early without penalty to the people who ran it.

The case for more control, and the alignment trap

The strongest objection to everything above is that top-down control works. Some of the most admired execution stories are about a CEO who personally drove it. Sull's article takes the best example head on: Larry Bossidy, who as CEO of AlliedSignal negotiated performance objectives with managers several levels below him and monitored their progress. AlliedSignal's stock outperformed the market under his leadership ¹.

It did work, for a while. Bossidy himself wrote that shortly after he retired “the discipline of execution…unraveled,” and the company gave up its gains relative to the S&P 500 ¹. The researchers' explanation is the mechanism of this whole page. Frequent intervention from the top teaches middle managers to escalate conflicts rather than resolve them with their peers, and over time they lose the ability to work things out across units ¹. Top-down execution borrows the coordination capacity of the organization and does not give it back.

At scale, the instinct to tighten control produces what Sull calls the alignment trap. Execution stalls, so leaders add metrics and more frequent progress meetings. The scrutiny turns into micromanagement, which stifles the experimentation and peer-to-peer coordination execution needs. Results worsen, so leaders tighten again ¹. In their words, managers who focus too narrowly on alignment “risk developing ever more refined answers to the wrong question” ¹.

The alternative they propose: execution driven from the middle, by the managers and experts they call distributed leaders, and guided from the top ¹. Guidance here means a short list of priorities everyone can repeat, a ring-fenced budget, a separate strategy review, and visible modeling of cross-unit behavior by the top team itself. That last item is not decoration: one-third of distributed leaders in the survey believed factions existed within the C-suite, with executives pursuing their own agendas ¹. A leadership team that cannot coordinate sideways should not expect anyone below it to.

If cascading and reporting already work, more of them will not help.

The first 90 days after the offsite

The weeks right after a strategy offsite decide whether its choices reach the operating rhythm. A practical sequence:

1. Week 1: Write the one-page versionReduce the offsite output to a short statement of the choices and no more than five priorities. List what is being stopped.
2. Weeks 2 to 3: Test understandingAsk the top 50 to 100 leaders to write the priorities in their own words. Fix the message wherever answers diverge, before cascading anything.
3. Weeks 2 to 6: Fund and staffMove budget and named people to each priority. Ring-fence the initiative budget and agree kill criteria for each initiative.
4. Weeks 4 to 8: Map cross-unit promisesFor each priority, list what it needs from other units, with a named owner and a date on both sides, and put those commitments into the giving unit's targets.
5. Week 4 onward: Separate the meetingsSet a monthly strategy review distinct from operational reviews, and rotate deep dives through the priorities.
6. Day 90: First adaptationReview what has changed since the offsite. Stop or re-fund at least one initiative based on evidence, so the organization sees that adapting is part of executing.

The offsite produces the choices. Monday produces the strategy: which budget line moved, which promise between two units got written down, which initiative stopped. A strategy nobody can repeat, that no money follows, held together by favors between departments, is still a slide.

Questions

What is strategy execution?

Strategy execution is the work of turning strategic choices into resource shifts, commitments between units and everyday decisions. Sull, Homkes and Sull define it as the ability to seize opportunities aligned with strategy while coordinating with other parts of the organization on an ongoing basis. On that definition, execution includes adapting the plan as conditions change, not only following it.

Do 70% of strategies fail?

The figure is widely repeated, but we have not found a study that defines failure and measures it to produce that number. Similar claims, such as 60% to 80% of companies falling short of their strategy's predicted success, are usually attributed to unnamed studies. Treat such numbers as untraced. Narrower survey evidence on priorities, coordination and resource shifts is more useful because it points to fixes.

What is the difference between strategy execution and strategy implementation?

In practice the terms are used interchangeably. Both describe the work that follows strategy formulation: resourcing, coordinating, monitoring and adjusting. Some writers use implementation for the initial rollout and execution for the ongoing work, but usage varies, so define the term once in your own planning documents and use it consistently.

Why does strategy execution fail?

In Sull's survey of nearly 8,000 managers, the main breaks were not vertical alignment or a weak performance culture. They were unreliable commitments across units, resources that did not move to strategic priorities, too many priorities for managers to remember, and cultures that rewarded safe commitments over collaboration. Kaplan and Norton add a structural cause: operational issues crowding strategy out of management meetings.

What is the alignment trap?

The alignment trap is Sull, Homkes and Sull's name for a downward spiral. When execution stalls, leaders add metrics and progress meetings to tighten alignment. The scrutiny becomes micromanagement, which stifles the experimentation and peer coordination execution depends on, so results worsen and leaders tighten further. The way out is to fix coordination across units rather than add vertical control.

Where to go next

• Strategic Initiative Charter: Template and How to Write One
• KPI Examples That Track Strategy, Not Activity
• Communicating Strategy So People Can Act on It
• Execution Gap
• 4DX (Four Disciplines of Execution)