Roadmap vs changelog:
what each is for

A customer asks for something on your feedback board. Two questions follow: will you build it, and did you? A roadmap answers the first. A changelog answers the second.

The roadmap

A roadmap is a list of what you are considering, building or have decided against. Keep it to a few honest states, such as planned, in progress and not planned. Leave out dates you can't keep: a date you miss does more damage than no date.

The changelog

A changelog is a dated list of what shipped, written for the people who asked. One line per change is enough, with a link back to the request that prompted it.

Why the board needs both

• Voters get an answer. A request with no status looks ignored. A status, even "not planned", tells people you read it.
• Shipping closes the loop. When a request moves to done and a changelog entry appears, everyone who voted can see their vote counted.
• It keeps you honest. A changelog is a record. If the roadmap says "planned" for six months and nothing appears, the gap is visible.

A small habit that works

When you ship, change the request's status first and write the changelog line second, in the same sitting. Doing both together is easier than catching up later.

Dupes Feedback has a public board, a roadmap and a changelog in one place. You can see them working on our own vote for the next dupe.

Try the live voting board ↗ Open the live board ↗ Join the hosted waitlist ↗