Roadmap

Use the roadmap to plan work that matters beyond a single todo. Roadmap items are usually Initiatives or Ongoing Work.

Replacing Aha!, Productboard, or another roadmap tool? Move projects, epics, and product bets into initiatives first. Using Linear, Jira, or another issue tracker? Keep issues there and use initiatives to explain the product, customer, or goal context those issues support.

What belongs on the roadmap

Put work on the roadmap when it needs shared context, an owner, a team, a status, and a connection to product or company priorities. Features, projects, epics, customer-impacting work, and cross-team efforts belong here.

Use Bugs when the work is a defect or incident with reproduction, impact, and expected behavior. Keep small personal follow-ups as Todos.

Plan initiative work

Roadmap initiatives can be nested under parent initiatives, grouped by owner or taxonomy, filtered by team or taxonomy, and assigned to people. Use hierarchy when a large initiative has child work that should stay visible under one parent.

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

Taxonomy helps you group work by goals, products, customers, skills, coding tools, and agents. Use taxonomy where it helps planning or reporting; avoid adding it to every small item just because a term exists.

Review priority

Use Priorities when you need context for what matters next. Use Stack Ranking when planned initiatives need an explicit order.

When work starts moving, use Roadmap Progress to see whether completed work is supporting the intended initiatives.