Interview Script·45 min·10 questions
Discovering why distributed teams abandon coordination tools despite initial enthusiasm
You're seeing a puzzling pattern in your user data: some distributed teams become power users of your coordination tool, while others start strong but quietly abandon it within months. You have engagement metrics and churn data, but you can't pinpoint what separates the teams that make it work from those that drift away. The surface-level feedback doesn't explain why similar-sized remote teams have such different outcomes.
Why standard questions fail here
Direct questions about tool preferences miss the critical moments when coordination actually breaks down. This script reconstructs specific coordination failures by anchoring in recent breakdowns, then works backward to uncover the cascade of communication choices that led there. Rather than asking what tools they prefer, you'll map the exact sequence from async attempt to sync escalation to understand when and why their coordination system fails them.
Sample Questions
Grounded in The Mom Test and Jobs-to-be-Done.
JTBD: Establish context for the job story and team dynamics before diving into problems
Let them paint the picture naturally - don't interrupt with clarifying questions until they finish
- How long have you all been working together remotely?
- What time zones are you spread across?
- Generic team descriptions without specifics about actual collaboration patterns
Mom Test principle: Ask about specific past behavior rather than general opinions about coordination
Use the critical incident technique - get them to relive the specific moment step-by-step
- What was supposed to happen versus what actually happened?
- How did you first realize something was wrong?
- Who else was affected by this breakdown?
- Vague generalizations like 'communication is always hard' instead of specific incidents
JTBD: Understand current workarounds and job performance - what solutions they hired to resolve coordination breakdowns
Probe for the sequence of actions they took, not just the end result
- How long did it take to get everyone back on track?
- What would you do differently if it happened again?
- Hypothetical responses about what they 'would normally do' instead of what they actually did
JTBD frequency analysis: Understand how often the core job needs to be done
Ask for specific timeframes and examples rather than accepting vague estimates
- Can you give me another example from the past month?
- What patterns do you notice in when these happen?
- Generic frequency claims without specific examples to back them up
JTBD: Map the entire job workflow to understand all the moments where coordination tools get hired
Use process mapping - ask them to describe each handoff point and decision moment
- Where in that process do things typically go sideways?
- What tools or methods do you use at each step?
- Idealized process descriptions rather than messy reality of how work actually flows
JTBD success story analysis: Understand what successful job performance looks like
Contrast technique - compare successful vs failed coordination to identify key variables
- What specifically did you do differently that time?
- What tools or processes were most critical to that success?
- Attribution to team chemistry rather than specific processes or tools
Get your user interview script
Generate a complete interview guide tailored to your specific product and audience — with rationale, techniques, and follow-up prompts for every question.
Create free account & generate