If the goal is useful product feedback at scale, I’d use all three—but for different jobs:
| Method | Best for | Scale | Depth | Main weakness |
|---|
| Surveys | Quantifying satisfaction, identifying patterns, prioritizing issues | ⭐⭐⭐⭐⭐ | ⭐⭐ | Shallow; response bias |
| Reviews | Understanding spontaneous sentiment and recurring complaints | ⭐⭐⭐⭐ | ⭐⭐⭐ | Skewed toward very happy/unhappy users |
| Post-purchase interviews | Discovering why people behave or feel a certain way | ⭐⭐ | ⭐⭐⭐⭐⭐ | Expensive and time-consuming |
A strong feedback system
1. Surveys = your measurement layer
- Send a short survey after the customer has had enough time to use the product.
- Ask 1–3 core questions, e.g. satisfaction, biggest problem, and desired improvement.
- Use quantitative questions to spot trends, then an open-text question for context.
2. Reviews = your always-on listening layer
- Monitor reviews for recurring themes.
- Categorize feedback into things like quality, usability, price, delivery, missing features, support.
- Don't just count mentions—look for severity + frequency + customer impact.
3. Interviews = your discovery layer
- Recruit a small, deliberately varied sample from survey respondents.
- Interview users who represent different behaviors—not just your biggest fans.
- Ask about what they actually did, rather than “Would you use feature X?”
The key is connecting them
A useful funnel is:
Reviews + surveys → identify patterns → interviews → understand causes → product changes → survey again
That gives you scale without sacrificing depth.
If I had to choose only one: surveys for an established product, interviews for discovering what to build next, and reviews as a complementary passive signal.
