Skip to content

Product roadmaps

Plan in the open.Ship with clarity.

Share a public roadmap customers can follow — keep internal plans private. Feedback, prioritization, and progress in one workspace.

TRUSTED BY THE BEST

1,500+ teams ship products instead of roadmaps with FeatureOS.

“Pricing felt right. Product felt intuitive. They even built a new feature for us!”
Michael Eckstein, Product Marketing Manager at Buffer
4.1M end users on FeatureOS boards
86% customers over 3+ years with FeatureOS

The loop

How a roadmap stays honest.

Votes first. Then the card. Then the lane. Then the changelog.

  1. Collect. Votes land on your boards first. Demand is counted before anything is promised on a roadmap.

  2. Add. Put a post on a roadmap, or live-sync a saved filter so matching requests appear without a second copy.

  3. Move. Drag cards across lanes as work progresses. Custom columns and statuses match how the team actually ships.

  4. Ship. Close the loop in changelog. Voters see what landed instead of chasing a status email.

Visibility

Public for customers.Private when it has to be.

A public roadmap on the portal for customers. A private one for the org. Visibility is per module, and you can hide boards or card details you are not ready to show.

  • Public roadmap on your portal
  • Private roadmap for org members
  • Module visibility by Team / Customers / Guests
  • Hide specific boards from the roadmap
  • Hide created dates and ETC on cards

Capabilities

What you can actually do.

Three views, two scoring methods, as many roadmaps as you need, and the embeds to share them.

Views

  • Timeline (Gantt)
  • Kanban
  • List
  • Default landing view

Prioritize

  • R.I.C.E.
  • Value vs Effort + chart
  • Sort by latest
  • Sort by votes
  • Sort by ETC

Many roadmaps

  • Product / quarter / team
  • Import a saved filter
  • Live-sync a saved filter
  • One post on many roadmaps

Share

  • Full embed
  • Board-specific embed
  • SSO embed
  • Headerless snippet
  • Trusted domains
  • Print / PDF

Get started

Get a public roadmap live.

Enable the module, pick who can see it, add posts or a filter, then share.

  1. 1

    Enable Roadmap

    1 min

    Turn the module on. The workspace already has the boards your cards will come from.

  2. 2

    Choose public or private

    1 min

    Public on the portal, or private for org members. Set who sees the module: Team, Customers, or Guests.

  3. 3

    Add posts or sync a filter

    5 min

    Drop posts onto cards, or live-sync a saved filter so the list stays current.

  4. 4

    Embed or share the portal

    2 min

    Share the portal link, or drop a full, board-specific, SSO, or headerless embed on trusted domains.

Roadmaps

Questions about product roadmaps

What a roadmap is, how views and scoring work, and how you share it.

Have more questions?

A product roadmap is a visual plan of what you are building, what is in progress, and what already shipped. In FeatureOS it is built from feedback posts, so a card can carry the votes and requests behind it. Share a public version on the portal, or keep a private one for the org.

Yes. A public roadmap lives on your portal for customers to follow. A private roadmap is limited to org members. You also set module visibility for Team, Customers, and Guests, hide boards you do not want on that view, and hide created dates or ETC on cards.

Three views: Timeline (Gantt), Kanban, and List. Switch between them anytime, drag cards across lanes, and set a default landing view so visitors open the one you want first.

Score cards with R.I.C.E., or plot Value vs Effort and use the chart. Sort the list by latest, votes, or ETC. FeatureOS does not ship a third named framework — those two, plus the sorts, are the built-in options.

Yes. Add a board post to a roadmap card, or import / live-sync a saved filter so matching posts appear without a second copy. One post can sit on many roadmaps. Linking the posts behind a card shows why it made the list.

Jira can stay in sync with FeatureOS: push a post as an issue, link an existing key, export issues back as posts, and choose One-to-One, All-to-One, or FeatureOS-to-Jira status rules. Linear connects posts to issues and can update status when linked issues move — it is not a guaranteed two-way sync of the roadmap itself.

Yes. Run separate roadmaps for a product, a quarter, or a team. Import or live-sync a saved filter onto each one, and keep the same post on more than one roadmap when it belongs in both places.

Yes. Use a full embed, a board-specific embed, an SSO embed, or a headerless snippet. Restrict the snippet to trusted domains, or print / export a PDF when you need a static copy.

Now / Next / Later is a time-horizon way to talk about priority without fixed dates. FeatureOS does not ship it as a named mode. Custom columns and statuses let you label lanes however the team plans — including those horizons if you want them.

There is no separate archive action on a roadmap. Hide boards you no longer want on a public view, keep finished work in a shipped column, or leave a private roadmap for the team. Board archive exists on feedback boards; it is not a roadmap feature.

Updated August 2026

Machine readable

Ask an AI about product roadmaps

Open Claude, ChatGPT, or Perplexity pre-filled with a prompt that points the model at /roadmaps.md, the machine-readable version of this page.

Research FeatureOS roadmaps with AI
View as Markdown

Product roadmaps

Your roadmap, without the spreadsheet theater.

Public for customers, private for the org. Cards stay tied to the votes that put them there.