How to turn business strategy into an execution roadmap

To turn business strategy into an execution roadmap, reduce the strategy to three to five strategic initiatives, give each one a single owner, a start and end date, milestones, dependencies and risks, and then slice the year into 90-day plans that the leadership team reviews on a fixed cadence. The roadmap is the bridge between what the company has decided and what people do on Monday morning. Without it, strategy stays a document. With it, strategy becomes a sequence of commitments that someone is accountable for.

Most growing companies do not lack strategy. They have an offsite deck, a set of ambitions and a founder who can explain where the business is going. What they lack is the translation layer: the point where a direction becomes a short list of pieces of work, each with a name next to it and a date by which it has to land.

Why strategies fail in execution

Strategy rarely fails because the thinking was wrong. It fails in the gap between the decision and the calendar. Work on strategy execution published in Harvard Business Review by Donald Sull and colleagues points to coordination across units and follow-through as the usual breaking points, rather than a lack of agreement at the top. In companies of twenty to three hundred people, the same three causes come up again and again.

• Too many priorities. Twelve strategic priorities is a wish list. When everything is important, teams choose for themselves, and they choose what is urgent or familiar.
• No owners. Initiatives belong to the leadership team, which in practice means they belong to nobody. Progress depends on whoever has spare time that month.
• No cadence. The strategy is reviewed once a year, at the next offsite. In between, nobody asks whether the work is on track until it is clearly not.

Behind those three sits a fourth cause: the strategy is written in a language nobody can act on. Becoming the reference partner in the region is a direction. It is not something a head of operations can put in a plan.

A strategy that cannot be scheduled is not yet a strategy. It is an intention.

From strategy to three to five strategic initiatives

A strategic initiative is a defined piece of cross-functional work, with an end, that moves the company materially towards one of its strategic objectives. It is not a department's business as usual, and it is not a KPI. Opening a second warehouse is an initiative. Improving on-time delivery is a goal that an initiative might serve.

Getting from strategy to a short list usually takes one structured leadership session and some honest cutting.

1. State the outcomes. Write down the two or three things that must be true about the company in eighteen to twenty-four months.
2. List every candidate initiative. Everything currently in flight or under discussion, without filtering. The list is always longer than anyone expects.
3. Score each candidate. Impact on the outcomes, effort, risk and dependence on scarce people. A project prioritisation matrix makes the trade-offs visible rather than political.
4. Cut to three to five. Everything below the line is stopped, deferred to a named quarter or handed back to a department as ordinary work.
5. Name one owner per initiative. One person, at leadership level, accountable for it landing. Contributors can be many. The owner is one.

The cut is the step that matters. A company of ninety people with five initiatives can move all five. The same company with fifteen will move two, and spend the year explaining why the other thirteen are late.

How to structure a strategic roadmap

A strategic roadmap does not need to be sophisticated. It needs to answer the same eight questions for every initiative, in the same place, so the leadership team can read it in ten minutes. Our strategic roadmap template follows this structure.

Slicing the year into 90-day plans

A twelve-month roadmap is too long to manage directly. The working unit is the quarter: each initiative is broken down into what must be true by the end of the next ninety days, and those commitments become the plan for the quarter.

In practice, each initiative owner brings a short proposal to the quarterly planning session: the milestone they will reach this quarter, the two or three pieces of work that get them there, the people they need and the risks they see. The leadership team tests the proposals against each other, because the real constraint is almost always the same handful of people. We cover the mechanics in our guide to the 90-day plan.

Not every initiative needs to be active every quarter. Sequencing is a legitimate decision. An initiative that deliberately starts in the third quarter is in a far better position than one that starts in the first and stalls for six months.

How the roadmap connects to OKRs, KPIs and the review cadence

The roadmap is one part of a business operating system, not a standalone document. It works when everyone can see how each piece relates to the others.

OKRs are a good way to express the quarterly slice of each initiative: the objective describes the milestone, the key results are the evidence that it has been reached. KPIs do a different job. They tell you whether the core business is holding while leadership attention is spent on change. The distinction is covered in OKRs vs KPIs.

The review cadence is what keeps the pieces connected. Initiative owners report against the next milestone in the monthly review, the leadership team re-sequences in the quarterly business review, and the roadmap itself is rebuilt once a year. Robert Kaplan and David Norton, writing in Harvard Business Review, described this as the closed loop that links strategy to operations. Without that rhythm, the roadmap becomes a slide that was accurate in January.

Example: a roadmap for Marés Altas

Marés Altas is a fictional company, used here only to make the structure concrete. It is a food distribution business in the north of Portugal with around ninety people, supplying restaurants and independent retailers. Its strategy for the next two years is to expand beyond the north, grow its retail channel, and stop depending on two people for every operational decision. After a prioritisation session, the leadership team cut a list of fourteen candidate projects to four initiatives.

Three things are worth noticing. Every initiative has one owner, and the CEO owns only one of them. The order-to-delivery system starts in the second quarter on purpose, because the operations team cannot absorb it while the Lisbon hub is being set up. And progress is described in words against the next milestone, rather than as an estimate nobody can check.

Keeping the roadmap alive

Most roadmaps die somewhere in the second or third month. Not because the work stops, but because nobody opens the document any more, so it stops describing reality. Keeping it alive comes down to a few habits.

• One owner for the roadmap itself. Usually the COO or a chief of staff. Their job is to keep it current, not to do the work.
• Monthly updates in the same format. Each initiative owner updates status, next milestone and any new risk before the monthly review. Two lines are enough.
• Changes are decisions, not drift. Moving a date, adding an initiative or stopping one is decided in the leadership meeting and recorded. It is never quietly edited.
• A visible stop list. What the company decided not to do this year sits next to the roadmap. It is the simplest way to protect focus when a new idea arrives.
• An annual rebuild. Once a year the roadmap is rebuilt from the strategy, not rolled forward from the previous version.

This is the core of our Company Operating System work: building the roadmap with the leadership team, connecting it to the planning and review cadence, and staying long enough for it to run without us.

Where to start

If your strategy is clear but the year keeps filling up with everything else, the first step is a short, honest look at how priorities, owners and reviews work today. Book an Operating Assessment and we will map where the gap between strategy and execution sits in your company.