---
title: "12 Public Roadmap Examples to Learn From (2026)"
summary: "12 real public roadmaps from Buffer, GitHub, AWS, Heroku, Mastodon, Microsoft and more, each checked live on Nov 4, 2026, and what each one does well."
date: 2026-11-04
author: "Karthik Kamalakannan"
canonical: https://featureos.com/blog/public-roadmap-examples
markdown: https://featureos.com/blog/public-roadmap-examples.md
categories: ["product-management","guides"]
readingTime: 6
---

A good public roadmap shows what is planned, what is in progress and what shipped, and lets customers react to it. The 12 examples below are real roadmaps we opened on November 4, 2026: seven run on FeatureOS (we make it, so weigh that) and five are well-known roadmaps on GitHub or a company's own site. Each one does at least one thing worth copying.

If you are still choosing a tool, start with [product roadmap software](/blog/product-roadmap-software) or our [public roadmap software](/public-roadmap-software) page. This post is about what to put on the roadmap once you have one.

## The 12 examples at a glance

| Roadmap | Built with | Layout | What to copy |
|---|---|---|---|
| [FeatureOS](https://feedback.featureos.app/roadmap) | FeatureOS | Planned / In Progress / Completed | Bugs and features on one roadmap |
| [Buffer](https://suggestions.buffer.com/roadmap) | FeatureOS | Five stages, including Beta | A Beta stage between building and released |
| [PeopleForce](https://feedback.peopleforce.io/roadmap) | FeatureOS | Completed column first | Leading with what shipped |
| [anny](https://roadmap.anny.co/roadmap) | FeatureOS | Planned / In Progress / Completed | Custom domain, roadmap next to changelog |
| [Tandem](https://feedback.tandem.net/roadmap) | FeatureOS | Planned / In Progress / Completed | Bugs split by platform |
| [OnTheClock](https://ontheclock.featureos.app/roadmap) | FeatureOS | Monthly timeline | Dates instead of columns |
| [Asolvi](https://asolvi.featureos.app/roadmap) | FeatureOS | "Discovery pipeline" | One portal for several products |
| [GitHub](https://github.com/github/roadmap) | GitHub issues and Projects | Labeled issues, project board | Release phases and a link to the changelog when shipped |
| [Heroku](https://github.com/heroku/roadmap) | GitHub issues and Projects | Project board | Customers can open and comment on items |
| [AWS Containers](https://github.com/aws/containers-roadmap) | GitHub issues and Projects | Project board | Preview programs tracked on the roadmap |
| [Microsoft 365](https://www.microsoft.com/en-us/microsoft-365/roadmap) | Own site | Filterable list with dates | Rollout dates per release ring |
| [Mastodon](https://joinmastodon.org/roadmap) | Own site | Short list by version | Items tied to version numbers |

## Roadmaps built on FeatureOS

### 1. FeatureOS

Our own [roadmap](https://feedback.featureos.app/roadmap) opens with one line of intro and three columns: Planned, In Progress and Completed. Every card shows its vote count and the board it came from, so feature requests and items from the Bugs & Fixes board sit side by side.

**What to copy:** put bugs on the roadmap, not just features. Customers who reported a bug want to see it move too. Small fixes are tagged "[Paper cut]" so nobody mistakes them for big launches.

### 2. Buffer

Buffer's [roadmap](https://suggestions.buffer.com/roadmap) has five stages: Exploring, Planned, In Progress, Beta and Released. Cards come from separate boards for feature suggestions and for new channel and integration requests, and the vote counts are public. At the time of writing, a request for a Reddit channel led the Exploring column with about 3,000 votes.

**What to copy:** the Beta stage. It tells customers a feature exists and can be tried before it is called done, which is when feedback is most useful.

### 3. PeopleForce

The HR platform's [roadmap](https://feedback.peopleforce.io/roadmap) opens on its Completed column, with the request title, vote count, board (Feature Requests, Recruiting, Integrations) and date for each item. A "Product updates" tab sits next to it.

**What to copy:** lead with what shipped. A long Completed list is the best proof that requests on the board get acted on. Posts arrive in more than one language, and the board accepts them as they are.

### 4. anny

The booking software company runs its [roadmap](https://roadmap.anny.co/roadmap) on its own domain, with a Changelog tab one click away. Columns are Planned, In Progress and Completed, and each card is tagged as a Feature Request or an Improvement. Posts are in German and English.

**What to copy:** keep the roadmap and the changelog next to each other on your own domain. A customer can follow an item from "Planned" to the release note that announced it.

### 5. Tandem

The language exchange app's [roadmap](https://feedback.tandem.net/roadmap) keeps bugs on separate boards per platform: Web App, Android and iOS, each with its own emoji label, next to Feature Requests. The Planned and In Progress columns are short, a handful of items each.

**What to copy:** label items by platform when you ship on several. And keep In Progress honest: a short list people believe beats a long one nobody does.

### 6. OnTheClock

OnTheClock's [product roadmap](https://ontheclock.featureos.app/roadmap) uses a monthly timeline instead of columns. Items sit on a calendar that runs across the coming months.

**What to copy:** use a timeline when your customers plan around dates. Use columns when you would rather not commit to them.

### 7. Asolvi

Asolvi's [roadmap](https://asolvi.featureos.app/roadmap) is called a "Discovery pipeline". Requests start in a Received column, and each card is tagged with the product it belongs to (for example Tesseract, Asolvi Anywhere or MySalesDrive).

**What to copy:** one portal for several products, with a product tag on every item. Naming the roadmap a "discovery pipeline" also sets expectations: received does not mean promised.

## Roadmaps on GitHub and company sites

### 8. GitHub

GitHub's [public roadmap](https://github.com/github/roadmap) treats every item as an issue. Labels show the release phase, the feature area, the product SKUs and the deployment model (cloud, server or both). When an item ships, it gets a "shipped" label and the issue is closed with a link to the changelog post. Issues are read-only; feedback goes to GitHub's community discussions.

**What to copy:** close the loop. Every shipped roadmap item points to the release note that announced it.

### 9. Heroku

Heroku's [roadmap](https://github.com/heroku/roadmap) is also built on GitHub, and customers can propose ideas and comment on existing items. The README states plainly that items can change at any time and that purchasing decisions should be based on what is available today. It also credits the AWS Containers roadmap for the format.

**What to copy:** the disclaimer. One sentence saying the roadmap is not a contract protects you and sets the right expectation with buyers.

### 10. AWS Containers

The [AWS Containers roadmap](https://github.com/aws/containers-roadmap) covers ECS, ECR, Fargate and EKS. Developer preview programs are tracked in the same repository, with past programs listed once they are generally available, and the README links to other AWS public roadmaps.

**What to copy:** put early-access programs on the roadmap. Customers who want a feature most are the ones who will test it.

### 11. Microsoft 365

Microsoft's [roadmap](https://www.microsoft.com/en-us/microsoft-365/roadmap), now called the AI at Work roadmap, lists features with estimated release dates. Rollout start dates show when a change reaches Targeted release and then Standard release, and items are removed once they are generally available, cancelled or postponed.

**What to copy:** if you roll out in stages, say which group gets a feature first. Admins plan around that more than around the feature itself.

### 12. Mastodon

[Mastodon's roadmap](https://joinmastodon.org/roadmap) is a short page, not a board. Each item has a status (Released or Next release), the version it belongs to (4.6, 5.0) and a "Learn more" link.

**What to copy:** a roadmap does not need a tool to be useful. A short list tied to version numbers is easy to read and easy to keep current.

## What the best public roadmaps have in common

- **Three to five stages, clearly named.** Planned, In Progress and Completed is enough for most teams. Add Beta or Exploring only if you use them.
- **A visible Completed or Released list.** It is the proof that feedback leads somewhere.
- **A link from shipped item to release note.** GitHub and anny both make this easy to follow. In FeatureOS, a [changelog](/release-notes) entry can link to the requests it ships, and voters are notified.
- **Votes or comments.** A roadmap customers can react to tells you what to build next.
- **A line about uncertainty.** Heroku's disclaimer and Asolvi's "Discovery pipeline" both stop a roadmap from reading like a contract.

To set one up, see [what a public roadmap is](/glossary/public-roadmap), [FeatureOS roadmaps](/roadmaps) and [public roadmap software](/public-roadmap-software). Roadmaps change daily, so the columns and counts above may look different when you visit. Spot an error? [Tell us](/support).
