Blog Details

Strategy Implementation

Most strategies fail in the doing, not the design. The five points where implementation breaks down, the questions to ask at each, and how to create the conditions for a strategy to take root.

Strategy Implementation

The gap between the plan and the business

A strategy is a roadmap. It only becomes a journey in the doing. Businesses invest heavily in strategy development: where the opportunities are, what the future should look like, how growth will be achieved. At the end of that phase there is a clear vision, and nothing in the business has actually changed.

The gap is well documented. In an Economist Intelligence Unit survey for the Brightline Initiative, 61% of senior executives said their organisations struggle to bridge the gap between strategy formulation and day-to-day implementation. In our experience the gap opens at five predictable points. Knowing where they are is most of the battle.

1. Old capabilities, new tricks

Picture a steam engine on a railway. The operating model is simple: coal in, steam up, go. When you need to change direction or pace, you need enough fuel, track and crew to keep moving. If any of those fail, the engine slows to a halt or leaves the rails.

Now suppose the strategy is to switch to electric. Same business, entirely different operating model: new trains, new expertise, new infrastructure. Bold choices do not create change by themselves. Implementation is the work of laying the supporting framework, and without adapting the organisation's structures and capabilities to what the strategy needs, momentum and support drain away.

Adaptation means training, hiring, new tools, new systems and workflows, sometimes new regions. These are costs with a budget line, and that line belongs in the strategy itself. If it is not there, you are not ready to implement.

Ask yourself: Have you defined your target operating model? Do you know where capital needs to go to make it real? How will you support staff as they adapt?

2. The daily grind

Everyone knows the feeling: too busy doing the work to step back from it. But strategy does not sit on top of business as usual, and it cannot be squeezed into two hours on a Friday. It has to be at the top of the list and lived every day.

Creating capacity is a deliberate act. It may mean temporary hires so the day job does not pile up, reorganised workflows, or saying no to some business as usual to protect strategic priorities. A one-year horizon works well: clear targets, key actions, a defined RACI, resources and risks.

Ask yourself: Have you created capacity for implementation? How will you cope with the daily grind? Have you told people that priorities have changed?

3. The forest for the trees

Busyness produces a second trap. The energy of a new strategy launches a programme of activity, and people get so caught up ticking off tasks that nobody asks which ones actually move the strategic objectives. Everyone is busy. The parts are not pulling together.

This traces back to whether the strategy work identified the one-year priorities, the few projects with the biggest impact on the new direction. The best implementation plans include early quick wins to build faith in the strategy, and a person or team whose job is to keep activity from being mistaken for progress.

Ask yourself: What are the most important projects driving your strategy? Who decides priority? How are you measuring progress?

4. Mission without control

Strategy is usually developed by a small team at the top. If that team launches it and dusts off its hands, it will not land. Implementation is an active, managed process.

Objectives and Key Results (OKRs) are a practical tool here. Teams define their own objectives in line with the strategy, key results give management a way to check progress, and both can be redefined as the work evolves. OKRs are more flexible than top-down KPIs and give teams the autonomy to execute while keeping leadership in control.

Ask yourself: Are teams clear enough on the vision to set their own objectives? How will you define key results? What keeps teams moving forward?

5. Hearts and minds

The most common failure of all. Inside the small circle that wrote it, the strategy is clear and feels right. Step outside and ask the people who will do the work: do they understand the vision, do they know their role, do they feel part of it or subject to it?

Winning hearts and minds deserves real time. Tell the strategy as a story in terms people can relate to. Pare it down to an elevator pitch. If it cannot be told quickly and simply, it will not capture the wider team.

Ask yourself: Is the strategy story clear? Is the team engaged? Could they retell it in their own words?

Creating the conditions for success

None of these failures is inevitable. With a defined operating model, protected capacity, a short list of priority projects, a control framework teams can own, and a story people can repeat, implementation becomes the turning point where the strategy takes root and the growth you planned for arrives.

Get clear on what needs to happen, who will do it, what they need, and how you will know whether you are on course. Then ask the hard questions above, and keep asking them.

Where Good Analysis fits

We work with leadership teams to close the gap between strategy and execution: defining target operating models, creating implementation capacity, prioritising projects, setting up OKR frameworks, and crafting strategy narratives that engage every level. See Positioning & Messaging for the narrative work and Platforms & Process for the systems that make new ways of working stick.

Compelling Value Propositions

Compelling Value Propositions

A value proposition is a promise you can keep and a competitor cannot. How to find the sweet spot between customer need, competitor weakness and your own capability, and how to tell whether yours is working.

3 minute read
3 minute read
Distinctive Growth Strategies

Distinctive Growth Strategies

Sustained outperformance is a system, not a run of luck. What the companies that grow faster than their market for years do differently, and how to tell whether your organisation is built for it.

3 minute read
3 minute read
Choosing Java or Python

Choosing Java or Python

The decision is not which language is better. It is which one fits your team, your workload and the next five years of maintenance. A practical checklist for leaders.

3 minute read
3 minute read