Blog · October 16, 2026 · 5 min read
How to run a public roadmap without overpromising
A public roadmap shows customers what you’re working on and what’s coming next. Done well, it builds trust and cuts down on “is this coming?” emails. Done badly, it becomes a list of broken promises. Here’s how to keep it useful.
Why have a public roadmap at all?
- Fewer repeated questions: people can check the roadmap instead of emailing you.
- Proof the product is alive: for a small or new product, visible progress is reassuring to anyone deciding whether to rely on you.
- Better feedback: when people see what’s planned, they tell you what’s missing or what matters more.
- Closing the loop: people who asked for something can watch it move from idea to shipped.
Use a few simple statuses, not dates
Most good public roadmaps use three or four columns: Planned, In progress and Completed, sometimes with “Under consideration” before them. That’s enough for people to understand where things stand.
Avoid dates, or at least avoid exact ones. Plans change, estimates slip, and a missed date on a public page feels like a broken promise even when the delay was the right call. If you want to give a sense of timing, use broad horizons like “Now”, “Next” and “Later”.
What to include, and what to leave out
Include things customers will notice: features, integrations, big improvements. Describe each in their words, with the problem it solves rather than how you’ll build it.
Leave out internal work (refactoring, infrastructure), anything you aren’t reasonably sure you’ll do, and anything confidential, like a partnership that isn’t announced yet. A shorter roadmap you keep is better than a long one you don’t.
Connect it to feedback
The most useful public roadmaps grow out of a feedback board: people suggest and vote on ideas, and you move the ones you take on into Planned. That way the roadmap shows not just what you’re building but that you listened, and voters see their idea progress.
It also keeps the roadmap honest. When everything on it started as a real request, it’s easy to explain why it’s there.
Keep it current
An out-of-date roadmap is worse than none: it suggests the product has stalled. Update it whenever something ships or a plan changes, and look over the whole thing once a month.
When you drop something from Planned, say so briefly rather than letting it quietly disappear. People notice, and a one-line explanation keeps their trust.
In short
- Three or four statuses; no exact dates.
- Customer-facing work only, described as problems solved.
- Fed by a feedback board, so it reflects what people asked for.
- Updated whenever things change, and reviewed monthly.
With UserNote, the public roadmap is included on every plan, free one too. Change an idea’s status in your dashboard and the roadmap view of your board updates automatically.