---
title: "Public Roadmap: What to Show, What to Hide (and Why It's Worth It)"
summary: "A public roadmap builds trust until it becomes a list of promises. Here is what to put on it, what to keep off, and the settings that control it."
date: 2026-11-13
author: "Karthik Kamalakannan"
canonical: https://featureos.com/blog/public-roadmap-what-to-show-what-to-hide
markdown: https://featureos.com/blog/public-roadmap-what-to-show-what-to-hide.md
lastUpdated: 2026-11-13
categories: ["product-management","guides"]
readingTime: 3
---

Should you publish your roadmap? Yes, if you publish themes and statuses and leave out dates you can't keep. A public roadmap earns trust when customers can see what you are working on and why. It loses trust the day a date on it slips.

So the real question is what goes on it. Here is how we think about it.

## What a public roadmap is for

A public roadmap answers one question for a customer: "is the thing I asked for going to happen?" It also answers it for the people who haven't asked yet. They see a product that is moving, and that matters when they are deciding whether to buy.

We run [our own public roadmap](https://feedback.featureos.app/roadmap) the same way.

It is not a commitment list, and it is not a changelog. The roadmap says what is coming. The [changelog](/release-notes) says what shipped. If you mix the two, both get worse. We wrote about the split in [changelog vs roadmap](/dossier/difference-between-changelog-and-roadmap).

## What to show

**Themes and problems, not feature specs.** "Faster onboarding for admins" survives a change of plan. "Add a setup wizard with six steps" does not.

**A small number of statuses.** Under review, planned, in progress, completed. That is enough. Every extra lane is one more thing to keep current.

**Items customers asked for.** When a request on your [feedback board](/blog/what-feedback-boards) moves to planned, the people who voted can see it move. That is the point of having both in one place.

**A few "not now" items.** Showing what you decided against, with a reason, makes the rest of the roadmap believable.

## What to hide

**Dates you can't keep.** Dates are what customers screenshot. If you can't stand behind a date, don't show it. A quarter is safer than a day, and a status with no date is safer than both.

**Anything under negotiation.** Work for one named customer, unsigned deals, partner launches that aren't announced. Keep these on a private roadmap.

**Internal chores.** Refactors, migrations and tooling matter to you. They don't help a customer decide anything.

**Unfinished ideas.** If the team is still arguing about it, it is not ready to be public.

## Who gets to see it

Public doesn't have to mean "everyone on the internet". Two settings control it:

- **Make the roadmap private.** One toggle in the roadmap settings limits it to members of your organization. Use it for anything that isn't ready for customers.
- **Choose who sees the Roadmap tab.** Module Visibility lets you show or hide the Roadmap separately for team members, customers and guests. You can show it to logged-in customers and hide it from visitors who are only browsing.

Showing it to customers first is a good middle step if your team is nervous. You hear from the people who matter most before the whole internet sees it.

## The controls that keep a roadmap honest

These are all settings on the roadmap, so you don't have to rely on everyone remembering the rules:

- **Hide a lane** from the customer view, for example a "Backlog" lane you only use internally.
- **Hide the ETC date.** ETC is the estimated time of completion. You can track it for the team and keep it off the public page.
- **Hide the post's created date**, so an old request doesn't look neglected.
- **Rename the statuses** to match your voice. "In progress" can say "Building now".
- **Hide completed posts once they are in the changelog**, so the Completed lane doesn't grow forever.
- **Name lanes by quarter**, for example "Q1" and "Q2", if you want time on the page without exact days.

Teams that need more than one view can run [multiple roadmaps](/blog/new-multiple-roadmaps), for example a public one for customers and a private one for sales.

## Three rules we'd give any team

1. **Every public item links to a reason.** A one-line "why" beats a long description.
2. **Update it when the status changes, not on a schedule.** A roadmap last touched in March is worse than no roadmap.
3. **Say no in public.** Moving a request to "closed" with a reason costs you one sentence and saves ten support threads.

For examples of how other teams lay theirs out, see [12 public roadmap examples](/blog/public-roadmap-examples). For the setup, see [public roadmap software](/public-roadmap-software).

## A 30-minute setup

1. Pick the privacy level. Start with customers-only if unsure.
2. Keep four statuses. Rename them if you like.
3. Hide the ETC date and any internal lanes.
4. Move your top ten requested items onto the roadmap, each with a one-line reason.
5. Put "update the roadmap" on the same checklist as "write the release note".
