The single source of truth for what we're building, in what order, and why. A CPO-level roadmap is themes-first, dates-soft, outcome-bound — not a list of features with hard deadlines.
— the eight elements without which it's not a roadmap, just a wishlist
| Element | What it is | Granularity |
|---|---|---|
| Time horizon | Quarterly grid (4 quarters minimum) + an annual 3-year strip above | Quarter, not week |
| Strategic themes | 3 to 5 max — the “why” of every initiative on the roadmap | Stable for 12–18 months |
| Initiatives per theme | Named bets, ~1–2 per quarter per theme | 1–3 months per initiative |
| Linked OKR / NSM | Every initiative declares the metric it's expected to move | 1 OKR per initiative, ideally |
| Status | Planned · In flight · Done · Cut · Re-scoped | Updated weekly |
| Confidence level | Committed · Explored · Exploratory — protects against false promises | Per initiative |
| Cross-team dependencies | Visual links to other teams' work that must land first | Named owner per dep |
| Capacity allocation | % of squads per theme (Growth 40 / Retention 25 / Mone 20 / Foundation 15) | Quarter-level |
The one-line test
If a stakeholder reads the roadmap for 30 seconds, they should walk away with: “In Q3, this team is betting on retention via onboarding revamp, expecting +8 pp on D7 retention.” If they can't, the roadmap is too dense or too vague.
— what the artefact looks like, themes-first, on a quarterly grid
Shoette · Product roadmap — FY 2026
North Star: Weekly active buyers with ≥ 1 repeat purchase in last 90 days
— What you read above is an HTML/CSS mock built for this page. Real tools (next section) render the same logic interactively.
— each tool has a sweet spot. Pick the one that matches team size, maturity and budget.
| Tool | Format | Best for | Watch out |
|---|---|---|---|
| ProductBoard | Themed roadmap + customer-feedback intake | Mid–large product orgs (10+ PMs) | Pricey · steep learning curve |
| Aha! | Strategy + roadmap + idea management | Enterprise / regulated industries | Heavy · opinionated |
| Roadmunk | Visual swimlanes / timeline | Mid-size teams who want a clean visual | Limited integrations |
| ProductPlan | Timeline + list views | Small–mid teams · stakeholder reviews | Light on prioritization features |
| Jira (Plans) | Cross-project Gantt-like portfolio | Teams already deep on Jira / Atlassian | Premium tier required · UI complexity |
| Linear | Cycle + roadmap views, modern UI | Engineering-led teams | Less product-marketing-friendly than ProductBoard |
| Notion | Database with timeline / board / table views | Small teams · ad-hoc setup · low budget | Manual maintenance · weak dependency view |
| Excel / Google Sheets | Grid + Gantt | Anyone, ad hoc · early-stage | Painful to maintain past 20 initiatives |
| PowerPoint / Keynote | Static visual | Board / exec presentations only | Out of date the moment you save it · never the “source of truth” |
| Miro / FigJam | Sticky-notes board | Workshops, brainstorming, early framing | Not for the ongoing source of truth |
Anti-pattern
Two roadmaps in two tools. One roadmap, one source of truth. If exec presentations and the team's working roadmap diverge, drift is guaranteed within 4 weeks.
— named differently across versions, used by most teams already on Jira
If the team is already on Jira, the feature for product roadmaps is called Plans in Jira Cloud (formerly “Advanced Roadmaps,” before that “Portfolio for Jira”). It is part of Jira Cloud Premium.
Plans provides:
For teams on the free / standard tier, the basic Roadmap view (within a single project) shows epics on a quarterly timeline. Adequate for small teams (1–2 squads); insufficient for cross-team portfolio planning.
See Atlassian's Plans documentation for screenshots and the live demo.
— direct links to vendors' marketing pages — they showcase real demos
ProductBoard
Themed roadmap · customer feedback intake
The reference for product-marketing teams. Themes, initiatives, OKR linkage, and a strong “Insights” module that connects user feedback to roadmap items.
See ProductBoard roadmap →Jira Plans
Cross-project portfolio · Atlassian Premium
Best fit when the engineering team already lives in Jira. Capacity planning + dependency view make it strong for delivery-heavy roadmaps.
See Jira Plans →Aha! Roadmaps
Strategy + roadmap · enterprise
Heavy and opinionated. Strong for enterprise / regulated industries that need an end-to-end strategy → release link.
See Aha! Roadmaps →Linear
Modern UI · engineering-led
Beautiful, fast, opinionated. Roadmap view focuses on cycles and milestones. Less depth on customer feedback intake than ProductBoard.
See Linear product views →Roadmunk
Visual swimlanes · mid-size
Clean swimlane visualization, easy to share with stakeholders. Lighter on intake / OKR linkage than ProductBoard or Aha!.
See Roadmunk →— the sensible default at Shoette scale
One discipline beats every tool: the same person (the CPO or a designated PM Ops) owns the canonical roadmap. Anyone reading any view downstream knows where the truth lives.