Votelantern

Product roadmap template: organize by theme or by quarter

A product roadmap is not a list of features with dates. It's a short statement of the problems you plan to solve for customers, in roughly the order you plan to solve them. The best ones are boring to read in a good way: clear, specific and believable.

This page has two free product roadmap templates, each filled in with a fictional example. One groups work by customer theme. The other sets a goal for each quarter. A third, simpler layout is at the bottom if you want to start small.

Template 1: Product roadmap by theme

Example (fictional) Product roadmap by theme
Crumbcount is a fictional recipe-costing app for small bakeries; the themes and items below are made up for the example.
Now
In progress
Next
Planned
Later
Under review
Ingredient prices from supplier invoices
Type in a new invoice price once and every recipe that uses the ingredient updates.
costing
Scale a recipe to any batch size
Turn a 12-loaf recipe into a 40-loaf one without doing the math by hand.
recipes
Cost per slice
See what one slice or one roll costs, not just the whole batch.
costing
Daily prep list
One list of what to mix, proof and bake tomorrow, built from the orders.
planning
Allergen labels
Print a label that lists the allergens in each product from its recipe.
labels
Packaging and labor in the cost
Add boxes, bags and baker hours so the cost reflects what leaves the shop.
costing
Wholesale price sheet
Share a price list with cafes that buy from you, built from your costs and margins.
wholesale
Suggested retail price
Get a starting price for a new product from its cost and the margin you aim for.
pricing

Crumbcount, a fictional recipe-costing app for bakeries, sorts its roadmap into three themes: know your costs, plan the bake, and sell more. Each theme is a lane that runs across Now, Next and Later, and the cards move between columns as the request statuses change.

Open this in Votelantern

When to use it: your product serves a few distinct jobs, and you want customers to find the part of the roadmap that matters to them. A baker who only cares about pricing reads one row and stops.

How to pick themes: write down the three to five outcomes customers mention most when they describe why they pay you. Name each theme as that outcome, not as a part of your code. "Know your costs" works; "Costing module" makes readers translate it in their heads.

Template 2: Product roadmap by quarter

Example (fictional) Product roadmap by quarter
Keyhollow is a fictional move-in inspection app for small property managers; the quarters and items below are made up for the example.
Q1 2027: faster inspectionsQ2 2027: happier tenantsQ3 2027: fewer disputes
Room-by-room checklist
Walk through a unit one room at a time with the items you always check.
inspections
Reuse last inspection
Start a move-out inspection from the move-in one, so only changes need notes.
inspections
Offline mode in basements
Keep working where there is no signal and sync when back online.
reliability
Tenant sign-off by email
Tenants confirm the inspection report from a link, with no account needed.
tenants
Plain-language report
A report tenants can read in a minute, with the condition of each room in one line.
reports
Side-by-side move-in and move-out
Show both inspections next to each other so changes are easy to spot.
reports
Deposit deduction notes
Record why part of a deposit was kept, linked to the room and item.
deposits

Keyhollow, a fictional move-in inspection app for property managers, gives each quarter one goal in its heading: faster inspections, happier tenants, fewer disputes. Every card under a quarter serves its goal. On a quarterly layout you place each card yourself, and a card can link to the request behind it.

Open this in Votelantern

When to use it: you plan in quarters and the people reading the roadmap (sales, investors, larger customers) want rough timing. The goal in each heading stops the quarter from becoming a grab bag.

A caution: let detail fall away with distance. Keep the current quarter specific and the furthest one to a few broad cards, or readers may treat guesses as commitments and you'll spend the year explaining changes.

Where the items come from

A product roadmap is only as good as the evidence behind it. For a small software team, three sources cover most of it:

Votes on a feedback board are a strong signal, but they aren't the whole decision. Say a request has 40 votes from users on your free plan and another has 6 from your largest paying customers; neither number tells you what to build on its own. Use votes to find what's common, then talk to a few of the voters to learn why they want it.

Turning requests into roadmap cards

Requests and roadmap cards aren't the same thing. Three requests ("export to my accountant", "send to the books", "download for tax time") may all be one card: "Export to the accounting ledger." When you write the card:

  1. Merge the duplicate requests into one, so the votes add up in one place.
  2. Write the card title as the outcome the requesters want.
  3. Keep the description to one sentence about the problem, not the build plan.
  4. Link the card to the merged request, so voters can follow it.

Spreadsheet, whiteboard or live roadmap?

A free product roadmap template in Excel or Miro is a fine place to think. Spreadsheets are good for sorting and scoring; whiteboards are good for a planning session with sticky notes. Both fall short once you want customers to see the plan. You end up exporting an image, pasting it somewhere, and redoing it every time something moves.

A status layout, such as Now, Next, Later or the theme template, stays current on its own because it reads your feedback board. When you set a request to In progress, it appears under Now. When it ships, it leaves the roadmap and shows up on your changelog. Nobody has to remember to update a file. A quarterly layout is different: you place and move its cards, so give it a look whenever plans change.

How the board feeds the roadmap in Votelantern

Votelantern gives you a public feedback board, a roadmap page and a changelog page that all share the same requests.

Pricing is still in draft. The Free plan includes one public board with its roadmap and changelog, unlimited end users and votes, and a "Powered by Votelantern" badge. Team (price not set yet) covers up to five boards, up to three admins and a custom domain. Business (price not set yet) adds private boards, which only people signed in from your own app can see.

Want something even simpler? The Now, Next, Later layout has no themes and no dates. See it filled in, with a quarterly layout beside it, on the main roadmap template page, or open it straight away:

Open this in Votelantern

Four filled-in product roadmap examples show how different kinds of product word their cards. For engineering work, try the technology roadmap template.

FAQ

Theme or quarter: which should I start with? Start with themes if your readers are customers. Start with quarters if your readers are people inside the company or investors who plan by the calendar.

How many items belong on a product roadmap? Enough to show direction, few enough to read in a minute. We suggest no more than three or four cards per theme or quarter.

Should a product roadmap include bug fixes? Not usually. Fixes go in release notes. The exception is a known problem so large that customers ask about it; then a card saying you're on it is worth showing.

Can I keep one roadmap for customers and another for the team? Yes. Each board has one roadmap, so use a public board for customers and a private board for internal work. A private board's roadmap and changelog are private too. Private boards are on the Business plan.

All templates and guides