Effective user interviews: The playbook I’d follow
Our reviewers evaluate writing services independently. Learn how we stay transparent, our methodology, and tell us about anything we missed.
Most PMs aren't formally trained to interview users. Then we wonder why research feels anecdotal. Here's the playbook I'd follow for effective user interviews.
Before: plan, source, screen, schedule
1. Plan
Write the decision this interview will inform. "Explore onboarding drop-off before we rebuild step 2" beats "chat with users."
Draft a guide: warm-up → context → deep dive → wrap. Keep it short enough to breathe.
2. Source
Existing customers, recent trials, support tickets, community, recruiting panels. Match the segment to the decision.
3. Screen
Five wrong users teach confidently wrong lessons. Screen for role, usage, and the pain you're studying.
4. Schedule
45–60 minutes. Record with permission. Invite a note-taker when you can—you'll listen better.
During: contextualize, dive, replicate
Contextualize
Explain purpose and consent. You're here to learn, not to pitch. Ask about their world before your UI.
Dive
Prefer stories over opinions:
- "Walk me through the last time you tried to…"
- "What happened next?"
- "What did you try before this tool?"
Avoid leading: "You'd love a dashboard that does X, right?"
Replicate
When they describe a workflow, ask them to show it (screen share) or narrate steps in order. Specificity > slogans.
Live note: watch for emotions, workarounds, and words they repeat.
After: retrospect and document
Retrospect
What surprised you? What hypothesis died? What needs a follow-up interview vs a metric check?
Document
One-pager per interview + a synthesis across n:
- Jobs / pains / triggers
- Verbatim gems
- Opportunity themes
- Confidence level (n is small—say so)
Share with eng/design like product ingredients, not a novel.
Mini example framing
If I were researching grocery delivery onboarding, I wouldn't ask "Do you like Instacart?" I'd ask how they planned last week's meals, where the order failed, and what made them abandon the cart.
Quality bar I hold
- Interviews change a decision or explicitly reduce uncertainty
- Insights are tagged to segments
- We don't invent a roadmap from two loud calls
- We pair qualitative with behavioral data when we can
My take
User interviews are a product skill, not a vibe session. Tight purpose, clean questions, ruthless notes, synthesis that ships.
Level up discovery craft with the Product Manager Certification. More field notes in the newsletter.
