How to run a public roadmap your users trust
Trust comes from the answers more than the plans: statuses that mean something, honest nos, and a note when it ships.
A public roadmap is a promise that people can see what you are working on and why. Kept well, it saves your team a lot of repeated explaining, and it gives users a reason to keep telling you what they need. Kept badly, it becomes a page of old "planned" labels that tells users their requests go nowhere.
The difference is mostly small habits: answering in public, using statuses that mean what they say, saying no clearly, and telling people when you ship. None of it needs a big process.
Answer in public
When you answer a request privately, you help one person. When you answer it on the request itself, you help everyone who voted for it and everyone who finds it later. A public reply also cuts down on the same question arriving again through support, because people can see it has been answered.
On Suggst, a product's page is public whether or not its team has claimed it. To answer, claim your page by signing in with a work email at your product's domain. From then on you can reply on posts and set their status, and people can see the team is answering.
Reply like a person. Use plain words and specifics. "Thanks for the feedback, we'll pass it to the team" reads as a brush-off when you are the team.
Use statuses people can rely on
A status is a small public promise. Suggst has four you can set: planned, in progress, shipped and not planned. Each one only builds trust if it means the same thing every time.
- Planned means you intend to build it and it is on your list. Not "we like it" or "maybe one day".
- In progress means someone is working on it now, or it is in beta.
- Shipped means people can use it today.
- Not planned means you have decided not to do it, at least for now.
When you mark a post planned, in progress or shipped, it shows Picked by with your product's name, and the person who posted it gets credit on their profile. That is a nice thing to give people, and one more reason not to hand it out for requests you are not really going to build.
Quick question
A request has many votes, but you know it will not happen this year because a partner you depend on does not support it. What should you do?
Say no well
Saying no is part of running a product, and most users understand that. What upsets people is a no that feels careless: a template, a closed thread, or nothing at all. A good no is short and has four parts.
- The answer. Not planned, said plainly in the first line.
- The reason. Cost, a constraint, a conflict with what most users need, or a direction you have chosen. You do not have to share everything, but share something real.
- What to do instead. A workaround, a setting, another product, or a related request that is planned.
- What would change your mind. If more demand, a partner or a change in the rules would reopen it, say so.
Two ways to say no
A brush-off
Thanks for your valuable feedback! We have shared it with the relevant team and will consider it for future updates.
Close the loop when you ship
Shipping a requested feature is the best moment you will have with the people who asked for it, and it is easy to waste. The release goes out, the post stays open, and the people who voted find out by accident, if at all.
When something ships, mark the post shipped and reply on it with three things: what changed, where to find it, and anything it does not do yet. If what you built is close to the request but not exactly it, say how it differs. Thank the person who posted it. Every post has a public record with a timestamp proof made with OpenTimestamps, so you can see who asked first, and naming them costs you nothing.
Then ask for a reply. "Try it and tell us if it fixes what you described" invites the people who know the problem best to check your work. Their comments are often where the next request starts.
Read the demand, not just the count
A raw vote count tells you how many people clicked. The marks around it tell you who they are and how much it matters. On Suggst, voters can say I use this product, so you can tell your own users from passers-by. They can mark I'd pay for this. And they can answer How often does this happen to you? with daily, weekly, monthly or rarely. A request with fewer votes from daily users who would pay may deserve more of your time than a popular one people hit once a year.
Comments matter too. People can mark comments helpful, which makes the clearest descriptions and the best workarounds easier to find.
If you want more than the public page, the brand plans add a dashboard, a way to message the people who voted on a request, and a way to ask your users a question. Claiming your page, replying and setting statuses stay free, and no plan can hide, delete or re-rank posts.
A weekly routine for the team
A public roadmap does not take much time if you look at it often. Half an hour a week is a reasonable place to start.
Once a week
0/6For the user side of this, why product teams ignore feedback covers what makes a request worth answering.
Claim your product's page for free with a work email at your domain, and start answering requests.
Claim your product's pageWritten by the Suggst team. Example requests about real apps are made up to show how to write them, not reports about those apps.