Anyone can create a strategic plan. Executing one is a different job.
I've led strategy execution work for 16 years, mostly with mid-market organizations, and many of them across multiple planning cycles. Working with the same leadership team over several years shows you what drives success and what quietly undermines it. The patterns below come from watching plans succeed and fail in the room, not from theory. You can watch the full webinar above, and download the strategy execution checklist to work through with your team.
A strategic plan is typically an 1,100 to 1,500 day commitment. It is a multi-year scope of work, not a document. That long timeframe is part of the problem: it lets ambiguity survive for quarters before anyone notices a project hasn't moved.
Here are the eight reasons I see execution stall, and what to do about each one.
1. Managers weren't engaged in the planning
The common pattern: the executive team or board goes on retreat, builds the plan, and pushes it down. Managers are expected to follow. In principle that makes sense. In practice it creates resistance, because managers feel the plan was built without understanding what they deal with every day.
The fix is to hear from your managers before you plan. Bring your top 20 or 30 managers together for a listening session of about two hours, or run a survey. Ask what's going well, where the sticking points are, and what winning looks like to them.
You don't treat their input as gospel. You use it as an input, then go back to them with the plan and show them where their concerns landed. When they can see the alignment, rollout gets easier, early wins come faster, and change holds longer.
There are more of them than there are of you. The faster the plan gets out of your hands and into theirs, the faster it moves.
2. Alignment was implied, not explicit
When I review strategic plans, I often see visions open to interpretation, missions with several competing focus areas, and five strategic priorities where three would do. Each of these creates a small fissure.
Teams can leave a planning session in full agreement and still drift apart over the following months, because they're running on different assumptions about what the plan means. Once people prioritize differently, they resource differently, and execution fractures.
A strategic plan is a tool for decision making when you're not in the room. It should tell people what to do and what not to do. Make your destination explicit, keep priorities few and clear, and test them in the room: ask whether anything is missing or unclear. Then keep checking for drift as new information comes in.
3. No clear ownership or structure
Important initiatives need someone to drive them and someone to approve them. When that isn't defined, you get the most common form of tactical stuckness: "I thought they were doing it."
Assign a single owner to each strategic priority, and a single accountable person for each goal or major initiative underneath. Other people can contribute. Ownership sits with one person, not a group.
On a two-week deliverable, missing ownership gets exposed fast. On an initiative that spans several quarters, it can go unnoticed for most of a year. A simple RACI matrix and a regular follow-up structure close that gap.
4. Resources weren't reallocated
Every organization has limits on money and people. The plan gets built with real ambition, and leaders leave believing all of it is achievable.
What gets missed is that two trains are running at once: the new strategic plan and all the operational work already underway. Most leadership teams assume the new work can simply be added on top. I haven't met many senior leaders at ambitious organizations sitting around waiting for more work.
The conversation that rarely happens is what the team will stop doing. One billion-dollar organization I worked with had a list of 30 high-priority initiatives. We deprioritized the bottom 20%, elevated the top 20%, and set a clear order for the rest.
With another client, a project team was expected to spend about 25% of its time on strategic work. That meant peeling off the bottom 25% of their existing workload and delegating it. If you stack priority work on top of a full plate, the high-value work is what gets stuck.
5. Resistance wasn't anticipated
Two or three days of planning lead to 1,100 days of execution. Even when the vision is compelling, change affects everyone, and some people will push back. That includes people the plan objectively benefits.
The gap is when leaders read resistance as a problem with the person. Resistance to change is normal human behavior, and it often means someone is thinking seriously about what the plan means for them.
Name the likely areas of resistance during planning and in your management conversations. Build a plan to support people through them. If a plan didn't generate resistance, you'd probably have achieved it already.
6. Accountability existed on paper only
Accountability breaks down at two levels. The first is structural: if the plan only gets discussed once a year, or even once a quarter, the rhythm is too slow.
The second is behavioral. The check-ins happen, but nobody discusses the impact of a missed commitment. In cultures that prize positivity, that conversation gets avoided. High performers generally welcome clear deadlines and clear scope. Letting people avoid accountability doesn't help anyone.
Strategic initiatives are connected through a critical path. One slipped commitment delays everything downstream, including work tied directly to your mission.
7. Motivation wasn't built at the individual level
Excitement at the rollout isn't the same as motivation when the operational pressure hits. People need a personal stake in the outcome.
If my doctor tells me chocolate will give me a stomach ache, I'll keep eating chocolate. If the doctor tells me it will kill me, I'll stop. The difference is the strength of the motivator.
Expect to do more work creating motivation than you think. That is really just leadership. Pay particular attention to long-tenured employees. They're often your most experienced and invested people, and they're locked into established ways of working. Without a strong enough reason, they're the ones who unintentionally stall the plan. Motivation works person by person, not at the level of the organization.
8. Trust was assumed
Leadership teams often assume trust exists because they get along. The trust that execution requires is deeper: confidence that others will follow through, and the ability to raise difficult issues openly, including personal ones.
Most organizations that have had something go badly wrong can trace it back to people not trusting each other enough to raise it. Treat trust as a capability to build across the board, leadership team, and management layers, not an interpersonal nicety.
The cost of stalled execution
There's the planning process that creates the plan, and then there's the system that supports execution. Most plans that fail have a sound plan and a weak system.
Putting these structures in place can feel expensive. Not putting them in place costs more. Poor execution burns time and money, then shows up as frustration, then as retention and culture problems. The most expensive version is when people start working around a colleague they don't trust or who isn't delivering, and it happens inside the executive team.
For an organization doing $30 million to $300 million in revenue, running 10 or 20% over on the full strategic plan is a significant number. The cost shows up somewhere regardless of size.
Where to start
Every issue on this list is fixable by your own team. The question is how quickly you want it fixed.
Download the strategy execution checklist and walk through it with your leadership team to find your gaps. If speed matters, book a conversation with me and we'll work through your plan and where execution is likely to stall.
Connect with Anthony
LinkedIn: linkedin.com/in/anthonyctaylor604
