Teams hesitate to publish a roadmap for one reason more than any other: they're afraid it becomes a list of promises they'll be held to. Then plans change, which they always do, and every change looks like a broken promise.
That fear is real, but it comes from treating the roadmap as a contract. Treat it as a conversation instead and most of the risk goes away.
Show direction, not dates
A roadmap that says "CSV export, March 14" is a contract. A roadmap that says "Planned: CSV export" with a short note on why is a direction. Customers mostly want to know whether you heard them and whether their thing is coming at all. A date adds pressure and very little reassurance.
If you do share timing, keep it coarse. "This quarter" survives a slipped week. "March 14" doesn't.
Fewer items, honestly labelled
A roadmap with sixty planned items isn't a plan. It's a wish list, and customers can tell. Keep "Planned" for things you genuinely intend to do, and keep "In progress" short. A small, true roadmap earns more trust than a big, hopeful one.
Let people talk back
The point of making it public is that customers can react. They vote, they comment, they tell you a planned item doesn't quite solve their problem. Those reactions are the cheapest product research you'll ever get, and they arrive before you've written any code.
So read the comments on planned items closely. A comment like "this would help, but what we really need is..." on something you're about to build is worth a meeting.
Changing your mind is allowed
Plans change for good reasons: you learned something, the market moved, a smaller fix turned out to solve the real problem. Customers accept that, as long as you tell them. What they don't accept is a planned item quietly disappearing.
When something comes off the roadmap, move it back with a sentence. "We've moved this back to review. The new import covers most of what people asked for here, and we want to see what's left." Honest and short.
One source of truth
The quickest way to a stale roadmap is keeping it separately from the work. If your public roadmap is a slide someone updates once a quarter, it'll be wrong most of the time. If it's the same data your team moves every day, it stays current without anyone remembering to update it.
A roadmap that's always roughly right beats one that's perfectly right once a quarter.