Strategic Roadmap

What this tool does

CM8-300 builds a strategic roadmap: themes, the initiatives inside them, the horizon each one sits in, who owns it, what it costs, what it would change, how confident you honestly are, and what has to land first. It draws the roadmap as a timeline, separates what you have actually committed from what you have merely intended, and runs a credibility check that pairs committed work with weak assumptions.

Everything runs inside this single file. There is no account, no upload and no network request of any kind, so your themes, investment figures and unfinished thinking never leave the computer you are using.

What a roadmap is not

A roadmap is a statement of intent organised by horizon. It is not a Gantt chart with dates you will be held to, and presenting it as one is the most reliable way to destroy its credibility. The mechanism is always the same: somebody asks for the roadmap, receives a chart with bars and dates on it, reasonably concludes that those dates are commitments, plans around them, and discovers eighteen months later that the bar labelled "own-brand range" was an ambition nobody had ever costed. The roadmap is then never believed again.

The defence is not vaguer dates — vague roadmaps are useless in a different way. It is saying clearly which parts are commitments and which are not, on the same page, every time. That is what the four horizons exist to do, and it is why commitment weight is a column rather than a footnote. You can hand this roadmap to a board, a lender or a new director and the page itself tells them how much of it is a promise.

Now, Next, Later, Exploring

Each initiative sits in exactly one horizon, and each commits you to a different amount:

• Now — in flight. Work that is actually happening: resourced, started, with someone spending time on it this week. The tool will not accept a Now initiative marked "not started", because that combination is the commonest way a roadmap lies to itself. Start it, or move it to Next.
• Next — committed, not started. You have decided to do it, you know roughly what it costs, and it starts when capacity frees up. If you would be embarrassed to drop it without explaining why, it belongs here.
• Later — intended, not committed. The direction you expect to go. The dates are indicative and everyone should read them as "about then". Nothing in Later should be depended on by anything in Now.
• Exploring — option only. An idea you are keeping open. You have not bought it, and the tool will not let an Exploring initiative carry investment above zero — an option with money committed to it is not an option, it is a decision that has not been announced.

Only Now and Next count as committed. The committed-investment tile adds up exactly those two horizons and shows the Later and Exploring figure alongside, so the difference between what you have signed up to and what you are contemplating is visible in one line rather than buried in a total.

Themes

A theme is the strategic thread an initiative belongs to — capability, cost position, market reach, people. Themes are what make a roadmap a strategy rather than a list of projects that happened to be approved. Without them you have a portfolio; with them you have an argument about where the business is going, and each initiative has to justify itself against that argument rather than on its own merits.

The theme chart is deliberately the most uncomfortable picture in the tool. A theme with nothing in the Now horizon is a theme you are not actually pursuing. It may have four initiatives, a large planned investment and an eloquent description, and none of that is work. Most organisations have one — usually the theme everybody agrees is important and nobody has ever been asked to start. The opposite finding matters too: a theme that is entirely Now has nothing behind it, so when this year's work lands the theme is finished. Aim for each live theme to have something in flight and something behind it.

Benefits stated as outcomes

Write the expected benefit as what changes in the world, not as what you will do. "Build a regional hub" is activity. "Next-day delivery reaches most of the customer base, which removes the commonest reason quoted for losing a tender" is an outcome — and it can be wrong, which is what makes it useful.

Then attach a benefit measure: the single number that would move if the outcome happened. It does not have to be precise or measured today; it has to exist and be nameable. An initiative whose benefit measure reads "— none named —" has not been thought through, however confident everyone is, because nobody will ever be able to say whether it worked. Naming the measure at proposal time also protects you later: benefits have a habit of being redefined after delivery to match whatever happened, which is how organisations accumulate projects that all succeeded while nothing improved.

Confidence and the credibility check

Confidence is a declaration, not a calculation, and the tool records it exactly as you set it. High means resourced and understood — you know who is doing it, roughly what it costs and what could go wrong. Medium means the shape is right but substantial questions are open. Low means the estimate is a placeholder, the approach is unproven, or it rests on something nobody has checked.

Low confidence is not a problem on its own. Low confidence on an option is exactly right — that is what an option is. The finding is the pairing: an initiative in a committed horizon with low confidence declared against it. That is something you have told people you will do, resting on assumptions nobody has tested, and it is the most useful thing this tool surfaces. The tile counts them and names the largest by investment; the credibility check table lists every one, alongside anything overdue and anything paused or dropped, so the awkward half of the roadmap sits on one page.

The right response is usually not to change the rating. It is either to do the work that would raise it — scope it, cost it, test the assumption — or to move the initiative back to Later until somebody has. Editing the rating to make the page look better is the one thing that empties the instrument of meaning.

Dependencies

The depends on column names the initiatives that must land first. Spell them exactly as they appear elsewhere so the chain can be followed by eye.

Two patterns are worth hunting for at every review. The first is a Now or Next initiative that depends on something sitting in Later — that is not a dependency, it is a blocker, because nothing in Later is committed to happening at all. The second is a chain three or four deep inside one horizon, where every link has to go right for the last one to be possible. In both cases the honest move is to redraw the plan rather than to hope.

The quarterly review

Review the roadmap quarterly, and treat moving things between horizons as the main business of the meeting rather than an afterthought. A roadmap where nothing has moved horizon in a year is not stable; it is not being used.

Work through it in order. What is in Now, and is it genuinely in flight? What should move from Next to Now, given what has finished? What should move from Later to Next — and has it earned that by having its confidence raised, or is it merely closer? What in Exploring has been an option long enough that keeping it open is itself a decision? And what should move backwards, or come off entirely? Moving something backwards is the hardest and most valuable action available. A Next initiative untouched for three reviews is not committed work, whatever the page says, and leaving it there quietly inflates the committed-investment figure other people are planning around.

Recording what was dropped

When an initiative is paused or dropped, the tool requires a reason before it will save. This is not bureaucracy — it is the only defence against the most wasteful pattern in strategic planning, which is re-proposing next year exactly what was investigated and rejected this year, by people who were not in the room the first time.

Write the reason so it is useful to a stranger: what was found, and what would have to change for the initiative to come back. "Not a priority" teaches nothing. "The site search found nothing within a workable recruitment catchment; revisit only if the market entry lands and changes where a second site would sit" both closes the question and reopens it under stated conditions. Keep dropped initiatives on the roadmap rather than deleting them — the credibility check lists them, and that list is the cheapest institutional memory you will ever maintain.

Where this sits alongside other tools

Two other CapsuleM8 tools work on strategy and are often confused with a roadmap. The OKR Planner sets objectives and measurable key results for a single short cycle, and is about whether you hit what you aimed at in that quarter rather than what happens in three years. The Hoshin Kanri X-Matrix deploys a small number of breakthrough objectives downward through strategies, tactics and measures so every level can see how its work connects to the top, which is a different job from sequencing initiatives across horizons.

Use this tool for the multi-year picture: what you are doing now, what you have committed to next, where you intend to go, and what you are only keeping open.

The spreadsheet workflow

Roadmaps usually begin life in a spreadsheet, and the toolbar keeps that route open.

• Spreadsheet template saves a CSV whose headings are exactly this tool's column names, with a guidance row showing what each column expects — the date format, and the accepted values for the horizon, confidence and status lists.
• Draft the initiatives there with the theme, initiative, horizon, owner and planned finish columns filled in, then delete the guidance row before saving. Keep the file as CSV.
• Import spreadsheet reads it back. Columns are matched by heading, so their order does not matter and extra columns are ignored. Rows missing a required column, or failing a validation check — a dropped initiative with no reason, a Now initiative marked not started, an Exploring initiative carrying investment — are skipped and reported by row number.

Nothing is uploaded, and importing adds to what is already here rather than replacing it. Spell theme names identically every time; themes are grouped by name, so "Cost position" and "Cost Position" become two themes with half a strategy each.

The formulas

A blank investment is a blank, never a zero: it is excluded from the count of priced initiatives, shown as "—" in the table, and contributes nothing to a total. The investment chart prints how many initiatives in each theme are unpriced, because a theme total built from two figures out of five is not a theme total.

FAQ

How many initiatives should a roadmap carry? Enough to show the shape and few enough to hold in your head — usually ten to twenty across four or five themes. If Now holds more than a handful, they are not all in flight.

What dates should Later initiatives have? Indicative ones, and say so every time you present the roadmap. The tool needs a planned finish so the timeline can place the initiative roughly right; that is all the date is for until it reaches Next.

Should the investment figure be the approved budget? No. It is the planning estimate for the whole initiative. Approved budgets belong in the finance system and will differ, often by a great deal, in the Later horizon. Treat the committed-investment figure as an order of magnitude for a conversation, not as a number to plan cash against.

Can one initiative sit in two themes? Not in one row. Pick the theme it primarily serves and mention the other in the notes — splitting it double-counts the investment and makes both themes look thicker than they are.

What about an initiative with no end date? It is not an initiative. It is an activity or a standing capability, and it belongs on an operating plan. Roadmap initiatives start, finish and change something.

Saving your work

Initiatives, settings and the report header are written to this browser's local storage as you type, and the toolbar shows the time of the last save. That storage belongs to one browser on one computer: another browser, a private window or a clean-up tool that clears site data will not have it.

Treat Export .json as the real save — one file containing everything, which Import .json restores anywhere. Export CSV gives you the initiatives for spreadsheet work. Reset asks twice, then erases everything this tool has stored; there is no undo. A roadmap states your intentions, your investment plans and your unfinished thinking in one page — treat exports as commercially confidential.

Accuracy & disclaimer

The arithmetic is simple and the tool does it faithfully. What it cannot do is tell you whether the themes are the right ones, whether an initiative will deliver the benefit claimed for it, whether an investment figure is realistic, or whether the confidence you declared is the confidence you actually feel. All of that is judgement, and the tool records it rather than checking it.

Be clear about what a roadmap is when you circulate one. It is a plan of intent at a point in time. Only the Now and Next horizons carry commitment; the dates in the Later horizon are direction, and treating them as promises is how a roadmap becomes a liability — to the people planning around it, and to whoever presented it. Investment figures are planning estimates, not budgets, forecasts or approvals.

This is a planning and communication aid. It is not financial, investment or strategic advice, and a printed roadmap is not a substitute for the quarterly argument it exists to structure.