Roadmapping
We recognise that a roadmap can effectively communicate the product’s priorities and intended direction, and that the process to create and regularly review this artefact helps keep stakeholders and the team focused on delivering value.
We expect that things will change as priorities shift, so we recognise that the roadmap reflects what we believe at a moment in time, and that this will require regular review.
Roadmap format #
- Use outcome-based roadmapping approaches that focus on the value delivered rather than feature lists
- As a minimum, create a Now-Next-Later roadmap to balance coverage of current delivery with longer-term goals
- Utilise clearly defined user needs to connect features to intended outcomes and the ultimate vision for the product. This may utilise user story frameworks such as user story mapping or jobs-to-be-done.
- Align roadmap timescales with your setting’s planning cycles.
- Consider creating different roadmap views tailored to different audiences. For instance, a more detailed and technical team view as well as higher level strategic roadmap for senior leadership.
- Consider using a multi-track roadmap which explicitly shows user-focused features, business-requirement milestones, and technical debt/infrastructure work.
Roadmapping activities #
- Establish a regular cadence for roadmap review and iteration
- Involve the delivery team and stakeholder community in roadmapping activities
- Run collaborative roadmap workshops using techniques like story mapping or an impact/effort framework
- Group related initiatives around particular themes to support strategic coherence
- Identify and communicate a plan for addressing any dependencies and risks related to roadmap priorities
- Consider confidence scoring and scenario planning to explore and communicate uncertainty
Communicating the roadmap #
-
Share the results of roadmap reviews with your stakeholders
- Regularly communicate progress against roadmap commitments, with a level of detail appropriate to the audience
- Use roadmap reviews to inform retrospectives and lessons learned
- Consider developing consistent templates/agenda items for regularly engaged audiences and settings (e.g. governance board, Show & Tells etc.)
- Consider whether a public facing roadmap is desirable and appropriate for this product
Last updated: 24 December 2025