Template · roadmap
Product roadmap
A shared roadmap is the cheapest trust you can buy. It says what you are working on, what is next, and what you have heard and not yet done, and it saves you writing the same reply to the same question a hundred times.
On fenbs the roadmap is not a separate document you forget to update. It is the board you already work: To Do is Later, Next Up is Next, In Progress is Now, and Completed is the changelog. Everyone you add sees it live, because it is the actual work.
Add customers and stakeholders with the Client role: they see the board and comment, and cannot change anything. Give the people who report bugs the Reporter role, and what they find lands on the board under their name.
What is on it
To Do
4- FeatureP6
Rename me: a later idea
Roadmap
- FeatureP7
Rename me: another later idea
Roadmap
- EnhancementP1
Add your customers and stakeholders with the Client role (People → Add someone)
Setup
- EnhancementP2
Connect your AI assistant with a role that can move tasks, so it moves them when code merges
Setup
Next Up
3- FeatureP3
Rename me: next feature
Roadmap
- EnhancementP4
Rename me: next improvement
Roadmap
- BugP2
Rename me: a bug users keep reporting
Roadmap
In Progress
2- FeatureP2
Rename me: the big feature we are shipping now
Roadmap
- EnhancementP3
Rename me: the improvement in progress
Roadmap
Completed
1- FeatureP5
Rename me: something we shipped last week
Roadmap
Feature · Enhancement · Bug — color is the kind of task, never its urgency.
Then
- Copy the board onto a team board, then rename the tasks to your own features. Keep the lanes as they are: that is what makes it a roadmap.
- People → Add someone → choose Client. Everyone you add sees the roadmap as soon as they sign in with that email.
- Connect your AI assistant with a role that can move tasks. Ask it to move them as pull requests merge, and the roadmap keeps itself.
Other templates: Bug tracker · Client project · AI assistant work log · Personal to-do