We made our roadmap public. Here’s what 90 days taught us.

For two years our roadmap lived in a private spreadsheet. We told ourselves it was about focus — that publishing it would invite noise, lock us into promises, and hand competitors our playbook. In March we finally published it anyway. Ninety days later, almost every one of those fears turned out to be backwards.

This is the honest version: what changed, what we measured, and the parts that still make us nervous.

The fear was about control. The payoff was about trust.

The first surprise was how quickly the tone of our inbox changed. When users can see what is planned, in progress, and shipped, they stop asking whether you have noticed a problem and start asking how they can help shape the fix. The conversation moves from suspicion to collaboration.

“Is this on your radar?” became our single most common support ticket. A public roadmap answered it before anyone had to ask.

We measured the shift across the first 90 days against the prior quarter:

• 60% fewer “is this planned?” tickets. The roadmap absorbed the question entirely.
• 3 features we had ranked low jumped to the top once votes were visible — we had been wrong about demand.
• 2.4× more comments per request — users explained why they wanted things, not just that they did.

Visibility changed how we prioritized

The biggest internal shift was discipline. When a roadmap is private, it is easy to quietly reshuffle priorities to match whatever shipped most conveniently. When it is public, every move is legible — so you make fewer of them, and the ones you make are deliberate. We started backing each promotion with the same three signals: demand, pain, and willingness to pay. The matrix did the arguing for us.

What we would tell our past selves

Go public sooner, but go public deliberately. Three things made it work:

• Keep columns honest — “Considering” is not a commitment, and labeling it that way protects you.
• Close the loop loudly. Every shipped item became a changelog post that notified the people who voted.
• Reply to declines with a reason. A clear “not now, because…” builds more trust than a silent backlog.

Ninety days in, the roadmap is no longer a document we maintain — it is the main place our users and our team meet. If you have been sitting on the idea, this is your sign. Spin up a public board and try it for a single feature first.