Roadmap Workshop

Purpose

The Roadmap Workshop aligns product, engineering, and business leadership on what will be built and roughly when. It produces a visual roadmap organized by themes or outcomes rather than a fixed feature list, allowing for agile adaptation.

At a glance

How to run

1. Review vision and strategy (15 min) — Confirm the product vision and strategic objectives.
2. Identify themes (20 min) — Group planned work into 3–5 strategic themes (e.g., "Reduce churn," "Enter new market").
3. Map themes to time horizons (25 min) — Place themes on a Now / Next / Later timeline or quarterly grid. Near-term is more detailed; far-term is directional.
4. Add key milestones (15 min) — Mark external deadlines, dependencies, and launch targets.
5. Identify risks and dependencies (15 min) — What could block delivery of each theme?
6. Review and validate (15 min) — Does the roadmap support the strategic objectives? Is it achievable given capacity?
7. Publish and communicate (15 min) — Agree on the roadmap format and distribution. Set a review cadence (monthly or quarterly).

Materials needed

• Product vision and strategy documents
• Candidate features and epics
• Roadmap template (Now/Next/Later or quarterly grid)
• Large whiteboard or Miro
• Stakeholder calendar with key dates

Pitfalls & common mistakes

• Feature-based roadmap — Organize by outcomes and themes, not by features. Features change; outcomes persist.
• Precise dates for distant items — Only commit to dates for the nearest quarter. Use ranges for later.
• No review cadence — A roadmap that is never updated becomes a lie.
• Excluding engineering — Without capacity input, the roadmap is a wish list.

Inclusion & accessibility

• Share the vision and candidate features in advance.
• Use visual formats (cards, colour coding) with text labels for accessibility.
• Invite diverse perspectives: product, engineering, design, sales, support.

Variations

• Now / Next / Later — Three-bucket format that avoids false precision.
• OKR-aligned roadmap — Map roadmap themes directly to company OKRs.
• Dual-track roadmap — Show discovery and delivery tracks side by side.

When NOT to use this

• If the product is in pure discovery mode with no delivery plans yet.
• If leadership is not willing to share the roadmap externally — the exercise loses its communication purpose.

Source & further reading

• Lombardo, C.T. et al. (2017). *Product Roadmaps Relaunched*. O'Reilly.
• Pichler, R. (2016). *Strategize*. Pichler Consulting.