Votelantern

Product roadmap examples: four kinds of product, four roadmaps

Templates show you the boxes. Examples show you what to put in them. Below are four filled-in product roadmaps, each for a different kind of software, each made up for this page. They all use the same three-column idea (what's happening now, what's next, what's being weighed) but word their cards very differently, because their readers are different.

Every example is live: what you see is the roadmap page as a visitor would see it, and any of them can be opened as your own roadmap to edit.

Example 1: a B2B software product

Example (fictional) Example roadmap: B2B software product
Tallyfern is a fictional expense-approval tool for finance teams at small companies; every item below is made up for the example.
Building now
In progress
Up next
Planned
Exploring
Under review
Approval rules by amount
Small expenses go to a manager; larger ones also need finance to approve.
approvals
Card feed matching
Match company card transactions to submitted receipts so nothing is counted twice.
cards
Audit log for admins
See who approved, changed or rejected each expense, and when.
admin
Spending limits per team
Set a monthly limit for each team and warn the approver when it is close.
budgets
Export to the accounting ledger
Send approved expenses to the books in the format your accountant asks for.
accounting
Mileage claims
Claim travel by distance, with the rate set once by the finance team.
claims
Per-diem allowances
Pay a fixed daily amount for trips instead of collecting every meal receipt.
claims

Tallyfern is a fictional expense-approval tool sold to finance teams at small companies.

Open this in Votelantern

What to notice:

Example 2: a consumer phone app

Example (fictional) Example roadmap: phone app
Trailmug is a fictional hiking-log app for phones; every item below is made up for the example.
Now
In progress
Next
Planned
Someday
Under review
Record a hike with the screen off
Keep tracking the route while the phone is in a pocket, using less battery.
tracking
Dark map style
A darker map that is easier on the eyes at dawn and dusk.
maps
Download a map area
Save the map for a park before you leave, for places with no signal.
maps offline
Elevation chart
See the climbs and descents of a saved hike on a simple chart.
stats
Share a hike with a friend
Send a link to a finished hike so a friend can see the route and notes.
sharing
Trail notes from other hikers
Read short notes others left about mud, closures or the best viewpoint.
community
Watch companion
Start and stop a hike from a smartwatch without taking out the phone.
devices

Trailmug is a fictional hiking-log app for phones.

Open this in Votelantern

What to notice:

Example 3: a developer API

Example (fictional) Example roadmap: developer API
Routemint is a fictional address-validation API for developers; every endpoint and item below is made up for the example.
In progress
In progress
Planned
Planned
Considering
Under review
Batch validation endpoint
Send many addresses in one request and get one response back.
endpoints
Clearer error codes
Each error says which field failed and why, with a link to the docs.
errors docs
Version 2 of the response format
A tidier response shape; version 1 keeps working for a long notice period.
breaking change
Sandbox keys
Test against fixed sample addresses without using your monthly calls.
developer experience
Client library for Python
An official library so Python users skip writing their own request code.
libraries
Retire the old XML output
XML responses are deprecated; we will post the shutdown date well ahead.
deprecation
Webhook when a stored address changes
Get notified when a postal change affects an address you validated before.
webhooks

Routemint is a fictional address-validation API for developers.

Open this in Votelantern

What to notice:

Example 4: an internal tool

Example (fictional) Example roadmap: internal tool
Order Desk is a fictional internal order-handling tool at Bramblecart, a fictional online garden-supply shop; every item below is made up for the example.
This month
In progress
Next up
Planned
Backlog we are weighing
Under review
Refund button on the order screen
Support staff issue a refund without asking the finance team each time.
support
Faster order search
Find an order by phone number or ZIP code, not only by order number.
search
Stock warnings for the warehouse
Warehouse staff see a flag when an order includes an item that is running out.
warehouse
Notes visible to every team
A note added by support shows up for the warehouse and finance too.
notes
Delivery issue report
A weekly list of late or damaged deliveries for the operations lead.
reports
Seasonal order limits
Cap orders of large items during the spring rush so the warehouse can keep up.
warehouse
Plant care follow-up emails
Send care tips a week after a plant is delivered, triggered from the order.
customers

Order Desk is a fictional internal tool used by staff at Bramblecart, a fictional online garden-supply shop.

Open this in Votelantern

What to notice:

What the four have in common

Look across the examples and the same habits show up:

  1. Six to eight cards. Enough to show direction. Not so many that the roadmap reads like a backlog.
  2. Titles in the reader's words. Each title would make sense to a customer seeing it for the first time.
  3. One sentence per card. The sentence says what gets easier, not how it will be built.
  4. An honest last column. Whether it's called Later, Exploring or Someday, it signals "not promised".
  5. Tags for scanning. One or two per card, so readers can find their area quickly.

Customer-facing versus internal roadmaps

Three of the examples are customer-facing; one is internal. The difference isn't the layout, it's what you're willing to say. A customer-facing roadmap leaves out costs, staffing, competitor plans and anything under contract. An internal one can include all of that, plus the reasons behind each choice.

If you need both, keep two: a public roadmap for customers and a private one that only people signed in from your own app can see, each fed by its own board.

A note on agile roadmaps and slides

Agile teams sometimes worry that a roadmap fights with working in sprints. It doesn't have to. Now, Next and Later describe intent at a level above sprints; the sprint board holds the detail. Updating a card's status when work starts is a small habit that keeps the two in step.

If you came looking for product roadmap slide examples, any of these layouts copies onto a slide by hand. The live version is the one to link from your website, your help center and your release notes, because it doesn't go out of date after the meeting.

How the examples work in Votelantern

Each example opens as a roadmap page tied to a feedback board. Customers post and vote on requests; you set each request's status, and the roadmap places it: In progress under Now, Planned under Next, Under review under Later, in columns you can rename. Linking a changelog entry to a request moves it to Shipped when you publish.

The Free plan covers one public board, its roadmap and changelog, and the widget, with a "Powered by Votelantern" badge. Team (price not set yet) and Business (price not set yet) are the paid plans, and prices may change before launch. Private boards, which the internal-tool example needs, are on Business.

To build your own from a blank layout, start with the product roadmap template or the general roadmap template. If your roadmap tracks a single project with an end date, the project roadmap template fits better.

FAQ

Which example is closest to a typical startup roadmap? For a small team selling software to businesses, the Tallyfern example. Copy its column names and its habit of showing admin features.

Should a customer-facing roadmap show who asked for each item? Show the request and its vote count, not names. On a board, requesters can choose a "First L." display name or post anonymously.

Can I combine two examples? Yes. An API company with a dashboard might take the API example's breaking-change tags and the B2B example's admin cards. Open one, then edit the cards.

How do I know if my roadmap is any good? Show it to two customers and ask them to explain it back to you. If they can, it works. If they ask what a card means, rewrite that card.

All templates and guides