Why Strategic Initiatives Lose Momentum Even When the Plan Is Sound
- Karlene A. Millwood, MBA
- Aug 10
- 8 min read
An IMPACT™ examination of why strategic priorities lose momentum between intention and execution
Leadership Insight Series | Part Two of Three
The Initiative Was Not Stalled by Strategy. It Was Stalled by the System.
For a brief period, the organization began to move differently.
Leaders who had rarely interacted started sharing information. Teams developed a clearer understanding of how their work connected. A critical operational process was revamped. A strategy-execution initiative that had been struggling began producing measurable improvements.
The change did not begin with a new strategy. We had not introduced new technology. The organization had not hired more people. There was no sweeping restructuring or additional budget. What changed was that people could finally see the work and each other. They understood where processes were breaking down, how responsibilities intersected, where information was getting trapped and what was preventing the work from moving.
The meeting did not create capability. It released capability that was trapped in the system.
That distinction matters because organizations frequently respond to stalled execution by asking people to work harder, report more often or recommit to the plan. Yet effort cannot compensate indefinitely for unclear ownership, fragmented information and decision pathways that repeatedly delay action. The organization had a strategy.
What it did not have was a shared operating picture.
The Strategy Was Visible. The Work Was Not.
In Part One of this series, I described entering a large organization to lead a strategy-execution initiative with a team of approximately eight people.
The initial symptoms appeared interpersonal. Employees were guarded. Routine questions created anxiety. Teams communicated cautiously, and strained relationships among leaders were affecting the people responsible for carrying out the work.
But beneath those behaviours was an execution problem.
People were unclear about processes, roles and responsibilities. Teams were working around one another rather than with one another. Managers were spending their time putting out fires. Accountability varied depending on the person or situation.
These were not minor workplace irritations. They were operating conditions that determined whether strategy could advance.
Gallup’s midyear 2026 findings show that only 49% of U.S. employees strongly agreed that they knew what was expected of them at work. That figure had improved slightly from 2025, but remained well below the 61% recorded in 2015.
If half the workforce lacks strong clarity about what successful contribution requires, organizations should expect more than employee frustration. They should expect delayed handoffs, competing priorities, duplicated work and inconsistent performance.
Strategic initiatives do not usually stall in the strategy document.
They stall at the handoffs.
When Activity Conceals Immobility
The organization was busy. Meetings occurred. Managers responded to urgent issues. Employees completed tasks. Leaders made decisions. Yet activity and execution are not the same.
Execution is the coordinated movement of an organization towards a defined outcome. It requires people to understand not only their individual assignments, but also how information, authority, timing and dependencies connect across the system.
Without that shared understanding, every team can appear productive while the larger initiative remains stationary.
Atlassian’s 2025 research illustrates how common this fragmentation has become. It found that 56% of knowledge workers said their organization lacked a consistent approach to planning and tracking work, making collaboration more difficult. Even more telling, 50% had worked on a project only to discover later that another team was working on the same thing.
I watched a version of that problem surface in the meeting I convened. Teams discovered they had been attempting to solve the same problems separately.
The duplication was not evidence of laziness or incompetence. People were responding to the work visible from their own part of the organization. No one had given them a reliable view of the whole.
When information does not travel, employees compensate locally for problems that require an organizational response. They create workarounds. They repeat tasks. They escalate the same issue through different channels. They carry responsibilities that belong elsewhere because allowing the work to fail feels worse than absorbing the additional burden. The organization then mistakes this activity for progress, but activity can conceal immobility.
Four Questions Changed the Operating Picture
To see what was obstructing the initiative, I brought multiple teams and leaders into one room.
I asked four questions:
How well do you understand our operational processes?
How clearly do you understand your role within the structure?
What is working—and what is not?
Where are breakdowns affecting your work, your team or the organization?
The questions were simple. Their value came from asking them across organizational boundaries and allowing the answers to interact. One team’s obstacle was another team’s missing information. One manager’s urgent workaround was creating additional work elsewhere. Employees who had previously seen only isolated symptoms could now identify patterns. The room became a live picture of the organization at work.
A colleague with more than twenty years in the organization said, “Never in my career here have we had a meeting like this. It was needed.”
Shortly afterwards, a director told me that he had resigned because he could no longer tolerate the environment. After the meeting, he decided to withdraw his resignation. For the first time, he said, he felt understood. What changed his mind was not a retention incentive or a revised title. The meeting restored a credible connection between his experience and the organization’s capacity to respond.
That connection affects more than morale. PwC’s 2025 Global Workforce Hopes and Fears Survey, which included nearly 50,000 workers across 48 countries and regions, found that employees who felt most strongly connected to leadership goals were 78% more motivated than those who reported the weakest connection.
People do not execute strategy simply because leaders have announced it.
They execute when they understand the destination, can locate their contribution within it and believe the organization will address the obstacles standing between intention and results.
What IMPACT™ Reveals
IMPACT™ is KMI’s proprietary strategic planning and execution methodology. It examines how organizations move from understanding current conditions to sustaining meaningful change. Viewed through the IMPACT™ lens, the intervention revealed six requirements of execution.
Investigate: See the conditions beneath the symptoms
The visible symptoms were guarded conversations, strained relationships, recurring delays and inconsistent accountability. Investigation required looking beyond those individual manifestations. By checking in with employees, visiting other teams and observing how work moved, I could see that the same difficulties were recurring across boundaries.
The essential question was not, “Who is failing?”
It was, “What conditions keep producing these outcomes?”
That shift prevents organizations from assigning individual blame for structurally generated problems.
Map: Make the whole system visible
Employees understood portions of the work, but few could see how the pieces connected. Bringing teams together allowed the organization to map the distance between intended processes and lived operations. Roles, dependencies and communication gaps became visible in relation to one another. A strategy cannot be executed collectively if it is understood only departmentally.
Prioritize: Distinguish root constraints from recurring noise
Firefighting had become normal. Urgent issues consumed attention, while the conditions generating them remained intact.
The discussion helped separate symptoms from the constraints requiring leadership attention: unclear processes, restricted information flow, inconsistent ownership and a recurring decision bottleneck.
Prioritization is not simply choosing which task comes first. It is identifying which few conditions are restricting progress across multiple areas of the organization.
Align: Connect roles, authority and operations
In organizational language, “alignment” is often treated as agreement. But agreement alone does not move work.
Operational alignment exists when people know:
what outcome they are responsible for;
where their authority begins and ends;
what information must move between teams;
which decisions require escalation;
and how their work affects the next person in the process.
The meeting created this clarity. Leaders began sharing information. Teams understood their interdependencies. The initiative gained momentum because people could act with a more accurate view of the system.
Cultivate: Turn isolated clarity into operating practice
One effective meeting can release energy. It cannot, by itself, establish a new way of working. The gains continued because communication changed, teams applied what they had learned and a critical operational process was revamped. Clarity began moving from conversation into practice.
This is where many initiatives weaken. Organizations celebrate the breakthrough but fail to establish the responsibilities, routines and oversight required to preserve it.
Transform: Build change that can survive resistance and transition
Not everyone welcomed the meeting or what it revealed. One leader objected because the meeting had proceeded without their involvement. Yet their involvement had repeatedly contributed to a decision bottleneck, and the initiative required movement.
Although the work was producing positive results, my contract was later terminated without a documented performance review or specific examples supporting the stated concern about my work. The matter eventually resolved itself.
Through an execution lens, this ending reveals something important: the process had changed faster than the authority arrangements surrounding it. The organization had experienced improvement, but it had not yet built the institutional capacity to protect the conditions producing that improvement.
An initiative is not transformed because results improve temporarily. It is transformed when the organization can preserve the conditions that produced them.
The Bottleneck Was Not Only Procedural
Organizations often treat bottlenecks as process defects: an approval takes too long, a handoff repeatedly fails or information arrives too late, but bottlenecks can also be behavioural and structural.
Decision authority may be overly concentrated. Leaders may interpret independent action as exclusion. Teams may withhold information until permission is secured. Employees may learn that moving the work forward creates more personal risk than allowing it to stall. Under those conditions, the formal process map tells only part of the truth. The organization must examine what people actually have to navigate to produce an outcome.
That includes:
how authority is exercised;
where information stops;
which problems repeatedly require workarounds;
whose cooperation determines whether a priority advances;
and what happens when someone challenges an ineffective pattern.
Strategy becomes executable when the designed process and the lived process begin to match.
Strategy Needs an Organization Capable of Carrying It
The initiative in my story did not regain momentum because employees were pushed harder. It moved because people were finally able to see the work as an interconnected system. They could name the obstacles. They could understand one another’s roles. They could identify duplicated effort. They could connect their daily responsibilities to the broader outcome.
That is the difference between communicating a strategy and building the conditions for execution. A strategy does not fail only when people reject it. It also fails when the organization makes it unnecessarily difficult to carry out.
Before launching another initiative, leaders should therefore ask:
Can employees explain the intended outcome in operational terms?
Are roles and decision rights clear at the points where work crosses boundaries?
Does essential information reach the people who need it in time to act?
Are teams addressing shared problems together—or solving them repeatedly in isolation?
Can the organization remove a bottleneck even when that bottleneck is protected by status or habit?
Will the new operating conditions survive a change in leadership, personnel or attention?
The answers reveal whether the organization has more than a plan.
They reveal whether it has the capacity to carry one.
Strategy sets direction. Execution depends on whether the organization can move as one system.
Continue the Leadership Insight Series
This is Part Two of a three-part series examining the same organizational experience through KMI’s proprietary frameworks.
Part One — The PRISM™ Lens: Values Do Not Govern Organizations. Systems Do. examined the ethical infrastructure that shapes trust, authority, candour and accountability.
Part Three — The EMERGE™ Lens: When Leadership Capability Exceeds the System’s Willingness to Recognize It. will examine what happens when a high-capacity woman demonstrates the courage, judgment and influence an organization claims to value—but her leadership disrupts patterns the system has learned to protect.
A KMI Strategic Diagnostic examines leadership, governance, culture and execution as an integrated system—identifying where unclear priorities, fragmented ownership, restricted information and decision bottlenecks are delaying results.
Comments