Product Roadmap Planning

An outcome-based roadmap built from strategy, real capacity and existing commitments, refreshed monthly as learning arrives, with honest versions for the team, leadership and customers.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Product Roadmap Planning, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

204

Starter tasks

🧩 Product Management

Product Roadmap Planning

Building and communicating a product roadmap organised around outcomes and themes, updated as learning arrives rather than frozen for the year.

  1. Inventory of every roadmap in circulation
  2. Roadmap purpose and audience statement
  3. Choosing between Now, Next, Later and a dated timeline
  4. Three to five roadmap themes drawn from strategy
  5. Planning horizons and confidence labels
  6. Roadmap item card with problem, outcome and evidence
  7. Capacity baseline for the next two quarters
  8. Register of commitments already made
  9. Choosing a roadmap tool or staying in a spreadsheet
  10. Single published home for the roadmap
  11. Monthly roadmap refresh
  12. Quarterly roadmap planning cycle
  13. Weekly roadmap change log
  14. Evidence file for each roadmap theme
  15. Quarterly roadmap health check
  16. Outcome review of shipped roadmap items
  17. Annual roadmap theme reset
  18. Intake route for roadmap requests
  19. Monthly dependency check-in with other teams
  20. Roadmap risk register
  21. Writing outcome statements instead of feature names
  22. Studying five published product roadmaps
  23. Roadmap sizing with T-shirt estimates
  24. Practising how to say no to roadmap requests
  25. Presenting the roadmap as a ten-minute story
  26. Roadmapping and product strategy reading queue
  27. Sequencing roadmap bets by risk and learning
  28. Converting a feature-list roadmap to outcome themes
  29. Written list of what the roadmap will not do
  30. Investment balance across new, improve and maintain
  31. Technical debt and platform work on the roadmap
  32. Pruning the Later horizon
  33. Customer-facing roadmap page
  34. Rules for sharing roadmap items in sales deals
  35. Annual planning roadmap submission
  36. Roadmap section for a board or investor meeting
  37. Roadmap preview at a user conference
  38. Roadmap briefing for a strategic customer
  39. Re-planning the roadmap after a strategy change
  40. Founder's first roadmap before product-market fit
  41. Inheriting a roadmap as a new product manager
  42. Combining team roadmaps into one product roadmap
  43. Lean roadmap for a team of two or three engineers
  44. Roadmap continuity through a re-organisation
  45. Roadmap response to a churn or lost-deal pattern
  46. Cross-team dependency map for a major initiative
  47. Scenario roadmaps for budget or headcount uncertainty
  48. Forecasting the Next horizon from delivery history
  49. Roadmap performance metrics
  50. Year-end retrospective on roadmap decisions

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Inventory of every roadmap in circulation

Most product teams have more roadmaps than they think: a planning spreadsheet, a slide in the sales deck, a board appendix and a promise sitting in someone's inbox, each slightly different. Finding every version before building a new one shows where the contradictions are and who relies on which copy, so nothing breaks quietly when the new roadmap replaces them.

First tasks

  • Search shared drives and chat for files and slides named roadmap
  • List each version with its owner, audience and last edit date
  • Ask sales and support which roadmap they show customers
  • Ask the agent to compare the versions and list every contradiction
  • Set a retirement date for each version you will replace

Roadmap purpose and audience statement

A roadmap that tries to serve engineers, executives, salespeople and customers at once usually serves none of them well. Writing down which decisions the roadmap exists to support, and which audience gets which version, settles arguments about detail and dates before they start.

First tasks

  • Write the three decisions the roadmap must help people make
  • List each audience and the level of detail it needs
  • Decide which audiences see dates and which see only sequence
  • Agree the statement with your manager or co-founder

Choosing between Now, Next, Later and a dated timeline

Timeline roadmaps look precise but turn every estimate into a promise, while a Now, Next, Later board shows sequence and confidence without inventing dates months away. Choosing the format deliberately, with your contracts, release trains and audiences in mind, avoids switching formats halfway through the year.

First tasks

  • List every item that carries an external date commitment
  • Mock up five current items in both formats side by side
  • Write the rule for when a date may appear on the roadmap
  • Record the chosen format and the reason on the roadmap page

Make it yours.

Install Product Roadmap Planning, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.