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

What actually makes strategy execution fail?

Not a lack of will, and rarely the quality of the strategy. The breakdown 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 first works through the day-to-day business that piled up. After that, the day-to-day has reclaimed the calendar, and the strategy has no fixed place in it.

The second breakdown 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 pushback.

How does strategy get from paper into the calendar?

The first step is a visible kickoff, not an email. At launch, you carry the strategy into the organization in a way people understand, and set up the foundation at the same time: one central place where everything comes together, the top-level goals, the steering bodies, and a fixed reporting rhythm. Nothing more is needed at this point. What matters is that no communication vacuum follows the bang of the announcement, otherwise your strategy tiger turns into a paper tiger.

Next comes translating it into results. Goals are broken down across all levels, fields of action are turned into initiatives and projects, and the portfolio moves into performance management. The guiding question shifts from the individual project to the whole: are we doing the right things overall, in the right order, with the resources we actually have?

And then one rule decides everything: every report ends with a decision. Prioritize, sharpen, reallocate or stop. A report that is merely noted has cost everyone's time and moved nothing. That calls for lean performance management that steers instead of controls.

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 is that it happens, even when there's little to report. The length is irrelevant.

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 out there, and what do they deliver?

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

For most mid-sized companies, the third 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 involved and on different timelines. The result is predictable: the strategy names projects 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 was only spoken out loud.

This works in the other direction too: 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 a hundred to a thousand employees, that's often the head of finance or a division head with a broad view. All that matters is that the role is named and reflected in the calendar.

What early signals show it's fizzling out?

The most reliable signal is a meeting that gets postponed a second time. Not the traffic light in the report, that stays yellow for a long time anyway. When the monthly review gives way to a more urgent topic twice in a row, the decision about priority has long been made. Nobody just said it out loud.

The antidote is a cadence that's set from the start: a monthly review where teams get room to act, a quarterly sharpening, and once a year a retreat for the big question. This rhythm is the difference between execution that runs and execution that gets administered.

• The review meeting gets postponed for the 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 off the top of their head. Ask three people on the leadership team separately for the three most important initiatives. If you get three different answers, the strategy hasn't landed.
• Initiatives get started but never finished. If twelve initiatives are running after six months and none is complete, you collected instead of prioritizing.
• New initiatives appear that aren't in any strategy. That always happens. It's only a problem when nobody notices.