Feature Requests That Ship: Running a Public Feedback Portal Without the Graveyard

Every feedback portal launches with optimism and most end as graveyards: hundreds of ideas, years old, "under review." The graveyard is worse than having no portal — it tells every visitor that asking is pointless.

The failure is not the tool. It is running the portal as a suggestion box instead of a communication channel. These are the operating rules that keep ours alive.

Every request gets a state, and states move

An idea in our portal is always in exactly one of: Open, Planned, In progress, Shipped, or Not planned. The last one is the load-bearing state. Saying "we are not going to build this, and here is why" feels harsh and reads as respect. Silence is what reads as contempt.

The operating rule: nothing sits in Open for more than 90 days with meaningful votes. It either advances to Planned or closes with a reason.

Votes are signal, not governance

Vote counts rank visibility, not priority. Ten votes from your ideal customer profile outweigh two hundred from a segment you are moving away from — and pretending otherwise leads to a roadmap shaped by whoever brigades hardest.

We say this out loud on the portal. Customers handle "votes inform, they do not decide" fine. What they do not handle is discovering it silently after months of voting.

Duplicates are data

The fifth duplicate of "export to CSV" is not clutter to delete — it is a phrasing you have not indexed. Merge duplicates and keep every variant's wording; the AI agent uses those phrasings to route future conversations to the existing thread, which is how requests accumulate weight instead of fragmenting into six two-vote posts.

Automate the follow-through

The magic moment of a portal is the notification: "the thing you asked for in March shipped today." Nobody sustains that manually. When an item moves to Shipped, everyone who voted gets notified and the changelog entry links back to the original thread — automatically.

That chain is the whole flywheel: ask → see movement → get told when it lands → ask again, better. Break any link and participation decays to the graveyard state.

The numbers that matter

Portal health is three numbers reviewed monthly: percentage of requests in a terminal or moving state (target: above 80%), median days from Open to any decision, and voters who return to vote again. Vanity totals — "1,400 ideas submitted!" — measure the size of the graveyard.

Run this way, a portal costs an hour a week and replaces most "what are you building?" churn emails. The mechanics — states, merge-with-phrasings, auto-notify — are built into Chattering; the honesty about Not planned still has to come from you.