← All posts

2026-04-15 · Greg Armstrong

What 300 feedback responses actually look like

Sarah runs a cafe. It's been open three years, has decent reviews, and does reasonable trade. Not spectacular, but not worrying either. She'd been meaning to collect customer feedback properly for a while -- not the Google reviews that trickle in, but something she could actually learn from. So she set up a short form on a QR code at the till. Three questions: a star rating, how likely they were to come back, and an open text box asking what they'd noticed about their visit.

Over about four months, she collected 300 responses.

Here's what that actually looks like.

The star ratings told her almost nothing new

Most were four stars. A cluster at five, a handful at three, very few below that. Pretty much what she expected. The distribution matched her Google rating. She already knew people thought the place was decent.

What she didn't know was why the three-star responses existed. They weren't obviously different visits -- they came from all times of day, all days of the week. The ratings alone gave her nothing to work with.

The open text was where it got interesting

She started reading through the comments. A lot of them were fine: "great coffee," "friendly staff," "nice spot." Useful to hear, not particularly actionable. But then she started noticing something.

The word "quiet" kept coming up.

Not always the same sentence. "Would be better if it was a bit quieter." "Lovely place but quite loud." "Hard to have a conversation." "Quieter than I expected, which was great." A few like that last one, actually -- people who were happy about the noise level. But the majority were mentioning it as a problem.

She hadn't noticed this in the Google reviews. One review mentioned noise, maybe two. It hadn't registered as a pattern. But across 90 open text responses, the word "quiet" or something near it appeared 17 times. That's one in five people with something to say bothering to mention the same thing.

She hadn't thought of the cafe as noisy. She's in it every day -- you stop hearing it. But she started paying attention differently, and she could see it: the music was maybe a bit loud, the hard floors bounced sound around, and on busy mornings it got genuinely difficult to talk.

What she did with it

She turned the music down. Not off -- just down. She added a couple of soft furnishings that had been on the "might do eventually" list. Small changes, not expensive.

Over the following two months, she collected another 80 responses. The word "quiet" still appeared, but about half as often. And the proportion of five-star ratings crept up a bit.

She couldn't prove causation. Maybe it was a coincidence. But it was the only thing she'd changed, and the signal had shifted.

The thing about patterns

Here's what she said when I asked her about it: "I thought I had a pretty good sense of what people thought. I was wrong about one specific thing, and I'd have kept being wrong about it indefinitely."

That's the thing about feedback patterns. A single comment about noise is easy to dismiss. Seventeen people mentioning it in their own words, unprompted, is harder to ignore. But you have to read all of them to find that. If you're collecting feedback and only skimming the responses, or only reading the ones from the worst-rated visits, you'll miss it.

300 responses is a lot to read carefully. Most business owners don't, not because they don't care, but because there's no obvious way to make sense of it all. You end up reading the ones that catch your eye and calling it done.

This is what Qria does with the open text: reads through all of it and tells you what keeps coming up. Not just word frequency, but the actual themes -- what people are noticing, what they're mentioning in slightly different ways across different visits. Sarah's 17 "quiet" mentions would have surfaced immediately rather than taking her an afternoon of careful reading to notice.

Most of it won't be surprising

To be clear: the majority of what Sarah found wasn't a revelation. Good coffee, nice staff, convenient location. Things she knew. Patterns that confirmed what she'd already guessed.

That's normal. Most feedback is confirmation. The value isn't in being constantly surprised -- it's in catching the one thing you're genuinely wrong about. The assumption that's been quietly costing you repeat customers for months while everything else looked fine.

Sarah almost missed it. She would have missed it if she'd only read the bad reviews, or only skimmed the open text, or decided that 300 responses was too many to bother reading properly. The pattern was there. It just needed someone to look.