A short guide to roadmapping

Most teams know this matters. Fewer have decided who owns it. Everything we would tell a client about roadmapping in the time it takes to drink a coffee.

Clear scope protects the client at least as much as it protects the agency. Doing this properly once is usually cheaper than doing it approximately three times.

What is actually at stake

A roadmap is a statement of intent, not a promise. The teams that handle this well are rarely the ones with the biggest budgets. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.

The practical version

Sequence by value and dependency, not by loudest request. The cost of getting this wrong is rarely visible on the day it happens. Budget a little time for it every quarter and it never becomes a project of its own.

Common failure modes

Review it quarterly or it becomes fiction. The reasoning matters more than the rule, because the rule has exceptions. If two people in the business would answer this differently, that gap is the actual problem.

In practice

Strategy work is mostly deciding what not to do, and writing it down so it stays decided. Three things worth confirming about roadmapping before you move on:

• Someone can say what the current setup is without going to look
• A roadmap is a statement of intent, not a promise — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If you want a second opinion on how yours is set up, ask.