Why strategies stall, and the system that carries them to year-end

Strategy execution is the system that links what leadership decided in the plan to what people do each week. It is often treated as an operations matter, something to hand down once the strategy is approved. In practice it is leadership work, because the decisions that keep a strategy moving (what to stop, where money and people go, which delay to accept) can only be made at the top. A system that works has four parts. Translate: choose a few strategic pillars and break each into initiatives with one owner, a measurable outcome and a deadline. Resource: move budget, headcount and the time of the strongest people to those initiatives, instead of spreading them evenly across departments. Review on rhythm: weekly at team level, monthly at leadership level and quarterly at strategy level, on dates booked a year ahead. Adapt: when the numbers or the market show that an assumption was wrong, change the plan deliberately and on the record. The gap between plan and results rarely comes from a weak strategy. It usually comes from one of these four parts missing, most often the third, because it is the only one that has to be repeated every month with no finish line.

Execution starts with subtraction. A company can usually push three to five strategic pillars at once; each pillar breaks into two to four initiatives that must succeed for the pillar to succeed. An initiative is different from daily work: it changes a strategic result, has a start and an end, and needs resources that would otherwise go elsewhere. Alongside the list of what the company will do, leadership should agree a stop list: projects to close or pause, so the people who own the new initiatives have time to drive them. Each initiative then gets a one-page charter. It states the outcome in measurable terms, names one owner with the authority to decide, sets quarterly milestones, records the budget and people committed, names the leading and lagging KPIs, lists the dependencies on other departments, and states in advance the conditions under which the initiative would be changed or stopped. Writing the charter is where vague initiatives reveal themselves: if the leadership team cannot agree on the outcome or the owner in one page, the initiative is not ready to start.

A budget is the strategy expressed in numbers, and when it is built by adding a percentage to last year, it quietly cancels whatever the strategy changed. Four practices keep money and people aligned with the plan. Approve the strategy before the budget, not after it, so the budget round funds the chosen initiatives first. Separate the run budget, which keeps the current business going, from the change budget, which funds strategic initiatives, and protect the second from being used to cover overruns in the first. Release larger initiative budgets in tranches tied to milestones, so money follows progress and a failing initiative can be stopped before it is fully spent. And plan capacity as carefully as money: an owner with a full-time operational role cannot drive a strategic initiative on top of it, so part of their time, and often a few dedicated people, must be freed through the stop list. Linking part of performance reviews to initiative milestones helps, provided the targets are ones the owner can influence; the performance management guide covers how to do this without encouraging people to game the numbers.

The monthly business review (MBR) is where execution either happens or does not. Its quality is decided before the meeting. Data is cut off on a fixed date; each KPI is given a status by a shared definition: green is on plan, amber is at risk but the owner has a recovery plan, red is off track and needs a decision from leadership. Owners of amber and red items write a short note: what happened, why, what they propose, and what they need. The pack goes out two working days ahead and is read before the meeting. In the room, green items are not presented. The agenda follows the exceptions: ten minutes on last month's open actions, most of the time on red items and then amber ones, each closing with a decision, an owner and a date, fifteen minutes on risks and assumptions to watch, and five minutes to read back the decisions. Minutes and the action log go out within one working day, and every open action returns to the next review until it is closed. When the agenda builds itself from what is off track, leadership attention flows automatically to where the strategy is slipping, which is the entire purpose of the meeting.

An execution system does not need a long design phase; it needs a first cycle that runs. In the first two weeks, leadership confirms the three to five pillars, selects the must-win initiatives, names one owner for each and agrees the stop list. By day thirty, each initiative has a one-page charter, the leading and lagging KPIs are defined with baselines, and the review dates for the year are booked. Between days thirty and sixty, the first monthly business review runs in the new format, even if some data is still incomplete; holding the meeting on time matters more than a perfect scorecard. Between days sixty and ninety, the second and third reviews refine the status definitions, the cascade extends to department plans, and KPIs nobody used are removed. Software makes this rhythm cheaper, with one place for actuals, automatic agendas and visible status, but the commitment to a fixed review is a leadership decision no tool can make. An outside team is most useful where internal teams find it hard to be neutral: facilitating the choice of priorities and the stop list, designing the scorecard, and running the first reviews until the rhythm holds without being pushed.