Skip to content
BENIBIX Learn

User Research Methods

Level 2 · Finding out from users

How to learn what people need before you design. Interviews with users and with the team, watching people at work, and diary studies.

Course contentsLesson 5 of 21

After this lesson you can

  • Pick a research method for a question
  • Run a user interview without leading
  • Say when a diary study fits

12 mincovers 6 glossary entries

Worth reading first: Service Design and Blueprints

How to learn what people need

User research is learning about the people who will use a product. It asks what they need, what they do now and what gets in the way. Five to eight interviews are often enough to see the main patterns. Research done before design is cheap. Research done after launch is a rescue.

Methods split two ways. Some tell you why, from a few people. Others tell you how many, from a lot of people. Some record what people say. Others record what they do. What people say and what they do are often different, so the best plans use both.

A user interview is a talk with one user, often 30 to 60 minutes. You ask about real past events, such as tell me about the last time you booked a trip. You do not ask would you use this, because people are kind and say yes to almost anything.

A stakeholder interview is a talk with the people who own the project. You ask about the goal, the limits and how success will be measured. It sounds like admin. It is how you find out on day one that the launch date cannot move.

Contextual inquiry means watching people work in their own place and asking as they go. You sit beside a nurse during a shift, not in a meeting room. You see the sticky notes on the screen and the paper list beside the keyboard. Nobody mentions those in an interview.

A diary study asks people to write short notes about using a product, for days or weeks. It catches what happens over time: the habit that fades after a week, or the task that only comes up on Fridays. A one hour visit would miss it.

The common mistake is to ask people what they want and build it. People are good at saying what bugs them and poor at designing the fix. Listen for the problem. The answer is your job.

Each method sits somewhere on two lines. Few people or many, and what they say or what they do.

Four ways to learn from people

MethodWhoWhat it catches
User interviewOne user, about an hourPast events and pain points
Stakeholder interviewThe project ownersGoals, limits and success
Contextual inquiryUsers in their own placeWorkarounds nobody mentions
Diary studyUsers over days or weeksHabits and change over time

Worked example

A school app learns from a parent

A team planned an app for school news. In 6 interviews, parents kept saying they missed messages about trips.

A 2 week diary study showed why. Notes came by email, text and paper bag, and nobody checked all three. The app's first job became one inbox.

The words for this lesson6

Check yourself

Why should an interview ask about a real past event, not a future one?

Finished this lesson?

Marking it complete also marks its 6 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.