Strategy execution · where the plan stalls between approval and Monday
Strategy Execution: the roles a plan passes through, and what each one assumes.
Strategy execution is the work of turning an approved plan into results the organization can count. The plan itself is rarely the problem. Between the executive who approves a priority and the professional who does the work on Monday morning sit nine other roles, and each one adds an approval, a handoff, or a queue. The delay gets read as a people problem. It is usually a route problem with a cost attached.
This page maps the eleven roles that strategy execution in business runs through, what each contributes, and the assumption its contribution rests on. It ends with four questions you can answer about one stalled result, and one way to trace it.
Executive summary Where strategy execution stalls, and the one route worth tracing first.+
An approved strategy passes through eleven roles before it becomes Monday's work. Every role above the people who carry the work adds an approval, a handoff, or a queue, and each one rests on an assumption about how easily the work will clear the roles below it. Checking that assumption against the route the work takes is nobody's job.
The gap is measurable. Bain surveyed nearly 1,000 executives and employees after reorganizations in 2026: 88 percent of leaders expected the new structure to hit its goals, and 36 percent of the employees inside it agreed. The tracking tools record owners and status. They do not record where the work waited, so the explanation drifts toward the people.
The standard cures add steps to the route: reviews, status meetings, approvals, sometimes a new framework. Each one is more Meeting Tax and Decision Density Tax charged against the same result. The route is the one explanation that can be tested. Remove two approvals from one stalled result and watch whether it moves inside fourteen days. Skill, motivation, and alignment cannot be tested that way.
Four questions near the end sort one stalled result into worth tracing or not. The Stalled Priority Snapshot reconstructs the route in 90 minutes, puts a defensible number on the waiting, and returns one 14-day routing change in writing within 24 hours. Fixed scope, $1,500.
The situation
The strategy was approved. The work is still waiting.
The board saw the plan. The town hall repeated it. The objectives cascaded into OKRs, the budget followed, and a quarter later the priority is on every status report and in nobody's week. Three status meetings return three explanations: competing priorities, not enough people, waiting on legal. Each is partly true. None of them says what to change.
The tools are not the gap. Workfront, Jira, and Planview record what the strategy implementation plan asked them to record: owners, status, and dependencies. What they cannot show is the route the work took to get there. Which approval it sat on for eleven days. Which review sent it back twice. Which manager's queue every exception landed in. Nobody drew that route, so the conversation drifts toward who is not delivering, which is the most expensive conclusion to reach and the hardest to support.
The gap between the plan and the work has a name, execution drag: the loss between the performance an organization has paid for and the performance its work paths let people deliver. It is measurable. In a 2026 Bain survey of nearly 1,000 executives and employees who had been through a reorganization, 88 percent of leaders believed the new structure would achieve its goals. Only 36 percent of the employees working inside it agreed. The chart below shows where that gap comes from: what each role assumes the work will clear, and what the work has to clear. Why projects fail covers the eight causes and what to check first. This page follows one of them, the route, through the eleven roles on the chart.
The chart
Eleven roles. One route. Eleven unchecked assumptions.
This is an org chart of strategy execution rather than of reporting lines. Purple roles set direction. Teal roles are the connective tissue that turns a decision into a plan with owners, money, and a review cadence. Coral roles carry the work, which is the only place a strategy gets executed. Hover or tap any role. The panel shows what the role contributes, the assumption that contribution rests on, and where it breaks. The last field says why the finding matters to someone in that chair.
Read the assumptions top to bottom and a pattern shows up. Every role above the coral tier assumes something about the route the work will take through the roles below it, and no role on the chart is assigned to trace it. Direction is set as if the approvals were free. Plans cascade as if an announced priority were a moving one. Budgets fund the work, and the waiting, the handoffs, and the rework never appear on a line. By the time the work reaches managers and professionals, the plan is carrying all of those assumptions at once.
Contributes to strategy
Contributes to execution
What this role assumes
Where it breaks
Why this matters to this role
Strategy vs execution
Nobody drew the route the strategy would have to travel.
The strategy vs execution debate usually ends with a verdict on the people: the plan was right and the organization could not deliver it. The chart supports a narrower reading. The plan was right and nobody traced what it would have to clear. What follows from that can be checked against a route you already have.
What the chart makes hard to unsee
The standard cures are additive. When leaders lose confidence in execution they add reviews, status meetings, and approvals, and sometimes a new strategy execution framework. Each control is meant to reduce risk. Each one is also a step added to the route the work already takes, and together they create the switching, the waiting, and the repeated review that produce more risk. The standard fix for execution failure raises the Meeting Tax and the Decision Density Tax on the same result. No framework is at fault for that. The steps added around it are, and those are the steps a route trace counts.
The same person, two outcomes. Take the manager who is not executing and take two approvals off the route their work travels. If the work moves, nothing about the manager changed. If skill, motivation, or alignment were the explanation, that result could not happen. Nobody counts it as evidence, because nobody drew the route before and after.
Every other explanation is unfalsifiable inside the organization that holds it. You cannot prove you do not have a culture problem. You can prove the route is not the problem in fourteen days: change one condition on the path, then watch whether the result moves. This is the only explanation on the chart that can lose, which is exactly why it is the only one that can be trusted when it wins.
Read the last field in the panel across all eleven roles and the pattern is simple. Every role above the coral tier gets a better explanation for a failure it already owns. Every role in the coral tier gets a test instead of a verdict. The COO and the department head are the two who can act on it without a committee, on one route, in two weeks. Stronger strategy execution starts there, with one result that moves.
A test you can run now
Which result would you least like to explain at the next review?
Not the whole strategy. One milestone, decision, or deliverable inside it that should have moved by now. Answer the four questions for that one. They are the signatures work leaves on a route when it is stuck, and each question below checks for one of them. The answers establish whether the route is worth tracing. They do not establish what caused the stall. The trace does that, and it may find that the outcome was never properly defined or that a vendor is setting the pace, in which case the route was never the answer.
Is it the route? Four questions about the result you named.
Hold that one in mind and answer for it.
Does it wait? Is it sitting on an approval, a review queue, or a committee slot right now?
Does it loop? Has finished work come back for clarification, correction, or another pass?
Is it piled up? Is it competing with other open items for the same people, and losing to whatever is loudest?
Does it route through one person? Do the approvals, escalations, and exceptions all land on the same desk?
Ninety minutes on one result, and a number you can defend.
The operations side of strategy execution rarely needs another framework. It needs one result, the people who move it, and 90 minutes with someone from outside the route who can say where it waited without paying for the sentence.
What the Stalled Priority Snapshot is
- One result. The initiative you just named.
- Ninety minutes with up to three people who move, approve, or unblock it.
- Path evidence only. Where the work waited, where it was handed off, and where it came back, reconstructed in the room. No surveys, no system access, no people questions.
- A written read within 24 hours: the work-path map, the hours you can defend with the arithmetic shown, and one 14-day routing change with an owner, a metric, and a decision rule.
- $1,500, fixed scope. Priced to be approved on a card, not by a committee.
What it is not
- Not coaching. Nobody on the route is assessed, and nothing feeds a performance process.
- Not a transformation program. It does not touch reviews, comp, or the org chart.
- Not a commitment. The read stands on its own. The fee credits toward the Work Demand Diagnostic if booked within 30 days, and nothing after it is assumed.
- Not a guess. If the route does not explain the stall, the read says so and names what to check next. You have ruled one cause out, and that is still a result you can hand upward.
Where this connects
The roles on the chart each have a page.
The queue that forms on middle managers is the subject of Span of Control: 97% of Managers Are Doing Two Jobs. Decisions that sit because the route to a decision-maker is clogged are covered in Slow Decision-Making: Why Ready Projects Wait. The sixth initiative the chief of staff could not refuse is the subject of Competing Priorities: Why Important Work Stalls. The cost vocabulary the CFO can repeat upward is the Five Capacity Taxes.
When the pattern is bigger than one result and shows up across a team or an operation, the Work Demand Diagnostic examines whether it is shared. Start with the Snapshot. The next question comes from what the first route shows.
Start with one result
Find what is holding up one priority.
Bring the milestone, decision, or deliverable that should have moved by now. You leave with the route the work takes, the hours you can defend, and one change to test in the next two weeks.
