Roadmap
A roadmap that cannot quietly go out of date.
Every item is a grouping over issues, and every issue is a channel where the work actually happens. The plan reports the state of the work because it is made of the work.
How it answers to the conversation
Expand an item and you are looking at real channels.
A roadmap in a separate tool is a snapshot of what someone believed on the day they last updated it. This one has nowhere to drift to.
Periods and lanes
Now, next, later — or your own periods. Lanes by team, product area or whatever your org actually uses.
Items group issues
Expand an item to see the issues beneath it and the channels those issues opened.
Status is derived
An item is not "on track" because somebody set a dropdown. It reports what its issues report.
One place to argue
The conversation about a roadmap item is in the channel attached to it, not in a document nobody can find.
What it does
Three things this surface is for.
Plan against real work
The gap between the roadmap and the repository is where most engineering plans die. This closes it structurally.
Honest slippage
When the work slips, the item slips, without a status meeting to discover it.
Small teams get one for free
No separate product to buy, and no third tool to keep in sync with the other two.
Yours or ours
Plan here, or keep it in ProductBoard.
Product management already lives in ProductBoard? Connect it. The roadmap stays there and renders here, with each item still linked down to the channels delivering it.
| Surface | Built in | Connect instead |
|---|---|---|
| Roadmap | Included |
|
Where it appears
Channels that expose this surface.
Roadmap and planning channels. It reads across the workspace rather than belonging to one feature, so a worktree channel does not get one.
- Docs A document an agent may suggest edits to, and a human accepts them. Built in, or connect Notion, Google Docs
- Dashboards Errors, service health and product analytics on one board. Built in, or connect Sentry, SigNoz, Grafana, Mixpanel
- Issues An issue filed from the channel that produced it, assigned to an agent. Built in, or connect Linear, Jira
- Roadmap Periods and lanes, where each item groups the issues that deliver it. Built in, or connect ProductBoard
Division of labour
What agents do here, and what needs a person.
Agents keep it current
Roll up the state of the issues under each item and flag the ones whose reality no longer matches their period.
Agents estimate
From the shape of the work and the history of similar channels, with the reasoning attached so you can disagree with it.
A person commits
What the company promises and when is not a delegable decision, and the product does not pretend otherwise.
A plan made of the work itself.
Crusible is opening to teams in private beta.