Principles of UX / UI (Product Design): User Interviews (Script, Moderation, Synthesis)

User Interviews (Script, Moderation, Synthesis)

Portfolio-Ready Study Guide: User Interviews (Script, Moderation, Synthesis)

What This Is

User interviews are structured conversations with real users to uncover their needs, pain points, and behaviors. They’re the backbone of user-centered design—helping you build products that solve real problems, not just look pretty. For example, a hospital redesigned its patient portal after interviews revealed that users struggled to find lab results, leading to a 40% drop in support calls. Without interviews, you’re designing in the dark.

Key Terms & Principles

• Semi-structured interview: A flexible script with core questions but room for follow-ups. Example: Asking, “Walk me through the last time you booked a doctor’s appointment online,” then probing deeper based on their answer.
• Leading question: A question that nudges the user toward a specific answer (bad!). Example: “Don’t you think this checkout button is too small?” (❌) vs. “How do you feel about the size of this button?” (✅).
• Affinity diagramming: Grouping interview notes into themes to spot patterns. Example: Sticky notes with quotes like “I hate typing my card info every time” clustered under “Payment Frustration.”
• Jakob’s Law: Users expect your product to work like others they’ve used. Example: Placing the “Submit” button on the right (like most forms) instead of the left.
• Hawthorne Effect: Users behave differently when they know they’re being observed. Example: A user might over-explain their actions in an interview but abandon a task in a real-world usability test.
• Empathy map: A visual tool to organize what users say, think, feel, and do. Example: A quadrant with “I’m frustrated” (feel) and “I keep clicking the wrong tab” (do).
• Saturation: The point where new interviews stop revealing new insights. Example: After 8–12 interviews, you start hearing the same pain points.
• Think-aloud protocol: Asking users to verbalize their thoughts while completing a task. Example: “As you book this flight, tell me what you’re looking for and any questions you have.”
• Confirmation bias: Focusing only on data that supports your assumptions. Example: Ignoring a user who says “I love this feature” because you expected them to hate it.
• Recruitment screener: A short survey to filter participants for interviews. Example: “Do you use mobile banking at least once a week?” to ensure relevant users.
• Non-verbal cues: Body language, tone, or pauses that reveal unspoken feelings. Example: A user sighs while saying “Yeah, this is fine”—likely a pain point.
• Synthesis vs. Analysis: Synthesis = combining insights into themes; analysis = interpreting what those themes mean. Example: “3 users struggled with X” (analysis) → “Users need clearer error messages” (synthesis).

Step-by-Step Process Flow

1. Plan: Define Goals & Script

• Action: Write a 1-page interview guide in Figma or Google Docs with:
• Goal: “Understand why users abandon their cart.”
• 3–5 key questions: Open-ended, non-leading (e.g., “Tell me about the last time you didn’t complete a purchase.”).
• Follow-up prompts: “What happened next?”, “How did that make you feel?”
• Pro tip: Share the script with a teammate to check for leading questions.

2. Recruit: Find the Right Users

• Action: Use a screener survey (Typeform/Google Forms) to filter participants. Example:
• “How often do you shop online?” (Daily/Weekly/Monthly)
• “What’s your biggest frustration with online checkout?” (Open-ended)
• Tools: User Interviews, Respondent, or Craigslist (for guerilla testing).
• ⚠️ Trap: Avoid friends/family—they’ll sugarcoat feedback.

3. Moderate: Run the Interview

• Action: Record the session (Zoom/QuickTime) and take timestamped notes (e.g., “03:15 – User hesitates before clicking ‘Pay’”).
• Script flow:
• Warm-up: “Tell me about your experience with online shopping.”
• Context: “Walk me through the last time you bought something online.”
• Probe: “You mentioned X—can you tell me more about that?”
• Wrap-up: “Is there anything else you’d like to share?”
• Pro tip: Stay silent after questions to let users fill the gap.

4. Synthesize: Find Patterns

• Action: Use affinity diagramming in Miro or sticky notes:
• Write 1 quote per sticky note (e.g., “I hate re-entering my address every time”).
• Group similar quotes into themes (e.g., “Checkout Friction”).
• Label themes with insights (e.g., “Users want saved payment info”).
• Pro tip: Color-code by user type (e.g., new vs. returning customers).

5. Share: Present Insights

• Action: Create a 1-page summary in Figma with:
• Key findings (bullet points).
• User quotes (with photos/avatars for empathy).
• Recommendations (e.g., “Add a ‘Save for Later’ button”).
• Example:
  ![Figma mockup: A slide with “Top 3 Pain Points” and quotes like “I don’t trust this site with my card info.”]

Common Mistakes

Design Interview / Portfolio Tips

What Interviewers Look For

1. Script quality: Do your questions avoid leading language? Example:
2. ❌ “Why do you dislike this feature?” (assumes dislike)
3. ✅ “How do you feel about this feature?” (open-ended)
4. Synthesis skills: Can you turn raw data into themes? Show a before/after in your portfolio:
5. Before: A wall of sticky notes.
6. After: A clean Miro board with labeled themes.
7. Empathy: Do you humanize users? Include quotes + photos in case studies (e.g., “Meet Sarah, a busy mom who struggles with X”).
8. Impact: Did your interviews change the design? Example:
9. “After 8 interviews, we learned users wanted X, so we added Y, reducing drop-off by 20%.”

Tricky Distinctions to Know

• User Interview vs. Usability Test:
• Interview: Uncover problems (e.g., “Why do you abandon carts?”).
• Usability Test: Observe task completion (e.g., “Can you book a flight?”).
• Affinity Diagram vs. Journey Map:
• Affinity Diagram: Groups qualitative data (quotes, observations).
• Journey Map: Visualizes steps + emotions in a user’s process.

Quick Check Questions

1. Scenario: A stakeholder says, “We need to add a chatbot to the homepage—users love chatbots!” How do you respond?

2. Answer: “Let’s validate that with users first. I’ll add a question to our interview script: ‘How do you prefer to get help when using this site?’ If 80% say chatbots, we’ll prioritize it.” (Key principle: Avoid assumptions; test with users.)

3. Scenario: During an interview, a user says, “This feature is fine,” but they keep clicking the wrong button. What do you do?

4. Answer: “You seem to be struggling—what’s going through your mind right now?” (Key principle: Probe non-verbal cues.)

5. Scenario: Your team wants to skip user interviews because “we already know our users.” How do you push back?

6. Answer: “Even if we think we know them, interviews often reveal surprises. Let’s do 5 quick interviews—if nothing new comes up, we’ll stop.” (Key principle: Saturation is the goal, not perfection.)

Last-Minute Cram Sheet

1. Semi-structured interviews = Core questions + follow-ups.
2. Leading questions = Bad (e.g., “Don’t you hate this?”).
3. Affinity diagramming = Grouping quotes into themes (use Miro/sticky notes).
4. Saturation = Stop interviewing when no new insights emerge (~8–12 users).
5. Think-aloud protocol = Users verbalize thoughts while completing tasks.
6. Hawthorne Effect = Users behave differently when observed.
7. Jakob’s Law = Users expect your product to work like others.
8. ⚠️ User interviews ≠ usability tests (interviews = problems; tests = task completion).
9. Non-verbal cues = Sighs, pauses, hesitations (probe these!).
10. Recruitment screener = Filter for target users (e.g., “Do you use this feature?”).