Menu

Digital Transformation

Digital strategy is not a roadmap

A roadmap is a plan. Strategy is the thinking that determines why the plan exists and how it should change.

Why treating a roadmap as the strategy creates false certainty, reduces flexibility, and often pulls teams away from the outcomes they were supposed to achieve.

12 July 20244 min read

In short

Why treating a roadmap as the strategy creates false certainty, reduces flexibility, and often pulls teams away from the outcomes they were supposed to achieve.

Why roadmaps get mistaken for strategy

They show what's being delivered, when it will be delivered, and who's responsible for it. In where and accountability matter, that level of structure feels reassuring, and over time the begins to be treated as the strategy itself.

The issue is that a is an expression of decisions that have already been made, not the thinking that led to those decisions. When it's positioned as the , the focus shifts away from why those decisions exist and towards maintaining the plan that has been created. Progress becomes measured in terms of rather than impact.

There is an organisational reason for the substitution too. A answers the question most people are actually asking, which is what will exist and when. answers a question nobody asked in that meeting, so the roadmap gets circulated and the reasoning behind it stays in the room where it was decided.

A roadmap is an expression of decisions that have already been made. It is not the strategy itself.

How the roadmap starts creating false certainty

Once something appears on a , it carries a level of implied commitment, even if the assumptions behind it haven't been fully tested. Conversations move away from exploring whether a direction is valid and towards managing expectations around timelines and outputs. Over time, the roadmap becomes harder to change, not because it's correct, but because it's been communicated, agreed, and embedded into how the organisation is operating. becomes reactive to the plan rather than the plan being responsive to the strategy.

Dates do most of the damage. A quarter written next to an item is read as a commitment by everyone downstream, and once other teams have planned around it, the item survives on the strength of that rather than on whether it is still the right thing to .

Key takeaway

When a roadmap gets treated as strategy, it becomes harder to challenge assumptions because the plan itself starts to feel like the commitment.

What strategy is actually supposed to do

isn't about defining everything that will be delivered. It's about creating a clear for making decisions. It establishes priorities, defines , and clarifies what matters most, allowing teams to adapt as new information emerges. A roadmap, by contrast, is a snapshot of intent at a particular point in time, based on the understanding that exists in that moment. When those two things are treated as the same, flexibility disappears.

A good test is whether it can settle an argument the authors were not present for. If two teams disagree about priority and the tells them which way to go, it is doing its job. If they have to escalate to find out what was meant, it is a description rather than a .

That is also why the matter as much as the ambitions. What the rules out is what makes it capable of resolving anything, because a document that endorses every reasonable option cannot arbitrate between two of them.

Why this becomes a problem in delivery

As work progresses, new inevitably surface. doesn't always align with expectations, technical become clearer, and priorities shift as the business evolves. In a healthy environment, the strategy provides the context needed to respond to those changes. When the roadmap has been positioned as the strategy, those adjustments become much harder to make. Changes feel like deviations rather than improvements. The work continues, progress is reported, and outputs are delivered, but the impact doesn't always align with what the strategy was supposed to achieve.

When and are treated as distinct but connected elements, the dynamic changes significantly. The strategy provides a clear articulation of the problem, the desired outcomes, and the within which decisions should be made. The roadmap then becomes a flexible representation of how those decisions are being acted upon, rather than a fixed plan that must be followed regardless of new information. When strategy is understood as the framework for decision-making, the organisation becomes focused on achieving the right outcomes, even if that means changing the plan along the way.

The healthier makes changing the plan a sign the is working rather than a failure to report. If new evidence never alters the , either nothing is being learned or the learning is not reaching the people who set the plan.

Written by Andy Scott

Strategic design, UX and digital transformation thinking from real projects.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer