> ## Documentation Index
> Fetch the complete documentation index at: https://docs.buildbetter.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Roadmap

> A public Planned / In Progress / Shipped roadmap that moves as the work moves, built from your feedback board

The public roadmap is a **view over your feedback board's status columns**, not a separate document. Move a post to In Progress and the roadmap shows it there. There is no second artifact to keep in sync, which is the usual reason public roadmaps go stale.

## The Columns

| Column          | Means                  |
| --------------- | ---------------------- |
| **Planned**     | Committed, not started |
| **In Progress** | Being built now        |
| **Shipped**     | Released               |

Three columns is deliberate. Customers understand them without a legend, and they don't imply dates you haven't committed to.

<Warning>
  A public roadmap is read as a promise even when you frame it as an intention. Put things in **Planned** only when you'd be comfortable being asked about them in a renewal conversation.
</Warning>

## Why It Stays Current

The roadmap reflects post status, and post status is something your team already changes while doing the work. There is no separate export, no spreadsheet, and no weekly sync — which means the common failure mode, a roadmap that quietly stops matching reality, requires actively neglecting the board rather than merely forgetting to update a doc.

## Demand Behind Each Item

Every roadmap item is a post, so it carries its votes and — through [post matching](./boards-and-voting#post-matching) — the feature requests extracted from your calls and tickets.

Prioritization stops being an argument about who remembers which customer conversation. You can see the accounts asking and the evidence behind each item.

## When Something Ships

Moving a post to **Shipped** is the public signal. It is not the same as telling the people who asked.

* **Publish a [changelog entry](./changelog)** so anyone reading the portal sees what changed.
* **Use [Close the Loop](../Success/close-the-loop)** to match the shipped release back to every customer who requested it and draft the individual follow-up.

A roadmap column moving is broadcast. Close the Loop is the personal message. Doing only the first is why customers say they never heard their request landed.

## Visibility

The roadmap inherits its board's visibility. Run it privately until the statuses are honest, then make it public.

## Next

<CardGroup cols={2}>
  <Card title="Boards & Voting" icon="thumbs-up" href="./boards-and-voting">
    Posts, statuses, and the demand behind them.
  </Card>

  <Card title="Close the Loop" icon="rotate" href="../Success/close-the-loop">
    Telling the customers who asked.
  </Card>
</CardGroup>