Skip to main content
Research interviews require a different kind of attention than sales calls. You need to listen more than you talk, catch themes as they emerge, and avoid leading the participant toward the answers you want to hear. StageWhisper helps with the discipline side: keeping you in listening mode and flagging the moments that matter for your research goals.

​
The setup

User research Playbook: 
I'm conducting a user research interview about our onboarding experience.

My role: listen, probe, and understand. I should be talking less than 30% of the time.

Watch for:
- Moments where the participant describes their actual behavior vs. what they think I want to hear
- Emotional reactions: frustration, confusion, delight, surprise
- Workarounds they've built (signals of unmet needs)
- Assumptions I'm making that I haven't validated
- When they mention other tools, competitors, or alternatives

Alert me when:
- I ask a leading question instead of an open one
- I interrupt or finish their sentence
- I start explaining or defending instead of exploring
- They describe a pain point I should probe deeper
- They say something that contradicts our current assumptions
- I've been talking too long

Checklist:
- First impression of onboarding
- Where they got stuck
- What they tried before finding us
- Whether they'd recommend it
- Unmet needs or wishes

​
During the interview

Research Playbooks tend to generate different signals than sales ones. Instead of coaching you to pitch or close, they keep you honest about research hygiene:
  • If you ask “Don’t you think the onboarding is intuitive?” the AI flags it as a leading question and suggests a neutral alternative.
  • If the participant describes a workaround, you get a green signal to explore what need that workaround fills.
  • If you start explaining how a feature works instead of asking them to describe their experience, you get an alert.
The talking-time awareness is useful. When you’ve been explaining for a while, the signal reminds you to hand the conversation back.

​
After the interview

The transcript becomes your research artifact. Signals mark the key moments:
  • Where the participant expressed frustration or confusion
  • Where they described unexpected behaviors
  • Where your questions may have led them
You can review these moments, pull quotes for your research report, and see your checklist coverage to know if you got the data you needed.

​
Running multiple interviews

When you use the same Playbook across multiple research interviews, you build a consistent dataset. Each session transcript has the same structure, the same checklist topics tracked, and the same types of signals. This makes synthesis across interviews easier than working from unstructured notes.

​
Customer feedback calls

The same approach works for ongoing customer feedback conversations, support escalation calls, or quarterly business reviews. Adjust the Playbook to focus on the outcomes you need: 
I'm on a quarterly review call with a key account.

Watch for:
- Features they use heavily vs. ones they've stopped using
- Upcoming needs or changes in their team/workflow
- Satisfaction signals and frustration signals
- Competitive mentions
- Expansion opportunities

Alert me when:
- They mention something that sounds like churn risk
- They describe a need we could solve with an existing feature they don't know about
- I miss asking about their roadmap or upcoming changes