logo

Strategy execution: why strategies fade into daily business and what helps

Most strategies don't fail because of the idea. They fail because by January, nobody remembers what was decided in November. Three things that keep a strategy alive in daily business.

By Christian Underwood ·

Ein offener Rahmen, aus dem Faeden zu kleinen Markierungen laufen; die meisten verblassen, einer erreicht sein Ziel.
Contents (7 sections)
  1. What actually makes strategy execution fail?
  2. How does the strategy get from paper into the calendar?
  3. What methods are there and what do they deliver?
  4. How do strategy and budget fit together?
  5. Who owns execution in the leadership team?
  6. What signals show early that it's fading?
  7. Common questions about strategy execution

What actually makes strategy execution fail?

Not a lack of will, and rarely the quality of the strategy. The break happens at a point you can see in the calendar.

After the decision phase, energy is high and everyone feels done. That feeling lasts about three weeks. Little happens during that time because everyone is catching up on the daily business they let slide. After that, daily business has reclaimed the calendar, and the strategy has no fixed place in it.

The second break comes later and is more dangerous: after six months, nobody remembers exactly **why** a decision was made the way it was. The decision is in the document, the reasoning isn't. So it gets reopened at the first sign of resistance.

How does the strategy get from paper into the calendar?

Three things, and none of them is a tool.

  • One page, not thirty. What doesn't fit on one page won't be remembered. The long version can exist, but the one page is what sits on the table in meetings.
  • Every initiative has a name. Not a department, a person. "Sales will take care of it" is the most reliable way to make sure nobody does.
  • A fixed date that doesn't get moved. One hour every two weeks is enough. What matters isn't the length, it's that it happens, even when there's little to report.

The third point is where things usually tip over. A meeting that has been postponed twice stops happening, and from then on the strategy runs without feedback.

What methods are there and what do they deliver?

Three are common in mid-sized companies, and they solve different problems.

Method

Solves

Limit

OKRs

Translates the strategy into quarterly goals and makes progress visible.

Requires a direction that has been decided. The quarterly rhythm doesn't fit every business.

Hoshin Kanri

Connects annual goals with measures and clarifies who contributes what.

Requires discipline to maintain and quickly feels over-engineered in smaller mid-sized companies.

Initiative planning with review dates

The simplest approach: a list of initiatives with owners, deadlines and a fixed rhythm.

Shows progress, but not automatically whether the goal is getting closer.

For most mid-sized companies, the third one is the right choice, at least in the first year. If you start with OKRs before the strategy is settled, you're building a goal hierarchy on top of an open question.

How do strategy and budget fit together?

More closely than most processes reflect. In many companies, strategy and budget planning run separately, with different people and at different times. The result is predictable: the strategy names initiatives that have no money behind them in the budget.

The test is simple and uncomfortable. Take the three most important initiatives from your strategy and check whether they show up in next year's budget. If they don't, the decision hasn't been made, it has only been spoken.

The same works in reverse: if large budget items aren't connected to any strategic initiative, you're doing things that no longer have a strategic reason. Usually there was one at some point.

Who owns execution in the leadership team?

One person, and it shouldn't be the CEO.

The reason is practical: the CEO has the fullest calendar and the most reasons to move a meeting. Whoever owns execution mainly needs persistence in following up, not decision-making authority.

In companies with between one hundred and one thousand employees, this is often the CFO or a division head with a broad view. What matters is that the role is named and reflected in the calendar.

What signals show early that it's fading?

  • The review meeting gets postponed a second time. That's the most reliable early warning sign, and it usually shows up in week six to eight.
  • Nobody can name the priorities from memory. Ask three people from the leadership team separately about the three most important initiatives. If you get three different answers, the strategy hasn't landed.
  • Initiatives get started but never finished. If twelve projects are running after six months and not one is done, you didn't prioritize, you collected.
  • New projects show up that aren't part of any strategy. That always happens. It's only a problem when nobody notices.

Common questions about strategy execution

Why does strategy execution fail?

Usually not because of the strategy, but because of the missing structure that should follow it. After the decision phase, the energy lasts about three weeks, then day-to-day business has the calendar back. Without a fixed review date, the strategy runs from that point on without any feedback.

What methods are there for strategy execution?

OKRs for quarterly management, Hoshin Kanri to connect annual goals with concrete measures, and plain initiative planning with fixed review dates. For most mid-sized companies, the third one is the right choice in year one.

How are strategy execution and budgeting connected?

Very closely, though in many companies the two processes run separately. The test: do the three most important initiatives show up in next year's budget? If not, the decision was announced but never actually made.

How often should progress be reviewed?

One hour every two weeks is enough. What matters isn't the length, it's that the meeting actually happens, even when there's little to report. A meeting that gets postponed twice usually never happens at all.

Related