user-interview

name	user-interview
description	Guide for conducting Torres-style story-based user interviews with bias mitigation and JTBD lens.

User Interview Guide

Discover opportunities through customer stories. Source: Torres (CDH), Kahneman, Christensen (JTBD).

Pre-Interview (Mandatory)

1. Run /bias-check before designing questions
2. Review current OST -- what are you trying to learn?
3. Design questions that are story-based and past-tense

Question Design Rules

ALWAYS Ask (story-based, past behavior)

• "Tell me about the last time you [tried to accomplish X]..."
• "Walk me through what happened when [situation]..."
• "What did you do when [problem occurred]?"
• "How did that make you feel?" (emotional dimension -- JTBD)
• "What did other people think about that?" (social dimension -- JTBD)

NEVER Ask (hypothetical, opinion, leading)

• "Would you use a feature that...?" (hypothetical)
• "Do you think X is a good idea?" (opinion)
• "Don't you find it frustrating when...?" (leading)
• "On a scale of 1-10, how important is...?" (abstract)
• "What features would you want?" (solution-space, not problem-space)

During Interview

• Listen for hiring/firing language (JTBD)
• Note emotional reactions (tone, hesitation, enthusiasm)
• Follow up on surprises -- "That's interesting, tell me more about..."
• Don't pitch or defend -- you're here to learn, not sell

Post-Interview Snapshot

Create immediately after each interview:

• 3-5 key quotes (verbatim)
• Opportunities identified (needs/pain points/desires)
• Surprises (things you didn't expect)
• JTBD dimensions observed (functional/emotional/social)
• Biases to watch for in interpretation

Output

• Update canvas/opportunities.yml with new evidence
• Update canvas/user-needs.yml
• Update canvas/jobs-to-be-done.yml
• Add snapshot to product-journal.md