Unit 3: Understanding your users: the foundation of everything

Learning objectives

By the end of this unit, you should be able to describe the difference between what users say and what they need, plan and conduct a basic customer interview, and use AI tools to augment (not replace) your user research.

Video script

Reading material

The interview toolkit

Before you conduct a customer interview, you need to prepare. Here's a lightweight process that works.

Define what you're trying to learn. Not "understand the user" (too vague). Something specific like "understand how marketing managers currently track campaign performance and where the process breaks down." This focus keeps your interview productive.

Write an interview guide, not a script. An interview guide has 5-7 open-ended questions that you'll adapt based on the conversation. A script is rigid and prevents you from following interesting threads. Your questions should start broad ("Tell me about your role") and get specific ("Walk me through the last time you...").

Recruit the right participants. Talk to people who represent your target users, not just people who are easy to reach. If you're building for enterprise marketing managers, don't interview your friend who does social media for a startup. The context matters.

Record (with permission) and take light notes. Don't try to transcribe in real time. You'll miss the emotional cues and follow-up opportunities. Record the session, jot down key moments and follow-up questions, and do your detailed analysis later. This is where AI transcription tools genuinely help.

Debrief immediately after. Within 30 minutes of the interview, write down your top three takeaways and any surprises. Your first impressions are valuable, and they fade quickly.

What to listen for

The most useful signals in a customer interview are often indirect.

Workarounds. When a user describes a manual process they've built to compensate for a tool's limitations, that's a product opportunity. The more elaborate the workaround, the stronger the need.

Emotional language. When a user says "I hate" or "it drives me crazy" or "I dread," pay attention. Emotion signals intensity of need, which matters for prioritization.

Frequency and recency. Problems that happen daily are more valuable to solve than problems that happen quarterly. Ask "How often does this come up?" and "When was the last time?"

Contradictions. When a user says "I love this product" and then describes multiple workarounds and frustrations, the contradiction is more informative than either statement alone.

Using AI in user research

AI is a legitimate accelerator for user research when used correctly.

Transcription and summary. Use AI to transcribe recordings and generate summaries. Review the summaries for accuracy, AI sometimes misinterprets context, but this saves substantial time.

Cross-interview analysis. After 5-10 interviews, AI can identify recurring themes and patterns. This is useful as a starting point, but always validate the AI's themes against your own notes and impressions.

Interview preparation. Before an interview, use AI to pull together everything you know about that user from support tickets, usage data, and previous interactions. Walking in with context makes the conversation more productive.

Hypothesis generation. After analyzing interviews, use AI to generate hypotheses about user needs. Treat these as starting points for further validation, not as conclusions.

The line to hold: AI processes information. You build understanding. Those are different things, and the second one is what makes user research valuable.

Practical exercise

Exercise: Your first customer interview

Identify someone who uses a digital product regularly (a coworker, friend, or family member). The product doesn't matter; this is about practicing the technique.

Prepare a short interview guide (5 questions) following this structure:

1. Tell me about your role/life and how [product] fits into it.
2. Walk me through the last time you used [product]. What were you trying to accomplish?
3. What was the hardest part of that experience?
4. How do you currently work around that challenge?
5. If you could change one thing about how this works, what would it be and why?

Conduct a 15-20 minute interview. Record it if possible.

Afterward, write up your three biggest takeaways. Focus on: what surprised you, what gap did you notice between what they said and what they seemed to need, and what product opportunity would you explore based on this conversation?