# Qualitative vs quantitative customer feedback

> Quantitative feedback is feedback you can count, such as star ratings, the number of messages by type or the number of customers who asked for something. Qualitative feedback is the text customers write. Counts show how big a problem is; the words show what it is.

Source: https://escutaproduto.com/resources/qualitative-vs-quantitative-feedback
Last updated: 2026-10-09

## What is quantitative customer feedback?

Quantitative feedback is anything you can count or put on a scale. A star rating is quantitative: a 4 is a 4 regardless of who gave it. So is the number of bug messages this week, the number of customers who asked for an export format or the average rating across a product.

Counts are good at answering "how many?" and "how much?". They make trends visible, and they let you compare one period with another. They also flatten meaning, because two customers can give the same 2 rating for completely different reasons.

## What is qualitative customer feedback?

Qualitative feedback is the open text customers write in their own words. "The invoice PDF shows the wrong tax rate for Portugal" is qualitative. It contains a product, a place, a problem and an implied expectation that a number could never carry.

Qualitative feedback is good at answering "why?" and "what exactly?". It shows the words customers use for a problem, which helps you name features the way they do. It also surfaces problems you did not know existed, because customers describe what matters to them rather than answering the questions you chose.

## What is each one good for?

Use each type for the job it does best:

| Question | Quantitative helps with | Qualitative helps with |
| --- | --- | --- |
| How big is this problem? | Counting distinct customers who report it | Checking that the reports describe the same problem |
| Is the product getting better? | Average rating and bug counts over time | Reading what praise and complaints say now |
| What should we fix first? | Ranking by how many people are affected | Understanding how severe the problem feels |
| What words should we use? | Rarely helpful | Finding the vocabulary customers use |

Counts without text tell you that something is wrong, but not what to change. Text without counts can make one loud customer look like a trend.

## Why combine a rating with a written message?

The most useful feedback form pairs a number with a sentence. The Escuta Produto form offers an optional 1 to 5 star rating and a required message, so every item has both. The rating gives you a quick trend, and the message explains it.

Read the two together. For example, if 12 of 40 customers gave a rating of 2 this month, the count tells you the problem is wide. Reading those 12 messages tells you whether they describe one broken step or several unrelated irritations. In this example the numbers are invented to show the method, not a real result.

## How do you read counts without losing the story?

Counts can hide meaning, so use a simple routine:

1. **Start with the count.** Note how many items arrived and how many describe the same thing.
2. **Read a sample of the text.** Open the messages behind the biggest count, not just the first few.
3. **Name the pattern in your own words.** Write a short internal note such as "export drops archived projects" on the item.
4. **Count again.** Use the internal notes to count distinct customers, not repeated messages from one person.

Counting the notes rather than the raw messages is the step most teams skip, and it is what keeps one enthusiastic customer from distorting the numbers.

## What are the traps with each type?

Each type has a characteristic mistake:

- **Quantitative traps.** Averages hide spread. A rating average of 3 can mean everyone was lukewarm or that half loved the product and half hated it. Check the distribution, not just the mean.
- **Qualitative traps.** Vivid messages feel more representative than they are. A single detailed complaint can dominate a meeting, so tie every quote to a count before you act on it.
- **Mixed traps.** Treating the rating as a measure of the product, when it is a measure of one moment. A customer who rates a product after a failed export is reacting to that export.

## How do you use both in Escuta Produto?

Escuta Produto keeps the rating and the message on each item, and the inbox shows counts by type, the average rating and a 30-day chart. Use those counts to decide where to look, then read the messages behind them. The inbox has text search, so you can find every message that mentions the same word.

For analysis beyond the screen, export the product's feedback as UTF-8 CSV and count themes in a spreadsheet. Escuta Produto does not cluster or score sentiment for you, so the tagging and grouping are work you do with internal notes or the export. For how to turn those notes into decisions, read [how to triage customer feedback](/resources/how-to-triage-customer-feedback). For the rating and message fields in detail, see [what a feedback widget is](/resources/what-is-a-feedback-widget) and the [widget documentation](/docs/widget).

## Frequently asked questions

### What is the main difference between qualitative and quantitative feedback?

Quantitative feedback can be counted or scored, such as ratings and the number of customers who asked for something. Qualitative feedback is the open text customers write, which explains why and what exactly is wrong.

### Which kind of feedback should a small team collect first?

Collect both at once with a short form. A star rating gives you a quick number, and a required written message explains it. Adding a rating costs customers almost nothing and makes the messages easier to rank.

### Can you turn written feedback into numbers?

Yes, by counting distinct customers who describe the same problem. Write a short internal note for each theme, then count the notes. Count customers rather than messages so repeat writers do not inflate the total.

### Is a low average rating enough to decide what to fix?

No. An average can hide a split between very happy and very unhappy customers. Read the distribution and the messages behind the low ratings before you decide what to change.