Roadmap
Overview
Section titled “Overview”Roadmap takes the top of your backlog hierarchy, big rocks and epics, and lays them out on a timeline instead of a ranked list. It answers a different question than the backlog: not what should we do next, but when will this actually land.
Because roadmap items trace back to the same backlog and PRDs everyone else works from, there is no separate roadmap document to keep in sync. Reprioritizing the backlog or moving a sprint updates the timeline automatically.
In MVP, roadmap is an internal planning view. Publishing a roadmap externally to customers is outside the MVP scope and shows a coming-soon message if you try to reach it.
What you can do here
Section titled “What you can do here”- View big rocks and epics laid out across a timeline.
- Filter by project to focus on one initiative at a time.
- Spot which epics are on track versus at risk based on sprint progress.
- Click through from a roadmap bar to its underlying epic or big rock.
- Share the internal view with stakeholders inside the workspace.
When to use
Section titled “When to use”- Communicating a multi-sprint plan to internal stakeholders.
- Deciding sequencing between big rocks before committing sprint capacity.
- Checking whether a target date is still realistic given current progress.
Prerequisites
Section titled “Prerequisites”- A signed-in member account with product access.
- At least one finalized PRD with a generated backlog.
Where to find it
Section titled “Where to find it”- Sidebar: Roadmap
- Direct route:
/roadmap
Step-by-step
Section titled “Step-by-step”- Open Roadmap (
/roadmap). - Filter by project if you want to focus on one initiative.
- Scan the timeline for big rocks and epics and their current status.
- Click any bar to open its underlying epic or big rock for detail.
- Compare target dates against actual sprint progress to judge realism.
- Share the view internally rather than exporting it for external stakeholders.
What success looks like
Section titled “What success looks like”- Stakeholders can see sequencing and rough timing without asking for a separate deck.
- You can tell at a glance which epics are on track and which need attention.
- The roadmap always matches the current backlog; nothing is manually re-typed.
Tips & best practices
Section titled “Tips & best practices”- Use Roadmap for internal planning conversations, not as a public commitment document in MVP.
- Revisit target dates after every sprint planning session, since scope and capacity shift.
- Pair Roadmap with Team Analytics when a stakeholder asks whether a date is realistic.
Common mistakes
Section titled “Common mistakes”- Treating Roadmap as a public-facing commitment when it is an internal MVP planning view.
- Ignoring the timeline entirely and planning sprints without checking sequencing across big rocks.
- Manually recreating the roadmap in a slide deck instead of sharing the live view.