Skip to content
Swingback, home

BlogRoadmap and changelog

Public roadmap: should you have one, and what to leave off

Whether your product needs a public roadmap, what to leave off it, dates first, and how to keep it current: make it a view of the requests people vote on.

By Elie Baier · · Updated · 4 min read

Most software products should have a public roadmap, as long as it's small: three columns (planned, in progress, done), no dates, and nothing your customers didn't ask about. It should also come straight from the requests people voted for, not from a document someone has to remember to update. A roadmap like that answers "are you working on this?" before anyone writes in, and shows that asking leads somewhere. A big, dated one turns into a list of missed promises.

What a public roadmap is for#

A public roadmap isn't your plan. It's a promise about direction, and an answer to three questions customers ask anyway:

  • Did you hear me? A request that moves to Planned tells everyone who voted for it that it was read. Without a roadmap, they assume it wasn't.
  • Is it worth waiting for? A prospect weighing your product against another wants to know whether the missing integration is coming. "Planned" can keep a deal that "we can't say" loses.
  • What happened to the thing I asked for? The done column, linked to what shipped, is the answer people rarely get.

Those answers also save your support team from writing them one at a time.

When not to have one#

Sometimes a roadmap is better left private:

  • You can't keep it current. A roadmap whose In progress column hasn't moved in three months says the product is stalled, whether or not it is. No roadmap is better than a stale one.
  • Your plan is mostly contracts. If what you build next is decided by two enterprise customers' agreements, a public board of votes tells everyone else a story that isn't true.
  • One item would hand over your strategy. That's rarer than it feels. Your competitors already read your changelog and your job posts, and a column of customer requests tells them little. When it's true, leave that one item off rather than the whole roadmap.

What to leave off#

The roadmaps that work are mostly defined by what they leave out.

  • Dates. A date on a public roadmap gets quoted back to you the day after you miss it. Planned, In progress and Completed say what customers need. If you must give a horizon, "now, next, later" promises less than a quarter.
  • Internal work. Refactors, upgrades and infrastructure mean nothing to a reader, and make the columns look busy. Put them on when customers feel them, as "Pages load twice as fast", not as "Move to the new database".
  • Bugs. A bug list on a roadmap reads as a list of what's broken. Fix them, and say so in the changelog.
  • What you haven't decided. Open and Under review are for your team to sort through. On the roadmap, they make hundreds of requests look like commitments.
  • What you decided against. A request you won't build belongs on its own page with an honest reason, said the right way, not in a column of rejections.
  • What was asked in private. A customer describing their own workflow, or a request from a private board, stays where they wrote it.

Make it a view of your requests#

The way roadmaps go stale is by being a second document. Someone keeps a Notion page or a Trello board for customers while the real status lives in the issue tracker, and the two drift apart within a month.

A roadmap that is simply your requests, grouped by status, can't drift. Moving a post to In progress moves it on the roadmap. Its voters see it where they voted, and they hear about it too. And when a request reaches Completed, the changelog entry that delivers it tells the same people, which is the other half of the loop.

It also sorts itself. Within a column, the most-voted requests come first, and Completed lists the latest first, so the top of each column is what most people are waiting for or most recently got.

The portal's roadmap: requests grouped by status, the most voted first, and Completed the latest first. Changing a request's status moves it.

A short checklist#

Before you publish yours, check that:

  1. Every item is something a customer could ask for in their own words.
  2. No item has a date, and no column claims more than you can deliver.
  3. Each item links to the request its voters are on, so they can follow it.
  4. A done item says how to use it, through the changelog.
  5. Someone owns moving items, and does it when the work moves, not once a quarter.

In Swingback#

The roadmap is your posts grouped by status: nothing else to keep up to date. Your portal shows three columns, Planned, In progress and Completed, and each customer sees only the posts they may see: a private post shows to its author alone. Your team's own roadmap, in the dashboard, has all six statuses. The roadmap can also be a tab of the widget in your product.

When you change a post's status, its followers hear about it, and you can add a note that shows in the post's history. A board can stay off the roadmap, a board of bug reports for instance, and the whole roadmap can be hidden from the portal while your team keeps using it.

Roadmap and changelog has the settings, and Changelog vs release notes what to write when an item reaches Completed.