The Framework Was Not the Problem
A CEO I worked with had tried four strategy execution frameworks in five years. Hoshin Kanri. OKRs. 4DX. A custom playbook from a tier-one consultancy. Each one was launched with conviction. Each one had a champion. Each one quietly went the same direction within six months — present in the slide decks, absent from the actual decisions.
He told me, "I do not need another framework. I need to know why nothing sticks."
That is the conversation most leadership teams need to have before they pick the next execution framework. Because the framework is almost never the part that fails. The framework is a scaffolding. The thing that holds it up is leadership behavior. Most organizations install the scaffolding and assume the behavior will follow. It does not.
Why Strategy Execution Frameworks Fail
The numbers are stark. Bridges Business Consultancy's research on strategy execution has found, across multiple years and industries, that roughly 67% of well-formulated strategies fail because of poor execution. Another study from Harvard Business School put the strategy-to-execution gap at 60-90% of stated value lost. These are not edge cases. This is the majority of organizations.
When you look closely at the failure pattern, it is rarely about the framework choice. Hoshin can work. OKRs can work. 4DX can work. The failure shows up in four predictable places.
Senior leaders treat the framework as a launch event. The kickoff is energetic. The first quarterly review is engaged. By the third review, the conversation is about progress against the dashboard, not progress against the strategy. The framework has been quietly absorbed into the existing rhythm and stopped producing anything different.
Middle leaders translate the framework into safe targets. This is the silent killer. The framework asks each level to set ambitious commitments. Middle leaders, watching how senior leadership actually reacts to misses, set targets they know they can hit. The result looks like execution. It is performance.
The behavior the framework requires has not been built. Every execution framework requires a specific leadership skill set. Hoshin needs catchball — the ability to receive substantive challenge from below as contribution, not threat. OKRs need disagree-and-commit — the ability to hold a hard conversation in the room and not relitigate it in the hallway. 4DX needs scoreboard discipline. If those skills are not present, the framework runs on top of the old behavior and produces the old results.
There is no shared why. Frameworks deploy targets. They do not deploy meaning. When a manager three levels down cannot articulate why a strategic priority matters in their own context, in their own words, they execute the activity and miss the outcome. Strategy dies in the middle because the why never made the trip down.
Notice that none of these failures are fixed by switching frameworks. They are fixed by building the capability the framework depends on. Most organizations skip that step because it is harder, slower, and less photogenic than a launch.
A Strategy Execution Framework Has Three Layers, Not One
The framework most leaders argue about is the artifact layer — the X-matrix, the OKR tree, the 4DX scoreboard. That is one layer. It is the most visible and the least load-bearing.
Underneath sits the rhythm layer — the monthly reviews, the quarterly resets, the cascade conversations. This is where most frameworks differ in shape but converge in purpose: a repeatable cadence that forces the strategy to be reread, recommitted, and re-translated.
Underneath that sits the capability layer — the leadership behaviors the rhythm depends on. Receiving challenge. Disagreeing publicly. Translating priorities into context. Holding a tough conversation without it becoming politics. Naming what is not working before it becomes a quarterly miss.
A strategy execution framework works when all three layers are live. Most frameworks fail because organizations install the top layer, partially install the middle layer, and never address the bottom layer. The capability layer is the one most worth your time, because it carries every framework you will ever adopt.
The Behavioral Test Most Frameworks Skip
Here is the question that exposes which layer your organization is missing. Pick any strategic priority your team agreed to last quarter. Walk down three levels in the organization. Ask the manager at that level two things. First, what is the priority in your own words. Second, what behavior have you changed in your work because of it.
If the manager can recite the priority but cannot name a behavior they changed, the framework is operating at the artifact layer only. If the manager can name a behavior change but cannot connect it to the strategic intent, the rhythm layer is working but the capability layer is thin. If the manager can do both, your framework is actually live.
In most organizations, the answer to both questions is "I am not sure" — which is the honest version of "this strategy does not really touch my work." When you hear that, you have found the gap. The gap is not solvable by adopting a different framework. The gap is closed by building the behavior the framework needs.
This is the same diagnostic underneath why your quarterly review doesn't change anything. The reviews keep happening. The behavior keeps not changing. Until the capability layer is addressed, the rhythm produces motion without movement.
Endurance as an Execution Framework
At Lead the Endurance, we work from a different premise. The framework is not the slide deck. The framework is the experience that builds the behavior the strategy needs.
In a Lead the Endurance experience, leaders become Senior Advisors to Ernest Shackleton on his 1914 Antarctic expedition. They face Shackleton's actual decisions. The plan stops working. Resources run out. The team has to be aligned by something other than the original brief, because the original brief no longer fits the world.
What happens in the room is what most execution frameworks are trying to produce and rarely do. Leaders practice receiving challenge as contribution. They practice disagreeing in the moment without relitigating in the hallway. They practice translating long-range intent into the next decision. They practice the Power of Why — POW — cascading why a decision matters before they cascade what to do. These are the capability-layer behaviors every framework assumes are present.
The rhythm pairs naturally. We connect each leader's function to the company strategy with the Big Picture Model. Then we make the cascade method portable. Leaders go home and run the same conversation pattern with their teams — not present strategy, facilitate it. The strategy gets owned at each level because each level had the conversation, not the slide.
The artifact layer is the easy part. Once the rhythm and capability are live, almost any framework — Hoshin, OKRs, 4DX, OGSM — slots in and works. The reverse is not true. No artifact survives a leadership team without the rhythm and capability.
How to Install an Execution Framework That Lasts
If you are choosing or relaunching an execution framework, four moves separate the ones that stick from the ones that fade.
Diagnose the capability gap before you pick the artifact. Run the three-level test above. Find out which layer is missing. If the rhythm exists but the behavior does not, no new artifact will fix it.
Build the behavior before you launch the framework. Most organizations reverse this. They launch the framework and hope the behavior follows. It rarely does, because launching the framework is the part that consumes the political capital you needed for the behavior work. Why leadership development needs pressure not slides gets at the same point — capability is built under pressure, not in a kickoff slide. Build the leadership capacity in a high-fidelity environment first. Then the framework becomes a tool the team already knows how to use.
Choose a framework that matches your team's current capability. A team new to cascade conversations should not start with full Hoshin catchball. A team without scoreboard discipline should not start with full 4DX. Match the artifact to the behavior the team can actually run. You can always upgrade the artifact later. You cannot downgrade a team that has been embarrassed by a framework they were not ready for.
Schedule the capability check, not just the strategy review. Quarterly reviews look at the dashboard. Almost none of them look at whether the capability layer is still live. Build in a six-month check that asks: are leaders still receiving challenge well? Is the cascade conversation still happening at three levels deep? Is the why still being translated, or have we slipped back to broadcasting? The check is the only thing that catches capability erosion before it becomes a missed strategic outcome.
For the structured cadence side of execution, Hoshin Kanri for leadership teams maps the rhythm in depth. For the cascade pattern that makes it portable, how to cascade strategy without a slide deck gives the conversation method. Both pair naturally with the capability work the executive development path is built to produce.
What Real Execution Looks Like in the Numbers
The shift shows up in execution speed. At ArcelorMittal, 710 leaders went through Lead the Endurance through Duke Corporate Education. The measurable change was decision speed — leaders making cross-functional decisions 30 to 40% faster. Not because anyone pushed for speed. Because the capability layer was strong enough that decisions stopped routing through three rounds of political translation.
At Bell MTS, revenue moved from $800 million toward $1.4 billion in a single year. The strategy was sound before the work started. What changed was the leadership team's capacity to execute it together — to hold a hard conversation in the room, translate priorities into local decisions, and stop relitigating every cross-functional choice.
Both organizations had strategy execution frameworks before the experience. What changed was not the artifact. What changed was the behavior the artifact had been waiting for.
That is the work. Pick the framework second. Build the capability first. If your plan keeps landing short of target, the deeper diagnosis is in the strategy execution gap — it is a people problem before it is a planning one.
Read next: Why Strategy Dies in the Middle