A roadmap is a set of bets. Without a regular review, it either goes stale while the business changes or gets rewritten every time someone has a new idea. A short monthly review keeps it honest: what shipped, what it changed, what to stop, and what comes next.
Step 1 — Prepare one page
Goal: Bring evidence, not opinions, into the room.
- List what shipped since the last review and the outcome each was meant to change.
- Show the measure for each outcome, even if the answer is “not yet known”.
- List new requests and problems that arrived, grouped by theme.
- Note anything blocked and why.
You finish with: A one-page pre-read shared before the meeting.
Step 2 — Review results
Goal: Learn from what already shipped.
- For each shipped item, decide: working, not working, or too early to tell.
- Agree follow-up work only where the evidence supports it.
- Record what the team learned about customers.
- Keep the discussion on outcomes, not on who was right.
You finish with: A short record of results and lessons.
Step 3 — Decide what changes
Goal: Adjust the roadmap on purpose.
- Stop or shelve items that no longer serve a current goal.
- Add new items only by naming what they replace.
- Confirm the next cycle’s top priorities and their owners.
- Check capacity so the plan is realistic.
You finish with: An updated roadmap with explicit stops and adds.
Step 4 — Communicate
Goal: Make sure everyone hears the same story.
- Share the decisions and the reasons in writing the same day.
- Tell sales and support what changed and what to say to customers.
- Update the roadmap tool so it matches the decisions.
- Set the date of the next review.
You finish with: A written update and a roadmap that matches it.
Common pitfalls
- Reviewing activity instead of outcomes.
- Adding work without naming what it replaces.
- Decisions that live only in the meeting.
- Skipping the review when things are busy.