Closing the feedback loop

There's a famous study in consumer research where participants were shown identical pairs of jeans and asked to choose their favourite. They overwhelmingly picked one pair and gave confident, detailed explanations for why — the stitching, the colour, the fabric quality. In reality, the jeans were identical.

Their stated reasons had nothing to do with their actual decision. This is the say/do gap, and it's everywhere in product feedback. Ask customers what they want and they'll tell you one thing.

Observe them — watch how they actually use your product, where they struggle, what they skip — and you'll learn something completely different. The best feedback strategies don't just ask. They observe.

Listening to customers is passive. Collecting feedback is active.

Good feedback collection means having dedicated channels: regular customer discovery calls, open feedback calendars where customers can book time directly with product, and customer success teams trained to capture insights systematically.

Every signal should be recorded in a central system and tagged against themes or roadmap items. When feedback is scattered across Slack messages, email threads, and meeting notes, it's not feedback — it's noise that happens to contain signal.

The most valuable feedback often comes not from what customers say, but from what they do. Session recordings, usage analytics, drop-off funnels, support ticket patterns — these tell you where the product is failing in ways that no survey ever will.

When a customer says "the product is fine" but their usage data shows they abandon a key workflow 40% of the time, the data is telling you the truth.

Build your feedback system around both qualitative input (what people tell you) and quantitative observation (what people actually do). The gap between the two is where the real insights live.

Not all feedback is equally useful. "Make it better" is low quality. "When I try to do X, I can't because Y, and that costs me Z" is high quality.

The quality of feedback you receive depends entirely on the questions you ask and the environment you create. Teach your customer-facing teams to dig beneath the surface — to ask "what are you trying to achieve?" instead of "what do you want us to build?"

When customers frame their needs as problems rather than solutions, the feedback becomes dramatically more useful for product decisions.

Feedback becomes actionable when it's aggregated and connected to product decisions. Individual requests are noise. Patterns across multiple customers are signal.

When the same problem surfaces from five different sources in different words, that's a roadmap item — not because one customer shouted loudest, but because the evidence supports it.

The discipline is in reading and reviewing every piece of feedback, linking it to existing themes, and letting the weight of evidence guide prioritisation rather than the volume of any single voice.

The most neglected step: telling customers what you did with their feedback. "You told us X was a problem. We built Y. Here's how it works."

This isn't just good manners — it reinforces the behaviour you want. Customers who see their input reflected in the product give better feedback next time. They invest more in the relationship. They become advocates.

And the opposite is equally true — customers who feel their feedback disappears into a void eventually stop giving it, and you lose the signal entirely. Closing the loop turns a one-time interaction into a compounding cycle of insight and improvement.