Features / Product feedback
Product roadmap
Show people where it is going
A public roadmap fed by the same requests your customers voted on, so the board and the plan can never disagree with each other.
Under review
Bulk export to CSV
57 votes
Planned
In progress
Shipped
What it does
- Columns you control, on your own domain
- Items carry their votes and their original request
- Reporters who raised it through a conversation are told when it ships
- Public view needs no login to read
Without it
Customers ask what you are building because they cannot see it
“Is that on the roadmap?”
You say you will check. You open an issue tracker written for engineers, read three tickets that mean nothing to a customer, and come back an hour later with a maybe.
The public roadmap and the real plan drifted apart
The internal board is current because the team lives in it. The public one still says Q2 for something you shipped in March and something else you quietly dropped, and now nobody trusts either.
Saying no feels worse than saying nothing
So you say nothing. The customer waits six months for a feature that was never going to be built, and then leaves for a competitor who told them the truth in week one.
How it works
The roadmap item is the request people voted on
Not a copy of it, the same record. There is nothing to sync and nothing to keep in step, so the board and the plan cannot disagree with each other.
Five statuses, and one of them is a no
Under review, Planned, In progress, Launched, and Not planned. A Not planned item carries a reason and, if you have one, a workaround, stored on the item rather than in a reply somebody has to remember to send.
What that includes
- Under review
- Planned
- In progress
- Launched
- Not planned
The no is honest without being a public graveyard
The public roadmap serves the four columns that are still moving. The Not planned reason lives with the request itself, so the people who asked can see where it landed without you publishing a wall of rejections.
Public votes have to be a real person
A vote from an unverified identity is refused rather than counted, a second vote from the same identity comes back as a duplicate, and both the organization and the individual are rate limited.
It reads without a login
The public roadmap is a read-only view on your portal address, so you can link it from a support reply and the customer just sees it.
What it means for you
You stop answering the same question by hand
“Is this planned?” becomes a link. The answer is the same one every time, and it is current because it is the record your team is actually working from.
A no you can send without wincing
Not planned, here is why, here is what people do instead. Sent once, in writing, attached to the request forever, rather than avoided until they churn.
The order is defensible
When someone asks why their request is below another one, you have a count with names behind it rather than an opinion.
The honest limit: Tore does not tell voters when their item moves. The automatic “you asked for this, it is live” message runs off shipped fixes and the people who reported them, not off roadmap votes, so telling voters is still a message you choose to send.
Also in Product feedback