Roadmap

The roadmap holds work that stays visible beyond today: features, projects, customer commitments, and cross-team efforts. Items are initiatives or ongoing work. Defects belong in bugs and small personal follow-ups in todos.

Plan initiatives

Select Add initiative to create one. Nest child initiatives under a parent when the work is large, then group the roadmap by owner or taxonomy, or filter it by team.

For spec-driven development, the roadmap initiative carries the intent behind the implementation. Keep the initiative brief current before work moves into delivery.

Add taxonomy where it improves planning or reporting.

The Related, Journal, and Changes tabs below the brief show the initiative hierarchy, completed work, and linked code activity. Tab details and breadcrumb behavior are covered in Initiatives.

Order the roadmap

Stack ranking gives initiatives an explicit order. Once work is moving, Roadmap Progress shows whether completed work supports the intended initiatives.

Coming from another tool?

Replacing Aha!, Productboard, or another roadmap tool? Recreate active projects, epics, and product bets as initiatives first. Keeping Linear or Jira? Leave the issues there and use initiatives for the product, customer, or goal context those issues support.