The HEROES Roadmapping Framework

Ask anyone who’s lived with a roadmap and the same complaints come up.

It’s cumbersome to maintain, it’s not truthful, it’s a list of solutions not opportunities, it only shows some of the work, nobody quite agrees with it, it’s always out of date, it’s unrealistic, stakeholders still want lists of features and dates.

And yet it’s often the first thing management will ask for.

And roadmaps seem to be everyone’s job now. Product has the most recognised process behind theirs (PMLC) but many other departments such as Marketing, IT, and Sales are all expected to produce one too, usually without an equivalent process to lean on.

Look online and you’ll find hundreds of templates, most of them Gantt charts in disguise. People copy the look and miss the work. They build a twelve-month delivery plan in isolation, with dates so far out they hope to work some magic to deliver it or hope stakeholders will have forgotten when the time comes around. One page. No discussion. No context.

That’s the gap. Most people think about roadmap. The work is roadmapping. HEROES is the six fundamentals that make the difference.

The six aren’t in strict logical sequence. Requests often comes before Exploration. Sharing happens throughout. Each is its own discipline, and a roadmap needs all six to do its job. What follows is a short tour of each.

High-level Strategy

You can tell when the high-level strategy isn’t doing its job. Teams can’t say why their work matters. The roadmap is a list of features with no thread back to where the company is actually going. “Strategy” turns out to be three words on a wall, or last year’s deck nobody has reopened.

The strategy tells you what to work on, and just as importantly, what not to. And it doesn’t operate at just one level. There’s company strategy at the top, and below it, strategy for the domain the roadmap actually serves: a product, a marketing function, an IT estate. Each is an explicit view of where that area is heading and why. Mission, vision and values are the easy part. The real work is naming the market you’re betting against, the customer and business problems you’ve chosen to solve, and the outcomes that tell you the bet is working.

The roadmap you’re creating expresses one of those strategies. It is a strategic roadmap: a statement of intent and direction, the shape of where this product or function is heading. It is not an execution plan. How and when you deliver a slice of it is a separate artefact, and fusing the two is one of the most common ways roadmaps fail.

Strategy also has to move. New technology, shifting customer behaviour, hard signals from execution: a strategy that can’t absorb those stops being a guide and becomes a relic. Done well, it’s what every roadmap decision gets checked against. Done badly, every team picks its own direction and calls it alignment.

Exploration

Skip exploration and you find out too late. The feature ships, the metric doesn’t move, and someone asks why you built it. By then the money is already spent.

Exploration is the work of understanding the problem before committing to a solution. Research, validation, fact-finding, small tests, and experiments, all aimed at one thing: reducing how much you’re guessing. Some organisations treat it as a phase that runs before execution. Others run it continuously, alongside execution, so each reduces the other’s uncertainty. Either can work.

Exploration reduces uncertainty. It never removes it. What it actually hands you is a confidence level: how sure you are that a problem is real and a bet worth making. That belongs on the roadmap. Near-term work you’ve examined closely can sit at high confidence; far-out items you haven’t reached yet cannot, and the roadmap should say so plainly rather than dress every item in the same false certainty. Visible uncertainty isn’t a weak roadmap. It’s an honest one, and honest is what makes it credible.

Done well, exploration is what lets you say no to the loud request and yes to the one that matters, before either has cost you a quarter. Skipped, the roadmap fills with solutions nobody has tested, each one claiming a confidence it hasn’t earned.

Requests

Every request feels urgent to whoever raised it. The customer who emailed support, the salesperson who lost a deal, the executive with a pet idea. Without a way to handle them, the roadmap becomes a request queue, and whoever shouts loudest wins.

Requests are the ideas, needs, and feedback coming from customers and employees: new features, enhancements, fixes, whole new products. They arrive through support tickets, portals, feedback forms, social media, sales conversations, and hallway asks. The channels aren’t the problem. The problem is what happens next.

A request is a signal, not an instruction. Handled well, each one gets weighed on the same terms: real value to customers, effort to deliver, and fit with the strategy the roadmap serves. Handled badly, the loudest voice sets your direction, and the roadmap stops being a set of decisions and your execution plan becomes a list of demands.

Operations

For most organisations, roadmapping isn’t a continuous process. At best it’s an event: a frantic planning offsite, a burst of activity, then quiet. At worst it’s a single page, produced by one person in isolation, shown once and left to go stale until someone rebuilds it from scratch.

Operations is what changes that: the processes, cadences, meetings and tooling that keep roadmapping running between planning cycles, not just during them. That is continuous roadmapping. It isn’t a separate role or department, and the roadmap it maintains isn’t one person’s document. A roadmap is a shared artefact: everyone whose work appears on it owns a piece of it, regardless of who maintains it. Operations keeps that collective effort coherent and current. The work itself spans prioritisation, capacity planning, budgeting, managing risk, and keeping teams in step.

This is also where the two artefacts have to stay connected. The strategic roadmap and the execution plan are different things, but they are not independent. The roadmap should shape the plan, and what’s learned in exploration and execution should flow back to test the roadmap and the strategy above it. Operations is what keeps that loop closed. The right tooling supports roadmapping, planning, and execution alike, and makes the work easier to manage and to communicate.

Execution

Most teams are already good at execution. They can break work down, run the cadences, ship at pace. Raw delivery capability is rarely what’s missing, and that is exactly the trap.

Speed is only worth having when it’s pointed. Strategy is what points it; exploration is what gives you confidence in the outputs and the approach. Without those, execution just carries you to the wrong place faster.

Execution is where a near-term slice of the strategic roadmap becomes actual, deliverable work: the breakdown into tasks, the split across teams, skillsets, and suppliers, the cadences, the dependencies. It is the home of Agile, Scrum, and whichever delivery method fits what you’re building.

This is the other half of the distinction the strategy section set up. The strategic roadmap is intent, the direction. The execution plan is how and when a slice of that direction gets delivered. They are separate artefacts on purpose, and keeping them separate is what lets the roadmap stay honest about direction while the plan stays honest about delivery. The discipline here is making sure the plan still traces back, that the work in flight genuinely moves you along the trajectory the strategy set.

Sharing

What you share rarely works for every audience. Show the board a team’s execution plan and they drown in detail. Show a team the board’s strategic roadmap and they can’t act on it. So the same view gets explained, and re-explained, meeting after meeting.

Sharing is communicating the right information to the people who need it: customers, investors, internal teams, partners. Done well, it isn’t one view shown to everyone. It is the right view for each audience, drawn from the same underlying roadmap materials, showing the problems, themes and outcomes that audience actually cares about, with as much delivery detail as they need and no more. And whatever the audience, the view should stay honest about confidence: what is committed, what is likely, and what is still a bet.

A one-page roadmap alone leaves the audience to fill in the gaps. The version that works is an artefact. It carries the strategy above (company and function), what’s important this period, the bets being explored, the work in flight, and what recent delivery has actually moved. That context is what makes any of it matter to the audience receiving it.

A roadmap without a story is a series of decisions sitting next to each other. The artefact’s job is to thread them: company strategy down to the smallest feature in flight, a golden thread that pulls every level into the same direction. That’s what makes a roadmap worth reading. Storytelling. Persuading. Bringing the audience along.

And sharing runs both ways. A roadmap presented is half the job; a roadmap that invites a response is the whole one. The feedback that comes back, the concerns, the gaps, the disagreements, is what keeps the roadmap honest and tells you whether it still reflects reality. A roadmap that only broadcasts will slowly drift out of touch with the people meant to be following it.