Publishing a Public Roadmap Without Over-Promising
Roadmaps · 10 min read ·
How to show the path ahead honestly: what a public roadmap should contain, how to word intentions, handle changes and keep trust when plans move.
A product with a visible path invites people to come along. They can see where it is going, judge whether it suits them and tell you what matters. A product with no stated direction asks them to trust that something good is happening out of sight. Public roadmaps have grown popular for good reason.
They also carry a risk that is easy to underestimate. Anything you publish can be read as a promise, and users who plan their own work around your plans will be disappointed if they change. This guide explains how to publish a roadmap that is useful, honest and sturdy: what to include, how to word it, how to handle the inevitable changes and how to keep the trust that it is meant to build.
What a roadmap is
A technology roadmap is a flexible planning approach that matches short-term and long-term goals with specific technology solutions to help meet those goals. In everyday product work, the word means something simpler: a high-level view of what the team plans to build or improve, and roughly when.
A roadmap is not a detailed plan, a schedule or a contract. It is a communication of direction. The more people treat it as a firm schedule, the more it will disappoint.
Why publish one
There are good reasons.
- Trust. Users see that the product is alive and that someone has thoughts about its future.
- Feedback. People tell you what they need, which helps you prioritise.
- Fewer questions. A visible plan answers "will you add X?" before it is asked.
- Alignment. Writing it down for others forces clarity within the team.
- Credibility with partners. People who build on or alongside your product can plan.
And reasons to be careful.
- Pressure. Public items can become obligations.
- Competitors see your plans.
- Disappointment when plans change.
- Distraction. Debate about items may shape the work more than evidence does.
If you weigh these and decide to publish, do it with care.
Choose what to show
Not everything belongs on a public roadmap.
Include:
- Themes and goals: "make setup faster", "improve reliability", "support more file types".
- Features you are actively working on.
- Items where public feedback would help.
- Commitments to fix known problems.
Leave out:
- Speculative ideas you may never build.
- Anything under a confidentiality agreement.
- Fine-grained task lists.
- Security work, where detail would help attackers.
- Items that depend on uncertain outside events.
- Internal reorganisations.
A shorter roadmap that is accurate beats a long one that is half fantasy.
Choose the format
A few simple formats work well.
Now, next, later. Three columns that describe horizon, not dates. Now: in progress. Next: planned and likely. Later: under consideration. It is easy to read and avoids false precision. This format echoes the visual boards of kanban, a method of managing work that shows items moving across columns.
By theme. A few headings, such as speed, integrations and reporting, with a short line under each about what you plan to improve.
By stage. If your product is at a particular stage of growth, you might frame the roadmap around the milestones you want to reach, such as reliability for first paying customers.
A changelog-linked roadmap, where completed items link to their entries in the changelog, so readers can see that plans turn into delivery.
Avoid the long chart with dates against every line. It looks authoritative and ages badly.
Wording matters
Roadmap language shapes expectations.
- Use the language of intent. "We plan to", "we are exploring", "we are working on".
- Avoid the language of promise. "We will deliver", "by the end of the quarter", "guaranteed".
- State confidence, where useful: now means active, next means likely and later means possible.
- Say why. A short rationale makes an item more understandable, and shows users what is driving priorities.
- Include a visible disclaimer: "This roadmap shows our current intentions. It will change as we learn."
- Keep items small in word count. One line each, with a link for detail.
If you can only commit to a direction, commit to that. A roadmap that says "reliability is our main focus this quarter" is honest. A roadmap that lists twenty named features by date is a hostage to fortune.
Dates: use sparingly
Dates are the biggest source of broken trust. If you must use them:
- Use a broad period, such as a month or quarter, rather than a day.
- Only for items you are close to finishing.
- Label them as targets.
- Update them promptly if they move.
If you cannot update promptly, remove dates altogether. A stale date is worse than none.
Taking feedback
A public roadmap invites suggestions. Handle them well.
- Provide a clear route, such as a form or a thread, for ideas and votes.
- Thank people, and read what they write.
- Explain how you decide. Say that votes are one signal among several, with strategy, effort and fit also considered.
- Do not promise. "Thank you; we have noted it" is honest.
- Close the loop. When something ships that someone asked for, tell them.
Beware overweighting the loudest voices. Weigh feedback against what you know of your users overall, and against your milestone.
Handling change
Plans will change. The question is how you handle it.
- Update the roadmap promptly. A roadmap that does not reflect reality is a trap.
- Say what changed and why, briefly: "We moved this to later because we found a reliability problem that needs fixing first."
- Do not delete silently. Mark items as removed or postponed, at least for a time, so that those who followed them see the outcome.
- Tell people who asked for it, if you know them.
- Keep a changelog of the roadmap, so that history is visible.
Users forgive changes that are explained. They resent changes they discover by absence.
Linking with the changelog
A roadmap points forward and a changelog looks back. Together they give a coherent story: here is what we said, here is what we did. Link them. When an item is delivered, move it from the roadmap and add an entry to the changelog, with a link. Over time, the record shows how reliably plans become reality, which is the best evidence of credibility.
What readers and machines do with it
Search engines and AI assistants may quote a roadmap as if it were a statement of fact about the product. If it says "we plan to add X", a summary may state that the product supports X. To reduce the risk:
- Label sections clearly, such as "Planned" and "Available".
- Keep the roadmap on a separate page from the features page.
- Date the page, and show when it was last updated.
- Avoid wording that reads as a present capability.
Accurate labelling helps humans and machines alike.
Common mistakes
- Treating the roadmap as marketing. Padding with items you do not plan to build.
- Over-specifying dates.
- Letting it go stale. The commonest failing of all.
- Using it to deflect. Pointing at the roadmap instead of answering a question.
- Hiding bad news. Not mentioning that something has been delayed.
- Building to the roadmap, at the expense of what users now need.
- Being everything to everyone. A roadmap with forty items shows no focus.
A worked example
A small team publishes a roadmap for their budgeting app in three columns. Now: faster sync, a clearer first-use screen. Next: support for two more currencies, a shared-account view. Later: an export option and a tool for annual summaries, under consideration. Each item has a one-line rationale, such as "Many of you told us setup takes too long."
At the top: "This roadmap shows our current intentions. It will change as we learn. Last updated 14 March." No dates are attached. A link leads to the changelog, and a form invites suggestions.
Six weeks later, the team finds a reliability fault in syncing that demands attention. They move the shared-account view to later and add a note: "Postponed while we fix sync reliability, which affects more people." Two users who had asked for the shared view receive a short message. When the sync fix ships, they add a changelog entry and move the item off the roadmap. A reader who follows the page for a few months can see that the team says what it plans, tells people when it changes and delivers a good share of what it says. The page has become evidence of the team's reliability.
Questions makers ask
Do I need a roadmap at all? Not necessarily. But some indication of direction helps users, and a short, honest page costs little.
Should customers see everything? No. Share what is useful and safe, and keep strategy and speculation private.
What if a user relies on a planned item? Be direct: do not rely on future features. Say what exists today.
How do I deal with demands for dates? Explain that you share direction, not schedules, and say why.
Summary
A public roadmap shows direction and invites feedback, but it can be mistaken for a promise. Show themes and active work, keep speculation and sensitive items out, use now, next and later in place of dates and word items as intentions. Take feedback gracefully, update promptly when plans change and explain what moved and why. Link the roadmap to the changelog so that delivery is visible, and label planned items clearly so that no reader, human or machine, mistakes them for features that exist.
Questions and answers
- What is a public roadmap?
- A published outline of what a product team intends to work on, grouped by timeframe or theme, shared so users can see the direction.
- Should I put dates on a roadmap?
- Only if you are confident. Broad horizons such as now, next and later are safer than specific dates.
- Is a roadmap a promise?
- It should be labelled as intentions that can change. Treat anything you cannot control as a possibility, not a commitment.
- What if a planned item is dropped?
- Say so, explain briefly and move on. Quiet removal damages trust more than an honest note.
- How often should a roadmap be updated?
- Whenever something material changes, and reviewed on a schedule such as monthly.