Why Strategy Execution Fails: Fix the Execution System

Most strategies do not collapse because the idea was obviously wrong or because employees refused to work. They weaken as strategic intent passes through priorities, decision rights, budgets, incentives, handoffs, reporting systems and feedback loops. The failure is rarely located in one person. It is produced by the execution system.

The strategy looked coherent in the executive workshop. It contained a clear ambition, a small number of themes and a persuasive story about the future. The launch was professional. Leaders repeated the message. Departments created plans. New dashboards appeared. Meetings multiplied.

Twelve months later, the organization is busier—but not meaningfully different.

The old portfolio still consumes most capacity. Teams use the new language while protecting old priorities. Cross-functional initiatives wait for decisions that nobody feels authorized to make. Reports show completed activities, yet customer outcomes, speed, quality or strategic position barely move. Leadership concludes that the organization lacks accountability and asks for more urgency, more reporting and more discipline.

This is the point at which many organizations misdiagnose the problem. They interpret a systemic execution failure as an individual performance failure. They push harder on the same conditions that produced fragmentation.

Research on strategy implementation has long treated execution as a multi-actor, multi-level process rather than a final stage that begins after planning. Reviews of the field describe a diverse set of managerial activities spread across functions, levels and sometimes organizational boundaries. Leadership alignment, organizational structure, resource allocation and coordination all shape whether strategic initiatives become real outcomes.¹²

The central argument of this article is therefore simple:

What is strategy execution?

Strategy execution is the continuous organizational process through which strategic intent becomes coordinated decisions, resource commitments, operating priorities, daily behavior and measurable outcomes. It includes translation, alignment, coordination, delivery, feedback and adaptation.

This definition matters because execution is often reduced to project delivery. Projects can support a strategy, but a strategy changes more than a project plan. It changes what the organization protects, what it declines, how decisions are made, which capabilities receive investment and how teams resolve competing demands.

Strategy formulation	Strategy execution
Defines direction and strategic choices.	Turns choices into coordinated movement.
Determines what matters most.	Protects priorities against competing demands.
Identifies intended outcomes.	Changes decisions, resources, processes and behavior.
Is often concentrated among senior leaders.	Is distributed across levels, functions and boundaries.
Produces a strategic logic.	Tests that logic against operational reality.
Creates direction.	Creates effects—and learns from them.

The distinction should not create a wall between thinking and doing. A strategy changes as the organization encounters customers, constraints, competitors, technologies and unexpected consequences. Frontline adaptation can reveal that an assumption was wrong. New evidence can require a different sequence, investment or operating model. Execution is therefore not blind obedience to a fixed plan. It is disciplined movement that preserves direction while learning from reality.

This is why effective execution requires more than alignment from the top down. It also requires coordination across silos and adaptation close to the work—two themes emphasized in influential strategy-execution research.³

What is the strategy–execution gap?

The strategy–execution gap is the distance between the organization’s declared strategic intent and the pattern of decisions, investments and actions it actually produces.

The gap is not one missing step between a strategy document and delivery. It is accumulated distortion. Meaning is altered as it moves between levels. Priorities separate as they move across functions. Strategic attention erodes as urgent work consumes time. Each distortion can appear small. Together they create an organization that speaks one strategy and operates another.

Vertical distortion

Executives describe an aspiration such as “become customer-led,” “build an adaptive enterprise” or “shift from products to solutions.” Middle managers must convert this into priorities, capacity decisions and trade-offs. Operational teams must convert it again into specific behavior. When translation is informal, every layer fills the gaps with its own assumptions.

Horizontal fragmentation

Functions interpret the strategy through local objectives. Sales optimizes revenue. Operations protects stability. Finance protects predictability. Technology protects architecture. Each decision can be rational locally while damaging the enterprise outcome. The organization does not fail because no one is trying. It fails because the parts are not shaped to act as one system.

Temporal erosion

Strategic priorities compete with incidents, quarterly pressure, customer escalations, regulatory commitments and legacy work. Unless leaders remove old obligations and protect strategic capacity, urgent work gradually displaces important work. This is one mechanism behind organizational strategy drift: the organization does not announce a new direction; it quietly returns to the gravitational pull of its existing system.

A useful question is not merely, “Are people executing the plan?” It is:

Why strategy execution fails: eight systemic causes

There is rarely one cause. Strategy execution fails when several weaknesses interact and reinforce one another. The following eight causes are common because they sit inside the organization’s operating conditions—not because employees suddenly stop caring.

1. The strategy remains abstract

Aspirations are not yet choices. “Grow,” “innovate,” “become agile,” “improve customer experience” and “use AI” can point toward a direction, but they do not tell a team what to prioritize when goals conflict. A strategy becomes executable when it defines choices, trade-offs and decision rules.

Teams should be able to answer: What will we do differently? What will we stop? Which customer, capability, market or problem receives preference? Under what conditions should speed outweigh efficiency? Which opportunities should we deliberately reject?

When these answers remain unclear, the organization does not have one strategy. It has many local interpretations.

2. Priorities multiply instead of narrowing

Leaders often announce new strategic priorities without retiring old initiatives, service expectations or governance demands. The result is not strategic focus; it is portfolio congestion. Everything becomes “critical,” so teams use urgency, political sponsorship or local metrics to decide what actually receives attention.

This is why execution cannot be repaired by adding another program. Leaders must actively remove work. Research on project portfolios points to the importance of terminating initiatives that no longer fit strategy rather than allowing them to consume resources indefinitely.⁴

A strategy that does not change the portfolio is usually a communication campaign layered over the old organization.

3. Local incentives overpower enterprise intent

People respond to the system they experience. If collaboration is celebrated but bonuses reward local output, local output wins. If customer value is emphasized but budgets punish experimentation, teams protect certainty. If leaders ask for long-term capability while quarterly reviews reward short-term volume, the organization will optimize the quarter.

The incentive trap appears when the organization blames people for behavior its own measures, resource rules and status systems make rational.

4. Decision rights remain unclear

Many execution problems are decision problems in disguise. Teams gather data but cannot act. Decisions rise through several layers, return for more analysis, move to committees and eventually arrive too late. In other cases, several leaders believe they own the same decision, producing negotiation rather than accountability.

When organizational decision-making slows down, strategy loses tempo. Dependencies accumulate, work starts before assumptions are resolved and teams compensate with rework.

Clear decision rights do not mean centralizing everything. They mean specifying who decides, who contributes, what thresholds trigger escalation and what principles guide choices when leaders are unavailable.

5. Resources remain attached to the old strategy

Budgets, headcount, specialist capacity, leadership attention and meeting time reveal the operating strategy more accurately than presentation slides. If new priorities receive no protected resources, teams are expected to execute transformation from whatever capacity remains after the old system is served.

Research on implementation barriers has repeatedly identified resource allocation and organizational structure as material conditions of execution, affecting information, control and decision processes.⁵

The crucial question is not, “Did we approve the strategy?” It is, “What did we move, stop, fund or protect because of it?”

6. Cross-functional dependencies remain unmanaged

Strategic value increasingly crosses functions. A customer journey may involve sales, operations, technology, finance, risk and service. A product strategy may depend on data quality, platform capabilities, pricing, legal design and channel adoption. No single function controls the whole outcome.

Yet many organizations still govern work through vertical reporting lines. Handoffs become invisible ownership gaps. Teams optimize their portion and declare success while the end-to-end result stalls. This is a core reason organizations become siloed.

Execution requires explicit dependency maps, cross-functional decision forums and outcome ownership that extends beyond departmental boundaries.

7. Feedback arrives late, filtered or unusable

Leaders often receive reports designed to demonstrate progress rather than reveal reality. Metrics emphasize tasks completed, meetings held and milestones declared. Weak signals are normalized. Bad news is softened as it travels upward. By the time outcomes are clearly below target, the organization has spent months executing assumptions that no longer hold.

This is not only a measurement problem. It is a reality gap. The organization cannot adapt when information is delayed, politically filtered or disconnected from decision rights.

Strong execution depends on feedback loops that connect evidence to action: observe, interpret, decide, adjust and measure again.

8. Adaptation is confused with inconsistency

Some organizations protect the original plan long after conditions change because adaptation is interpreted as weakness. Others change priorities so frequently that teams cannot build momentum. Both extremes destroy execution.

Adaptive execution distinguishes between four things:

• Direction: the enduring outcome or strategic position.
• Assumptions: beliefs that must be tested against evidence.
• Execution choices: the current route toward the outcome.
• Operating conditions: structures, incentives and capabilities that shape action.

Direction can remain stable while assumptions and execution choices evolve. That is not strategic drift. It is disciplined adaptation—the capability organizations lose when they become unable to adapt to changing reality.

The Strategy-to-Action Cascade™

Strategic intent must become progressively more operational without losing its original logic. This requires a cascade—not simply a flow of messages, but a chain of increasingly concrete choices.

1. Strategic intent: Where are we going, and why does it matter?
2. Strategic choices: What will we do—and not do?
3. Enterprise priorities: Which few commitments must shape investment and attention?
4. Decision rules: How should teams make aligned choices when conditions are ambiguous?
5. Resource commitments: Which budgets, people and capabilities are protected?
6. Coordinated work: How will interdependent teams execute across boundaries?
7. Observable outcomes: What real-world effects will show whether the strategy works?

The cascade does not mean that senior leaders decide everything and lower levels merely comply. It means that each level receives enough clarity to make decisions consistent with the whole. A strong cascade creates distributed judgment. A weak cascade creates distributed guessing.

This is where organizational sensemaking becomes essential. Teams need a shared way to interpret changing conditions, distinguish signal from noise and update action without breaking strategic coherence.

The Execution Integrity Model™

Execution integrity is the degree to which strategic meaning remains coherent as it moves from intent to outcomes. High integrity does not mean rigid conformity. It means that choices, decisions, resources, coordination and learning continue to serve the strategic logic, even as execution adapts.

Layer 1: Strategic clarity

The organization makes clear choices and defines what truly matters. Clarity includes exclusions. It allows people to recognize work that is useful but not strategic.

Layer 2: Translation integrity

Strategy becomes concrete priorities, trade-offs and decision rules at every level. Translation integrity is low when each function creates a different meaning from the same words.

Layer 3: Coordination integrity

Functions and teams act as one system toward shared outcomes. Dependencies are visible, handoffs are designed and conflicts are resolved according to enterprise priorities rather than political power.

Layer 4: Commitment integrity

Resources, incentives, authority and leadership attention support the declared priorities. Commitment integrity is broken when the new strategy is funded by leftover capacity while the old strategy keeps its structural advantages.

Layer 5: Learning integrity

The organization detects what is working, what is not and what assumptions must change. Evidence can challenge plans and leadership narratives. Learning becomes durable through organizational memory, not merely a lesson noted at the end of a project.

A weakness in one layer can be temporarily hidden by strength in another. Exceptional managers may coordinate around unclear governance. A highly committed team may compensate for poor resource allocation. Leaders may personally unblock decisions. But these heroic workarounds are fragile. They make execution dependent on particular people rather than on a capable system.

The Execution Fragmentation Loop™

Execution failure often triggers a response that makes execution harder.

The loop begins with an abstract strategy. Teams interpret it differently, so local plans diverge. Divergence increases dependencies, rework and conflict. Coordination slows. Leaders see inconsistency and add approvals, reports and oversight. Teams spend more time managing the control system and less time executing the strategy. Results weaken. Leaders conclude that the strategy has not been communicated strongly enough and repeat the message with greater force—without changing the conditions that produce different interpretations.

This loop explains why bureaucracy can grow around strategic initiatives. Control is added to compensate for low trust and inconsistent execution, but every additional layer slows information and decision flow. The organization becomes less able to respond, which creates demand for still more control. Over time, execution problems and organizational bureaucracy become mutually reinforcing.

Breaking the loop requires more than reducing meetings. Leaders must clarify choices, align priorities across functions, redesign critical dependencies, simplify governance and create fast feedback that can change execution.

The Five Execution Friction Zones™

Execution friction is the energy lost as strategic intent encounters ambiguity, competition, delay, dependency and weak learning. Friction is inevitable in complex systems. The goal is not to eliminate every tension. It is to identify where friction compounds and remove it at the source.

Meaning friction

Teams cannot translate strategy into concrete choices. People ask what they should actually do differently. Strategy feels abstract, complex or disconnected from real work.

Priority friction

Strategic work competes with too many existing commitments. Priorities change frequently, urgent work dominates and nothing receives protected attention.

Decision friction

Authority, escalation paths and decision rules are unclear. Decisions take too long, move repeatedly upward or vary depending on who is present.

Coordination friction

Dependencies and handoffs break across functions. Information is lost, teams wait on one another and duplicated work appears as each group protects its local delivery.

Learning friction

Evidence arrives late, is filtered or fails to change execution. Problems are known but remain unresolved. Reports describe the past without shaping the next decision.

Friction should be measured through its effects: decision delay, rework, dependency wait time, duplicated effort, initiative churn, missed outcomes and the cost of unresolved issues. A large volume of activity can hide severe friction. This is why organizations that rely on too many indicators can become less—not more—capable of seeing execution. The problem is explored further in why organizations create too many KPIs.

How to fix strategy execution by redesigning the system

The goal is not to build a perfect plan. It is to create an execution system that preserves strategic intent, coordinates distributed action and learns faster than conditions change.

1. Convert aspiration into explicit strategic choices

   Write the strategy as a set of choices, not only goals. State the target outcome, the customers or problems that receive preference, the capabilities that matter, the trade-offs that leaders accept and the work the organization will stop.

   A useful test is whether two reasonable opportunities can be compared using the strategy. If every opportunity can be described as “strategic,” the strategy is not selective enough to guide execution.

2. Translate choices into decision rules

   Decision rules help teams act without waiting for executive interpretation. They might define when to prioritize customer speed over internal efficiency, when to standardize rather than customize, which risks can be accepted locally and which conditions require escalation.

   Rules should be few, concrete and connected to strategic logic. They are not procedures for every situation. They are guardrails for judgment.

3. Map the execution architecture

   Identify the decisions, capabilities, dependencies, resource constraints and feedback channels through which the strategy must move. Map where value crosses functions and where no one owns the end-to-end outcome.

   This is not simply an organization chart. It is a map of how work actually travels: who needs information, who can decide, where queues form, which handoffs fail and which legacy systems preserve old behavior.

4. Remove contradictory commitments

   Every strategic priority should trigger an explicit portfolio conversation. Which work will stop? Which service level will change? Which approval can disappear? Which target is no longer relevant? Which project no longer justifies scarce capacity?

   Without subtraction, strategic execution becomes additive overload. The organization creates complexity instead of clarity—a pattern examined in why organizations create complexity instead of clarity.

5. Align resources, incentives and authority

   Move budget, people, specialist time and leadership attention toward the strategic priorities. Review whether performance measures reward the behavior the strategy requires. Give outcome owners enough authority to resolve conflicts across functional boundaries.

   Alignment research has long examined the relationship between functional priorities and organizational performance, reinforcing the practical importance of coherence between enterprise strategy and local priorities.⁶

6. Build cross-functional execution loops

   Replace periodic reporting with recurring cycles that connect observation, interpretation, decision, action and learning. A useful rhythm may include weekly operational decisions, monthly strategic reviews and quarterly outcome reviews—but cadence should follow the speed at which evidence becomes decision-relevant.

   The purpose of the forum is not to display status. It is to resolve dependencies, update assumptions, move resources and decide what changes next.

7. Measure effects, not only activity

   Track four perspectives: activity, progress, effects and learning. Activity shows what is being done. Progress shows whether commitments advance. Effects show whether customer or business outcomes change. Learning shows whether evidence improves the next action.

   When dashboards contain only activity, leadership receives the appearance of execution without evidence of strategic impact.

8. Adapt execution without abandoning direction

   Create explicit thresholds for adaptation. What evidence would justify changing an assumption? When should a team alter the route, seek more capacity or stop an initiative? Which strategic choices are stable, and which are experiments?

   This protects the organization from two failures: rigidly executing an obsolete plan and constantly changing direction before learning can accumulate.

The Execution Health Flywheel™

Once the most damaging friction is removed, execution can become self-reinforcing.

Clear direction improves alignment. Alignment enables focused execution. Execution produces evidence. Evidence improves learning. Learning helps the organization reinforce what works and repair what does not. Each turn makes the next turn easier because the system develops shared language, stronger decision patterns and more reliable feedback.

The flywheel is not a promise of frictionless execution. Complex organizations will still face disagreement, uncertainty and competing demands. The difference is that healthy systems convert those tensions into decisions and learning rather than into hidden delay and political workarounds.

The Execution Operating System™

An execution operating system is the connected set of priorities, decision rights, coordination mechanisms, measures, learning loops and governance practices that repeatedly turns strategy into results.

The idea of an operating model is not new. MIT CISR’s work on enterprise architecture, for example, emphasizes the importance of defining the processes a firm must execute well and building a foundation that supports those capabilities.⁷ The System Shaping perspective extends that logic beyond formal process and technology to include incentives, attention, meaning, authority, memory and feedback.

1. Set direction

Clarify priorities, intended outcomes, trade-offs and success measures.

2. Align and commit

Align teams, resources, incentives and authority around what matters most.

3. Execute and adapt

Enable teams to act with focus and change their approach when conditions require it.

4. Measure and monitor

Track leading indicators, strategic commitments, meaningful outcomes and emerging risks.

5. Learn and improve

Turn evidence into decisions, embed lessons and update the system rather than merely recording problems.

6. Sustain and govern

Reinforce what works, remove recurring friction and maintain accountability without creating unnecessary control.

This is where strategy execution becomes System Shaping. Leaders cannot personally command thousands of daily decisions. They shape the conditions under which those decisions occur: what information moves, who has authority, which behavior is rewarded, how dependencies are governed, what the organization remembers and whether reality can correct the plan.

The Executive Execution Dashboard™

Many executive dashboards confuse motion with progress. A balanced execution view distinguishes four perspectives.

Activity: What are people doing?

Examples include tasks completed, time invested, meetings held, experiments run and blockers raised. Activity is necessary, but it cannot prove that a strategy works.

Progress: Are commitments advancing?

Track milestone quality, initiative movement, resource deployment, dependency resolution and whether commitments remain on course.

Effects: Are we changing what matters?

Measure customer, operational, financial, capability or risk outcomes connected to the strategic logic. Effects reveal whether the work creates real value.

Learning: What are we discovering and changing?

Track assumptions tested, insights captured, actions changed, problems retired and evidence that altered resource allocation or strategic choices.

A dashboard becomes useful only when it changes conversation and action. Review all four perspectives. Look for patterns rather than isolated numbers. Use data to inform, not blame. Set a rhythm that matches the decision horizon. Close the loop by recording what was decided, what changed and what evidence will be reviewed next.

The Strategy Execution Diagnostic™

Score each statement from 0 to 1: award one point when the statement is consistently true across the organization, not only in a high-performing team.

The score is less important than the pattern. A low result in decision rights requires a different intervention from a low result in learning integrity. Do not average away the bottleneck. Identify the layer or friction zone that constrains the whole system.

A practical 90-day execution-system reset

Days 1–30: expose the real execution system

• Clarify the strategic choices and intended outcomes.
• Map active initiatives, capacity and hidden commitments.
• Trace two or three critical decisions from signal to action.
• Map cross-functional dependencies and recurring handoff failures.
• Compare leadership language with resource allocation and incentives.

Days 31–60: remove the highest-leverage friction

• Stop or pause work that no longer supports the strategy.
• Define decision owners and escalation thresholds.
• Create outcome ownership across functional boundaries.
• Simplify one governance mechanism that delays action without improving judgment.
• Protect capacity for the few strategic priorities.

Days 61–90: establish the execution rhythm

• Launch a balanced dashboard covering activity, progress, effects and learning.
• Establish recurring cross-functional decision and learning loops.
• Record assumptions and define evidence that would change execution.
• Embed lessons into processes, decision rules and organizational memory.
• Review the execution system itself—not only the initiatives inside it.

Large redesign programs often fail because they attempt to change every structure at once. A safer approach is to identify the smallest set of organizational conditions that constrain the strategic outcome, then redesign them without destabilizing essential operations. See how to redesign an organization without breaking it.

Common mistakes when improving strategy execution

Communicating the strategy more often without making it more concrete

Repetition cannot resolve ambiguity that originates in the strategy itself. Communication should clarify choices, trade-offs, decision rules and implications for real work.

Adding a strategy office that owns execution for everyone

A strategy office can coordinate, synthesize and facilitate decisions. It becomes harmful when functions treat execution as someone else’s responsibility or when the office creates reporting machinery without authority to resolve systemic constraints.

Using accountability as a substitute for authority

People cannot be meaningfully accountable for outcomes they lack the authority, information or resources to influence.

Measuring everything

More metrics can create less clarity. Choose measures that reveal whether strategic assumptions hold, commitments advance, outcomes change and learning alters action.

Launching transformation without changing the operating system

A transformation can succeed in a pilot while failing to scale because enterprise structures, incentives and dependencies remain unchanged. This is explored in why organizational transformation fails to scale.

Designing for compliance instead of learning

Compliance can produce predictable process adherence, but strategy unfolds under uncertainty. Execution systems need sufficient governance to protect coherence and sufficient freedom to interpret new evidence.

Strategy execution as System Shaping

Traditional execution advice often asks leaders to clarify, communicate, align and hold people accountable. These actions can help, but they remain incomplete when the organization’s deeper conditions preserve the old pattern.

System Shaping treats execution as the deliberate design of conditions that make desired patterns more likely. The unit of change is not only the individual, process or project. It is the relationship between meaning, authority, incentives, resources, information, coordination, memory and feedback.

From this perspective, leaders shape execution by asking:

• What information becomes visible, and what remains hidden?
• Who can make which decisions, at what speed and with what guardrails?
• Which outcomes are rewarded, and which contradictions are tolerated?
• Where do dependencies create queues, rework or local optimization?
• Can evidence change the plan, or must reality conform to the narrative?
• What does the organization remember after people, projects and leaders move on?

This approach connects strategy execution with organizational intelligence. An intelligent organization does more than collect information. It can perceive reality, create shared meaning, coordinate action, learn from effects and change its own operating conditions.

Frequently asked questions

Why does strategy execution fail?

Strategy execution fails when strategic intent loses coherence as it passes through priorities, decisions, resources, incentives, coordination and feedback. Common causes include abstract strategy, too many priorities, unclear decision rights, local optimization, unmanaged dependencies and weak learning loops.

What is the strategy–execution gap?

The strategy–execution gap is the distance between an organization’s declared strategic intent and the decisions, investments, actions and outcomes it actually produces. It grows through vertical distortion, horizontal fragmentation and the gradual erosion of priorities under short-term pressure.

What are the biggest barriers to strategy implementation?

The biggest barriers are usually unclear choices, priority overload, contradictory incentives, insufficient resources, slow decisions, cross-functional silos, activity-based measurement and feedback that cannot change action.

Is poor execution a leadership problem?

Leadership strongly shapes execution, but the problem is rarely explained by one leader’s behavior. Leaders influence the organizational conditions—decision rights, resources, incentives, governance and information flow—that make coordinated execution easier or harder.

How can an organization improve strategy execution?

Make strategic choices explicit, translate them into decision rules, remove contradictory commitments, align resources and incentives, map dependencies, create cross-functional decision loops, measure effects rather than only activity and adapt execution when evidence changes.

What is an execution operating system?

An execution operating system is the connected set of priorities, decision rights, coordination mechanisms, measures, learning loops and governance practices that repeatedly converts strategy into results.

How do organizational silos affect execution?

Silos encourage functions to interpret strategy through local objectives. They hide dependencies, weaken end-to-end ownership and create decisions that are rational for one department but harmful to the enterprise outcome.

What role do feedback loops play in strategy execution?

Feedback loops connect real-world effects to new decisions. They allow the organization to test assumptions, detect weak signals, adjust resource allocation and improve execution before problems become irreversible.

How should leaders measure execution?

Use four perspectives: activity, progress, effects and learning. This prevents leaders from mistaking busyness for progress and ensures that evidence can change the next action.

What is the difference between strategy execution and change management?

Strategy execution turns strategic choices into coordinated outcomes. Change management typically focuses on helping people and organizations transition from a current state to a desired state. Execution may require change management, but it also includes resource allocation, decisions, operating models, governance, coordination and learning.

Strategy does not execute itself

Why strategy execution fails is not a mystery that can be solved by another slogan about accountability. Strategies fail to become results when the organization cannot preserve their meaning through the system that allocates attention, authority, resources and action.

A strategy becomes real only when it changes choices. Choices become real only when they change priorities. Priorities become real only when they change resources, decisions and coordination. Execution becomes sustainable only when outcomes create learning—and learning changes the system.

The leadership task is therefore not to push the organization harder through the same architecture. It is to shape an execution system in which clear intent can become coordinated, adaptive action.

Continue exploring organizational execution

Selected research and further reading

1. Friesl, M., Stensaker, I., & Colman, H. L. “Strategy implementation: Taking stock and moving forward.” Long Range Planning (2021). Research overview.
2. Tawse, A., & Tabesh, P. “Strategy implementation: A review and an introductory framework.” European Management Journal (2021). Research overview.
3. Sull, D., Homkes, R., & Sull, C. “Why Strategy Execution Unravels—and What to Do About It.” Harvard Business Review (2015). Article.
4. Unger, B. N., Gemünden, H. G., & Aubry, M. “The three roles of a project portfolio management office: Their impact on portfolio management execution and success.” Related research on senior-management involvement and project termination quality. Research overview.
5. Heide, M., Grønhaug, K., & Johannessen, S. “Exploring barriers to the successful implementation of a formulated strategy.” Scandinavian Journal of Management (2002). Research overview.
6. Joshi, M. P., Kathuria, R., & Porth, S. J. “Alignment of strategic priorities and performance.” International Journal of Organizational Analysis (2003). Research overview.
7. Ross, J. W., Weill, P., & Robertson, D. C. Enterprise Architecture as Strategy: Creating a Foundation for Business Execution. MIT CISR / Harvard Business School Press (2006). MIT CISR summary.

The article intentionally avoids repeating universal “strategy failure rate” claims because definitions and measurement approaches vary substantially across sources.