Interview Script·45 min·11 questions

Understanding why solo users avoid teammate invites despite active collaboration tools

You have users actively working in your product but they're completely ignoring the team collaboration features. The usage data shows they're engaged with core functionality, yet invitation rates remain at zero — suggesting something specific is blocking them from bringing teammates into their workflow.

Why standard questions fail here

Direct questions about collaboration preferences often trigger socially acceptable responses about 'working independently' or 'not needing help.' This script reconstructs their actual work patterns and decision moments, anchoring in specific instances when they might have considered inviting someone but chose not to, revealing the real friction points behind their solo usage.

Sample Questions

Grounded in The Mom Test and Jobs-to-be-Done.

Q1 Can you tell me about your role and what your typical workday looks like?
Why ask this?

JTBD: Establish job context and daily workflow to understand where collaboration might fit

Technique

Listen for workflow patterns and pain points - don't interrupt their natural flow of explanation

Follow-up Prompts
  • What tools do you use most during your day?
  • Walk me through what yesterday looked like for you
Watch out for
  • Generic job descriptions without specific daily activities
Q2 Tell me about the last time you used our product - walk me through exactly what you did.
Why ask this?

Mom Test principle: Ask about specific past behavior rather than general usage patterns

Technique

Use the 'tell me more' technique - keep asking for more specific details about their actual actions

Follow-up Prompts
  • What happened right before you opened the product?
  • What were you trying to accomplish?
  • How did you feel when you finished that session?
Watch out for
  • Vague descriptions like 'I use it for projects' without specific examples
Q3 What's the hardest part about the work you do in our product?
Why ask this?

JTBD: Identify struggling moments where collaboration features might provide value

Technique

Use the laddering technique - ask 'why is that hard?' and 'what makes that challenging?' to dig deeper

Follow-up Prompts
  • Can you give me an example of when that was particularly frustrating?
  • What workarounds have you tried?
  • How much time does that difficulty typically cost you?
Watch out for
  • Surface complaints without emotional weight or specific consequences
Q4 When you're stuck or need input on something in our product, what do you currently do?
Why ask this?

JTBD: Understand existing collaboration 'jobs' and current solutions they hire

Technique

Probe for actual behavior sequences - get them to replay the last time this happened step by step

Follow-up Prompts
  • Tell me about the last time that happened
  • How long did it take to get the help you needed?
  • What was frustrating about that process?
Watch out for
  • Hypothetical responses like 'I would probably ask someone' instead of actual past examples
Q5 Walk me through how you typically work with colleagues or teammates on projects.
Why ask this?

Mom Test: Understanding actual collaboration behavior patterns outside the product

Technique

Ask for a specific recent project - get them to replay the collaboration timeline

Follow-up Prompts
  • What tools do you use to share work with others?
  • When do you involve other people in your work?
  • What's the most effective collaboration you've had recently?
Watch out for
  • Generic statements about 'good teamwork' without specific interaction examples
Q6 Have you ever wanted to show someone else what you were working on in our product?
Why ask this?

JTBD: Identify potential collaboration jobs-to-be-done that aren't being served

Technique

If yes, use story-gathering: get the complete narrative of what happened and why they wanted to share

Follow-up Prompts
  • Tell me about that situation
  • What did you end up doing instead?
  • How did that work out for you?
Watch out for
  • Quick 'yes' or 'no' without exploring the underlying situation and emotions

Get your feature adoption 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