Roadmaps

A roadmap is a named, mutable curation of work. It points at existing Initiatives, Milestones, and Cycles and gives them a position — either by manual buckets (“Now / Next / Later”) or by their own dates (Q1 / Q2 / Q3).

Roadmaps don't own the work — they reference it. The same Initiative can sit on multiple roadmaps (engineering, customer-facing, exec) with different bucketing in each.

• Rough — custom string buckets you define and reorder. Default starter set: “Now / Next / Later.” Use this when commitments aren't date-bound.
• Precise — date-derived buckets at a chosen grain (week / month / quarter / half / year). Items land in the bucket their target date or window falls into.
• Hybrid — items with dates use them; undated items fall through to a manual bucket. Best for early-stage roadmaps mixing committed work with fuzzy futures.

On the roadmap page, + Add item opens a picker over Initiatives, Milestones, and Cycles in the same base. Pick any combination — they all live on the same surface.

The reverse also works: every Initiative, Milestone, and Cycle page has an + Add to roadmap… action that lists the existing roadmaps and lets you add the item to any of them.

Shipped Initiatives and done Milestones don't fall off the roadmap — they stay where you put them, dimmed. History is part of the roadmap. A toggle in the header hides terminal-status items if you want a forward-only view.

• Drag a card to reorder within a bucket or move it between buckets.
• Rename a bucket and every item using it updates atomically.
• Delete a bucket and its items move to the previous bucket (or you pick where they go if it's the last one).
• Edit the underlying Initiative / Milestone / Cycle from the roadmap (opens a side panel) — changes propagate to every roadmap that references it.
• Per-roadmap notes — a short annotation on each item that only shows in that roadmap. Doesn't modify the underlying item.

You can have as many roadmaps as you want. Common patterns:

• Internal — full detail, all in-flight work.
• Customer-facing — the subset you're comfortable sharing publicly.
• Per-team — engineering, marketing, ops each curate their own.
• Quarterly — “Q3 plan,” “Q4 plan,” archived once the quarter is done.