Learning from Users

Introduction

Designers are not the users. What seems obvious to you may confuse others. The cure is to ask and watch real people. You do not need a lab or a budget, only curiosity, a few willing people and good questions.

Why research?

• To avoid building something nobody needs
• To find out how people do things today, and what frustrates them
• To discover differences between what people say and what they do
• To replace opinions in meetings with evidence

The user interview

An interview is a conversation with a purpose. Keep it short, such as 20 to 30 minutes.

Prepare:

1. A clear learning goal, such as "How do people decide what to cook for dinner?"
2. Who to talk to, from your real target group. Three to six people can already show patterns.
3. A short list of open questions.
4. Consent: explain why you are talking, how notes will be used and that they can stop at any time. Protect their privacy.

During:

• Start with easy background questions.
• Ask about real past behaviour, not predictions: "Tell me about the last time you..." beats "Would you use...?"
• Use follow-ups: "Why?" "Can you show me?" "What happened next?"
• Listen more than you talk, and be comfortable with silence.
• Note exact words, and what people do as well as say.

Avoid leading questions

How you ask changes the answer.

• Leading: "Don't you find the checkout confusing?" The question suggests the answer.
• Neutral: "How did you find the checkout?"
• Closed: "Do you like this?" gives a yes or no.
• Open: "What do you think of this?" invites detail.

Also avoid asking people to design the solution ("What feature should we add?"). People are good at describing problems, and poor at predicting what will work.

Other ways to learn

• Observation: watch people do the task in their own setting.
• Surveys: reach more people with simple questions, best for measuring how common something is. Short surveys with clear questions get better answers.
• Existing information: support emails, reviews and search terms show real problems.
• Analytics: numbers show what people do. Interviews show why.

Biases to watch

• Confirmation bias: noticing only evidence that supports your idea
• Politeness: people tell you what you want to hear
• Sampling bias: talking only to friends or enthusiasts
• Small sample over-reach: treating three interviews as proof for everyone

State findings carefully: "Four of five participants did X" rather than "users do X".

From notes to insights

1. Collect the observations: quotes and behaviours, on separate notes.
2. Group similar ones together, and look for patterns.
3. Write insights: short statements of what you learned and why it matters. Example: "People plan dinner on the way home, so they need quick decisions, not long recipes."
4. Frame the problem: "How might we help people decide what to cook in the shop?"

Personas are descriptions of typical users, useful when they are based on real research and kept simple. Invented personas based on guesses can mislead.

Be ethical

Get consent, protect identities, store notes securely, thank people and never pressure them. Do not collect more personal information than you need.

Try it yourself

Interview two people about how they do a task you are curious about. Use five open questions about the last time they did it. Write three observations and one insight, and note one place where you caught yourself asking a leading question.

Summary

• Research replaces guesses with evidence, and a few interviews can already show patterns.
• Ask open, neutral questions about real past behaviour, and listen more than you talk.
• Group notes into insights, state findings carefully and treat participants ethically.