# How to turn customer feedback into a roadmap

> Start from themes that repeat across feedback, not from single requests. Turn each theme into a bet with a problem, a group of customers and a clear success signal. Sort bets into now, next and later, and keep a link from each roadmap item back to the feedback that justified it.

Source: https://escutaproduto.com/resources/turn-feedback-into-roadmap
Last updated: 2026-10-09

## Start from themes, not from single tickets

A roadmap built from single requests reflects who wrote most recently, not what matters most. Start by grouping the feedback into themes. A theme is a problem customers keep describing in different words, such as "I cannot get my data out in the format my accountant wants." One request for a monthly CSV export is an item. Five requests across three months that all describe the same reporting pain are a theme.

Grouping takes patience. Read the feedback in batches, write a short name for each theme, and record which items belong to it. Do not worry about getting it perfect. A rough set of themes is far more useful than a perfect list of features.

## Turn themes into bets

A bet is a theme with a plan attached. Write it as one sentence with three parts: the customer problem, the group of customers who have it, and the signal that would show you solved it. For example: "Teams who report monthly to finance need a clean monthly export, and we will know it worked when those teams stop asking for workarounds."

Keep the signal honest. You do not need a percentage or a survey to define it. "Requests for the workaround stop" is a fine signal if you will actually watch for it.

## Use now, next and later

Now, next and later is a simple way to sort bets without fake dates. Now means the team is working on it. Next means it is decided and waiting for capacity. Later means it is worth keeping on the list but not yet chosen.

Sorting by time window, not by date, keeps the list honest. When a bet slips, it moves from now to next, which is a normal change. You do not have to rewrite a calendar.

Limit now to what the team can really do. A "now" list of twelve items is a wish list. Two or three is a plan.

## Keep a link from each item to its feedback

The roadmap is only as trustworthy as its links back to customers. For each item, keep a note with the feedback items that justify it. Use the item's internal note to list the count of distinct customers who asked and the themes they described. This makes the roadmap defensible when someone asks why you built one thing before another.

The link also tells you who to tell. When a bet ships, the people linked to it are the ones to thank and inform. That is the step most teams skip, and it is the one customers notice.

## Set how often the roadmap changes

Review the roadmap on a fixed rhythm. Monthly works for most small teams, with a short check each week for anything that moved. Changing the roadmap every day teaches the team to ignore it, and changing it once a year means it is wrong most of the time.

Record each change with a short reason. "Moved the export bet from now to next because the reporting fix took longer" is useful the next time someone asks why it slipped.

## What a roadmap is not

A roadmap is a plan for the team, not a list of promises to customers. It is also not a count of votes. Feedback is input, not a ballot, and a loud group of users can outweigh a quiet group that matters more to your business. Weigh each theme by how many distinct customers describe it, who they are, and how well it fits the direction you chose.

Do not publish the roadmap as a promise. If you want customers to see progress, share what shipped through a changelog and direct replies. For the reasons and the alternatives, see [should you have a public roadmap](/resources/public-roadmap-pros-and-cons).

## Plan for the bets you will not build

Every roadmap has a list of ideas that will never ship. Keep that list on purpose. Write down the bets you considered and dropped, with a short reason for each. When a customer asks about one of them six months later, you can point to the reason instead of reconsidering from scratch. The list also protects the team from the same debate every quarter. A dropped bet with a clear reason is a decision, not a failure.

## Building the roadmap from Escuta Produto

Escuta Produto does not have a roadmap feature. It keeps the feedback, and you keep the roadmap in a tool of your choice, such as a document, a spreadsheet or your project tracker. The inbox gives you the inputs: each item with its type, status, notes and sender.

Use the statuses to show where a theme sits. Items you have decided to act on are planned, items being built are in progress, and shipped items are done. Filter by type and by status to see which kinds of requests are waiting. The 30-day chart shows whether a theme is growing.

Export the feedback as CSV when you want to group themes in a spreadsheet, then bring the bets back into your roadmap document. Check which columns the export includes, and keep enough of each row, such as the message text, to find the source feedback again. For the status rules that make these filters reliable, see [how to design a feedback status workflow](/resources/feedback-status-workflow). For the weekly routine that feeds the roadmap, see [how to triage customer feedback](/resources/how-to-triage-customer-feedback). Alerts for new items are set up in the [notifications docs](/docs/notifications).

## Frequently asked questions

### How do you turn customer feedback into a roadmap?

Group the feedback into themes that describe the same problem, turn each theme into a bet with a clear customer problem and a success signal, then sort the bets into now, next and later. Link each item back to the feedback that justified it.

### What is the now, next and later roadmap format?

It sorts work into three time windows without fixed dates. Now is in progress, next is decided and waiting for capacity, and later is kept on the list but not yet chosen. Items move between columns as priorities change.

### How often should you update a feedback-based roadmap?

Review it monthly with a short weekly check for changes. Record each move with a reason, so the team can see why a bet slipped. Changing it daily teaches people to ignore it.

### Does Escuta Produto have a roadmap feature?

No. Escuta Produto keeps the feedback, with statuses, notes and CSV export. You keep the roadmap in your own document, spreadsheet or project tracker and link it back to the feedback items.