Roadmaps often reflect the strongest storyteller or the latest large customer. An evidence-based roadmap does not eliminate judgement, but makes visible what we know, what we assume and what learning each choice buys.
Define the problem before the solution
Describe who struggles, with which task and with what consequence. The proposed feature should not serve as proof that it is needed.
Gather different streams of evidence
Combine behaviour, interviews, support, sales and market constraints. Several independent signals are stronger than a large volume from one biased channel.
Assess uncertainty
Distinguish established demand, an unclear solution and an unknown implementation. A score must not hide the fact that two ideas carry different kinds of risk.
Compare opportunity cost
Record effort, dependencies, maintenance and what will be delayed if the idea is selected. Prioritisation means choosing between alternatives, not approving each idea in isolation.
Set a learning milestone
For uncertain opportunities, define a smaller test before committing to a full build. The roadmap should allow work to stop when the evidence does not become stronger.
This framework is an original editorial methodology developed by DigitalNow.