# The Responsible Roadmap A public roadmap is a trust instrument that most companies treat as a marketing surface, which is how it curdles. Dates slip, promised features quietly vanish, and the page becomes a museum of broken commitments. The responsible version publicizes direction without selling futures: now, next, later, no dates, and a changelog underneath acting as the receipts. The roadmap is the bet sheet; the changelog is proof you keep paying out. The style I keep coming back to is Supabase's release pages. The titles read like commit messages: "Realtime Broadcast now supports binary payloads." The feature is the headline. No semantic hook, no verb dressed up for a webinar, and when they do celebrate, the launch week pages bring the emoji and the confetti in a way that feels old-school and human, a side-scroll through what got built. A reader can scan and know exactly what changed, which is a form of respect. The plain sentence says the team is confident the feature speaks for itself. Engagement follows honesty here. Let customers vote on the backlog, comment on the bets, see their request move from later to next. That converts a roadmap from a promise you can break into a conversation you are having. I run a private version of this loop on [[Feature Backlog|Vibe Reader's backlog]], and the public PostHog-style changelog for this site is still on my list. The principle scales up and down: publish what shipped in plain words, publish what is next as intent, and never let the marketing team retitle a feature into a hook.