Customer research tips I actually use as a PM
Our reviewers evaluate writing services independently. Learn how we stay transparent, our methodology, and tell us about anything we missed.
Interviews are one input to qualitative research for product managers; I pair the stories with a clear plan for observation, synthesis, and follow-up.
When I need broader directional evidence, survey design for product managers helps me ask fewer, more decision-relevant questions instead of collecting noise.
Customer research isn't a phase you finish before building forever. It's how you stay honest. Here are the tips I'd keep on a sticky note.
1. Name the audience tightly
"Everyone who might buy" is not a segment. Pick a job-to-be-done and a context.
2. Hunt opportunities, not feature confirmations
Ask about past behavior and pain. Avoid pitching your solution in the first 20 minutes.
That evidence-first approach is the foundation of customer development; when a pattern suggests a new direction, use an opportunity assessment before committing roadmap capacity.
3. Mine reviews and support tickets
App stores, G2-type reviews, churn notes—patterns beat anecdotes if you tag themes.
4. Use research tools intentionally
Surveys, interview schedulers, session replay, heatmaps—each answers different questions. Don't collect data you won't analyze.
5. Watch competitors to learn alternatives—not to copy roadmaps
See how users work around problems today (including spreadsheets and interns).
6. Analyze like a product person
Quant shows what; qual shows why. Triangulate before you roadmap.
7. Surveys: short, specific, timed
One primary question per survey when you can. Incentives help; biased incentives hurt.
8. Observe real usage
Sit with customers (or recordings). Notice hesitations and workarounds your happy-path UX ignored.
9. Interview with a script—and break it
Standardize enough to compare; follow interesting threads. Record (with permission) so you're not drowning in your own notes.
10. Use public data carefully
Industry reports and search trends are context, not gospel.
11. Re-scope research per decision
A pricing change needs different evidence than a nav tweak. Match method to risk.
12. Incentives: fair, not leading
Gift cards OK; "we'll give you the feature if you like it" is not research.
13. Search listening
What do people type into Google / community forums about the problem? Language → positioning and IA.
14. Social listening
Themes and sentiment; still verify with direct research.
15. Feature feedback with intent
In-product prompts beat annual surveys for specific flows—don't interrupt critical tasks carelessly.
16. Experience ratings with follow-ups
A score without a "why" comment is half-blind.
17. Your email list / community is a panel
Use it for recruitment and longitudinal learning—not only launches.
My operating rules
- Write the decision you're informing before recruiting
- Store notes in a searchable place; tag by segment and job-to-be-done
- Share crisp insights with eng/design weekly—not a 40-page deck nobody reads
- Schedule research continuously (even 2 interviews/week beats quarterly panic)
My take
The goal isn't more quotes on slides. The goal is fewer wrong builds.
Level up discovery craft with the Product Manager Certification and the newsletter.
