How to Analyze Product Feedback for Your Roadmap

min read - Updated on Nov 15, 2026

You can analyze product feedback for your roadmap in Kimola by collecting the reviews of your app or product in one Report, asking every review two research questions, what customers are missing and what goes wrong for them, and turning the findings into an Action Plan with the goal Product development. Kimola classifies every review into themes and sentiment and answers the Dimensions Unmet Needs and Pain Points, then counts the records behind each answer. A roadmap discussion can then start from how many customers ask for something instead of who asked the loudest. Signals add what changed recently, such as a problem that started with the last release.

This guide follows four steps: collect the reviews, add Unmet Needs and Pain Points, find what changed recently and plan product changes. It works with the App Store and Google Play reviews of a mobile app, with the reviews of a product on another supported platform and with a file of your own feedback.

Getting Ready

Reports, Dimensions, Signals and the Action Plans of a Report are available in every package. Sign in to your Kimola account and have the link to the App Store or Google Play page of your app, or to the review page of your product on a supported platform, ready.

The Goal

This guide answers the question product managers, founders and designers ask before every planning cycle: what should we build, fix or change next, and how many customers want it. Product feedback usually reaches a team through channels that each lean one way. Feature requests come from the customers who write to support, interviews cover a handful of people, and the latest complaint feels the most urgent. Public reviews are written without being asked, they cover every release, and each one comes with a rating and, on most platforms, a date. Counting what they say shows how many customers raise each request and each problem. For more on how teams use Kimola for this work, see Product Feedback Analysis.

The result is a Report with a ranked list of what customers miss and a ranked list of what goes wrong, each with its number of records and quotes in customers' own words, the topics that changed recently and a plan of up to 12 actions. These findings support the roadmap decision. Your team still makes it.

Example

A team that builds a budgeting app has 14 candidate features for the next quarter and no agreed way to rank them. It collects the App Store and Google Play reviews of its app in one Report. The results might show that bank connection errors is the largest pain point, shared budgets for couples the largest unmet need, and dark mode a small one that a few reviewers repeat often. The team ranks its candidate features by the number of customers behind each.

Step 1: Collect App or Product Reviews

Create one Report from the review pages of your app or product, so that every review is classified with the same models and answers the same Dimensions. On Home, paste the link to the App Store or Google Play page of your app into the report creation area. When you don't have the link at hand, type the name of the app in the same field instead. Kimola searches the app stores, you choose the country and the store, App Store or Google Play, and you pick the app from the results. App Store reviews come from the country storefront, such as /us/ or /tr/ in the link, so use the storefront of the market your roadmap is for. For a product sold on a retail or review platform, paste the link to its review page. The platforms Kimola can read are listed in Supported Platforms for Creating Reports from Links, and the full method is in Create a Report by Adding Links.

[Screenshot: The report creation area on Home with the App Store link of an app pasted into it]

Note

App Store reviews come from the country storefront in the app's link. Use the storefront of the market your roadmap is for.

When your app exists on iOS and Android, collect both stores in one Report. Click add multiple in the search bar of the report creation area, and paste each link on a new line. Kimola checks the links, and each one shows "The link is valid!" or "The link is invalid." Every Report from links has a Platform column, so the reviews of the two stores stay apart and Step 2 can compare them. With several links, Kimola spreads the report size you choose across the apps.

The next steps of the wizard set up the analysis. Move the slider to choose the report size, which is the number of reviews Kimola collects, and confirm that you will use the extracted reviews for research purposes only. In the classifiers step, choose the Automatic Classifier, which discovers the themes of your reviews, and the Sentiment Classifier. A content classifier and the Sentiment Classifier together also give the Report its best and worst performing themes. Kimola's pretrained models include classifiers made for specific kinds of products, such as the Mobile App Feedback Classifier and the Software Feedback Classifier. Use the Automatic Classifier when you want the themes to come from your own reviews, and a pretrained classifier when you want the categories of a ready-made model for your kind of product. See List Pretrained Models.

[Screenshot: The Classifiers step with the Automatic Classifier and the Sentiment Classifier chosen]

In the Structure step, turn on Enable Multi-label Classification. A product review often praises one part and criticizes another, such as a customer who likes the design of an app and reports that syncing fails, and multi-label gives that review a label for each, while a single label groups it under one main theme. See Multi-label vs Single-label Classification.

Feedback that isn't on a public page, such as feature requests exported from your support tool or answers to an in-app survey, goes into the Report as a file. Kimola accepts .xls, .xlsx, .csv and .tsv files, one file at a time, up to 30 MB. You choose the Text Column, which holds the feedback, and a Date Column if the file has one. Keep the date, because Step 3 reads how topics change over time. From the classifiers step on, this guide applies to a file in the same way. See Create a Report by Uploading a Custom Dataset.

Step 2: Add Unmet Needs and Pain Points

Dimensions are research questions that Kimola asks of every review, and two of them carry most of the weight for a roadmap. Unmet Needs asks "What is missing or desired?" and collects the features, options and changes customers ask for, openly or through a workaround. Pain Points asks "What goes wrong or creates difficulty?" and collects the breakdowns, obstacles and disappointments customers report. Unmet Needs points to what to build, and Pain Points points to what to fix. Both belong to the Issues group, and the two together cover the requests and the complaints of your feedback.

In the Dimensions step of the wizard, click Unmet Needs and Pain Points to add them to My List. You can find them under All and under Issues. Add Personas, which asks "Who is experiencing this?", when you want to know who asks for a feature before you schedule it. Each Dimension you add multiplies the queries the Report uses: queries = rows × models × Dimensions. See Add Dimensions to a Report for how to choose them.

[Screenshot: The Dimensions step with Unmet Needs and Pain Points in My List]

Note

Every Dimension you add adds to the queries of the Report: queries = rows × models × Dimensions. See How to Calculate Queries.

In the Review step, type a Report Title if you collected several links, because a Report with several sources has no single page title to take it from, for example "Budgeting app: App Store and Google Play". Choose the Report Language: English, Spanish, French, German, Portuguese, Dutch or Turkish. Your reviews can be in any of the 30+ languages Kimola analyzes, whatever the Report Language. See Language Options in Reports. Check Required Query, then click Create Report. When the analysis is complete, Kimola shows "Here we go!" Click View Report to open it. To add a Dimension to a Report that already exists, open its Dimensions page, click the tab of the Dimension that has no check mark and click Generate Now.

Read the Unmet Needs

Open Dimensions in the menu of the Report and click the Unmet Needs tab. A ring shows the share of the Report's records that answer the question. Feedback that expresses no wish or missing piece gets no answer, so the ring tells you how often customers say what they would add or change. The summary card gives a headline and a few paragraphs on what customers want, with key terms in bold. Below it, every need is a cluster with its number of records, its share, a short summary and quotations, which are excerpts in customers' own words. The largest clusters are the requests that come up most often, and the quotations show how customers describe them. See Dimensions in Reports for every part of the page.

Cluster Scale shows each need's share of the records that answer Unmet Needs, and Dataset Scale shows its share of all the records in the Report. One review can state several needs, so the shares on Cluster Scale can add up to more than 100%. The Columns and Dimensions buttons on a cluster card show what lies behind a need, for example which platform or which Persona it comes from.

[Screenshot: The Unmet Needs tab of the Dimensions page with its summary and the largest clusters]

Read the Pain Points

Click the Pain Points tab. It has the same parts: the ring, the summary and the clusters, each with its records, share, summary and quotations. A pain point can be a breakdown, such as a crash or a failed payment, an obstacle that makes a task harder than it should be, or a source of dissatisfaction, such as a price that feels too high. Read the largest clusters first. Read the quotations to see what exactly fails, and open the Dimensions button of a cluster to see which other answers it comes with.

Cross the Findings with Ratings and Platforms

A count tells you how many customers raise something, and a cross tells you who they are. Open Tables in the menu of the Report, drag Unmet Needs into the table, then drag the rating column or the Platform column. Under every need, Kimola shows how its records split by rating or by store. Do the same with Pain Points. See Tables in Reports. To read the reviews behind one answer, open Content in Reports and filter by it, as described in Filter Records in Reports.

Example

In the budgeting app's Report, Unmet Needs lists shared budgets for couples with 410 records, export to a spreadsheet with 190 and dark mode with 35. Pain Points lists bank connection errors with 620 records, ahead of slow syncing. In Tables, most of the bank connection errors records come with 1-star and 2-star reviews, and most of the shared budgets for couples records come with 4-star and 5-star reviews. The first is a problem that costs the app ratings. The second is a wish of customers who already like it.

[Screenshot: A table grouped by Unmet Needs and then by the rating column]

Step 3: Find What Changed Recently

The counts of Step 2 show your feedback as a whole. Signals show what moved in it. Open Signals in the menu of the Report. Kimola tests every topic against every group of your reviews and lists the findings that hold up statistically in two lists, Differences and Trends. Kimola scores and ranks them with deterministic methods, so the same reviews always give the same signals in the same order, and an AI model writes the titles and texts afterwards, from numbers that are already computed. See Signals in Reports for every part of the page.

Trends is the list to read for a roadmap. It holds the topics whose mentions changed over time, measured as Change: the share of reviews that mention the topic in the latest periods against the periods before. A line above the list states the periods compared, for example "2026-W08–2026-W09 compared with 2026-W04–2026-W07 (by week)". A rising Trend shows a topic that grew lately, such as a problem that started with the latest release. A falling Trend shows whether a fix you shipped worked. Trends are built from the dates of your reviews, so they appear when the platform provides a date for each review, or when your file has a Date Column.

Differences is the list of topics that stand apart in one group of reviews, such as the reviews of one store. A problem that one store's reviews mention far more often than the other's shows which app needs the work first.

[Screenshot: The Trends tab of a Report with the compared periods above the first Change card]

Every signal is a card. Its title sums up the finding, the two percentages give the topic's share in the latest periods and in the periods before, and up to three quotes show what customers wrote. Why this is shown opens the evidence: what the group is compared with, the numbers behind the finding and how consistently it holds. Open in Tables opens the Report's Tables page with the signal's filters applied, so you can read the reviews behind it and cross them with your other columns and Dimensions.

Example

In the budgeting app's Report, a Trend card shows slow syncing in 15% of the reviews of the last two weeks and in 5% of the reviews of the four weeks before, and its quotes mention the latest update. A Difference card shows bank connection errors in 38% of the Android reviews and in 12% of the iOS reviews. The first moves a fix up the roadmap. The second says which app to fix first.

Give every card a verdict, so your team can tell the findings it already knew from the ones that need work: Known, New & important, Unimportant or Artifact. Click the same verdict again to take it back, and add a note to say why. Kimola hides cards marked Not supported by the verbatims or Volume driven unless you choose to show all signals, so the list starts with the findings that hold up. See Review Signals.

When the page says "No signal has enough evidence in this report", the Report has too little for the tests to tell a change from chance. More reviews give the tests more to work with, and so do descriptive columns such as the platform or the country. Trends also need reviews written across several periods. Create a new Report with a larger report size if you need signals.

A Report holds the reviews collected when you created it. To check how the next release is received, create a new Report from the same link, or follow the app with a Feed, which creates regular Reports and alerts. Feeds are not part of the Starter package.

Step 4: Plan Product Changes

The findings turn into work through an Action Plan: up to 12 actions that Kimola writes from the Report, each checked against the reviews before it is shown. Open Actions in the menu of the Report and click Create an action plan. The wizard asks four things, and Create an Action Plan describes every step of it.

The first step asks who the plan is for. Select your company's Profile or click New profile, type the organization's name and describe in a few words what it does, what it offers and whom it serves, for example "Develops a budgeting app for households, on iOS and Android". The description makes the actions specific to your product.

The second step, Where do you stand?, shows the side Kimola suggests from the Report. Reviews of your own app are feedback about your own product, so choose Our own offering: the plan then says what to fix, protect and build on. When Kimola isn't sure of its suggestion, it says "This is a guess, please check it." When a column of the Report names your apps or products, the step also lets you choose the values that name you.

[Screenshot: The Where do you stand? step with Our own offering chosen]

The third step asks what the plan is for. Choose Product development, the goal for what to build, change or fix in the product. A goal narrows the actions to its kind, while Balanced, which is selected when the step opens, covers what matters most of every kind. Under the goals, The situation lets you describe what you are facing in your own words, and Written in sets the language of the plan. The situation is optional, and it helps Kimola write actions that answer your question.

Example

For the budgeting app: "We have capacity for three larger items next quarter and must choose between shared budgets and a more stable bank connection."

Click Generate the Action Plan. Writing a plan takes about 5 to 7 minutes, and you can leave the page while it works.

[Screenshot: The What is the plan for? step with Product development chosen and the situation field filled in]

When the plan is ready, the page shows up to 12 action cards. Each card says what to change, for whom and when, who owns it, how confident Kimola is (High, Medium or Low) and How to See It Worked, with the evidence from your reviews behind it. Kimola drops the actions that its checks can't support, and a line under the cards says how many it dropped. See Actions in Reports for every part of a plan.

Read the actions next to the clusters of Step 2 and the signals of Step 3. An action that rests on a large Unmet Needs cluster or on a rising Trend has firmer ground than one that rests on a few records, and the confidence label of the card sums this up. Rate each action with a verdict: Useful, Already known, Too vague, Wrong or Not for us, with an optional note. The ratings tell your team which actions to take into the roadmap. See Rate Actions in an Action Plan.

When the evidence doesn't back any action firmly enough, Kimola doesn't write a plan and says "No action passed the checks this time". Click New plan and describe your situation, or choose another goal.

Note

When no action passes the checks, Kimola doesn't write a plan. Click New plan and describe your situation, or choose another goal.

[Screenshot: An Action Plan with its action cards, confidence labels and How to See It Worked]

What You Get

A product feedback Report gives you the following, all from your own reviews.

Themes with sentiment. Every review labeled with the themes it raises and its sentiment, with the number of reviews and the share behind each theme, on Overview and Content.

A ranked list of what customers miss. The Unmet Needs clusters, each with its number of records, its share, a summary and quotations in customers' own words.

A ranked list of what goes wrong. The Pain Points clusters, in the same form.

Who raises them. The needs and problems crossed with the rating, the platform and, when you add Personas, with the people who raise them.

What changed recently. Trends that show which topics grow or fade, and Differences that show which store or group stands apart.

An Action Plan. Up to 12 actions with an owner, a confidence level, a metric and the evidence behind each one, rated by your team.

To bring the findings to a roadmap meeting, export the Report as a PDF file or a PowerPoint file.

Next Steps

A Report shows the reviews of one moment. To follow the app as new reviews arrive, create a Feed. To follow the feedback of your own channels file by file, such as support tickets and survey exports, a Space in the Enterprise package keeps its themes, NPS and Signals current after every file.

To go deeper into one half of this guide, see How to Find Customer Pain Points. To read what a rival's customers miss and complain about, see How to Analyze Competitor Reviews, and to put the tickets of your support team next to the reviews, see How to Analyze Support Tickets. The collection steps for each store are in How to Scrape and Analyze App Store Reviews and How to Scrape and Analyze Google Play App Reviews. For the ways teams use Kimola on product feedback, see Product Feedback Analysis.

Was this article helpful?

Tell us about your thoughts and experiences regarding the article.