# Public roadmap launch checklist

Before you publish your roadmap to customers. 12 boxes.

---

## Content

- [ ] Every column has a clear meaning written above it. "Planned" vs
      "Considering" vs "Backlog" — pick one and define it.
- [ ] Every "In progress" card has a public description.
- [ ] No card mentions specific dates. "Soon" is fine; "March 15" isn't.
- [ ] No card mentions specific customer names without permission.
- [ ] Every "Completed" card links to the changelog entry.

## Tone

- [ ] Card titles are written from the customer's perspective.
      ("Search across all comments" not "Refactor search index").
- [ ] No internal jargon (sprint names, ticket IDs, codenames).
- [ ] Anything Closed/Won't Build has a one-line reason.

## Loop

- [ ] Voting is on. People who voted will get notified when status changes.
- [ ] Comments are on (or you've explicitly chosen not to — fine, but
      decide).
- [ ] Submission is open *or* gated to "via support email" — pick one and
      tell people.

## Signal

- [ ] You've set up a weekly reminder to triage votes.

---

*Print and check before you announce. The board is a promise — keep
the bar high.*