Back to course materials

Week 3 Guide: Research & Empathy

Learning goal: gather honest evidence about the people you are designing for, then turn that evidence into insights that will steer your design.
Estimated study time: 2 to 3 hours across the week (roughly 45 minutes of teaching, 60 to 90 minutes of interviews, 30 minutes to map and write insights).
Evidence to upload: your interview notes, a completed empathy map, and 3 written insight statements.

The Real Problem This Solves

Most weak designs fail for one reason: the designer solved a problem they imagined instead of the problem people actually have. This week you replace guessing with evidence. You will talk to real people, watch how they behave, and record what you find. By Friday you will know things about your users that you could not have invented at your desk.

Running project this week. You keep working on your chosen track from Week 1. Whichever track you are on, the method below is the same. Only the questions change.

Key Ideas You Need First

1. Primary research versus secondary research

TypeWhat it isWhen to use it
PrimaryEvidence you collect yourself: interviews, watching people, photos of the real situation.To learn how your specific users actually behave and feel.
SecondaryEvidence others have already published: articles, existing products, standard measurements.To learn context fast and avoid repeating known mistakes.

This week is mostly primary research, backed by a little secondary research so you understand the field.

2. Ask about experiences, not opinions

Opinions are cheap and often wrong. Experiences are gold. Do not ask "Would you like a better desk organiser?" Everyone says yes, and it tells you nothing. Ask "Walk me through the last time your desk got in the way of your work." A real story reveals real needs.

3. Empathy is evidence, not sympathy

Empathy in design means understanding what a person does, says, thinks, and feels well enough to design for them accurately. It is a working tool, not a mood. You will capture it in an empathy map.

Tools And Materials Needed

Step-By-Step Walkthrough

  1. Confirm your user. Write one sentence naming who you are designing for. Example: "A design student who works from a small bedroom desk." If you cannot name them, you cannot research them.
  2. Do 15 minutes of secondary research. Search for how the problem is usually handled. Save 2 or 3 reference photos or notes. This stops you reinventing basics.
  3. Pick your questions. Open the Interview Question Starter Pack and choose 5 or 6 questions for your track. Favour "tell me about a time" questions over yes or no questions.
  4. Invite your interviewees. Keep it simple and honest. Say: "I am studying design and I am researching how people use their desk. Could I ask you a few questions for about 10 minutes? There are no right answers, I just want your real experience."
  5. Ask for consent. Before you start, say you will take written notes, that you will not share their name, and that they can skip any question. If you want to record audio, ask first and only record if they agree.
  6. Run the interview. Ask your question, then stay quiet and let them talk. When they mention a problem, ask "why?" or "what happened next?" Write down the exact words they use, not your summary of them.
  7. Watch as well as listen. If you can, ask them to show you. Photograph the real situation. What people do often differs from what they say.
  8. Fill in the Empathy Map. Straight after each interview, sort what you heard into four boxes: Says, Does, Thinks, Feels. Do this while it is fresh.
  9. Write 3 insight statements. Look across all your notes and complete these sentences: "I noticed that…", "I was surprised that…", "I wonder if…" These carry into Week 4 where you define the problem.

Demonstrated Example

Project: redesign a desk organiser for a creative learner (design track).

User named: a design student who works from a small, shared bedroom desk.

Interview extract (real words captured):

Three insight statements written from this:

  1. I noticed that the biggest cost is not mess, it is the setup time before work can begin.
  2. I was surprised that visibility matters more than storage. Hidden tools get forgotten.
  3. I wonder if a design that keeps the most used tools in sight would beat one that hides everything away.

Why this is strong: it uses the person's own words, separates behaviour from opinion, and produces insights that point somewhere without jumping to a solution.

Architecture and spatial track version. Named user: a community group that runs weekend creative sessions in a small hall. Instead of a desk photo, photograph the real space and its problems (poor light, no quiet corner, nowhere to store materials). Interview a group organiser about a specific recent session: what slowed it down, what people asked for, where they naturally gathered. Your empathy map records what organisers and attendees say, do, think, and feel about the space.

Your Task This Week

  1. Name your user in one sentence.
  2. Complete at least 2 interviews of about 10 minutes each.
  3. Fill in one empathy map that combines what you heard.
  4. Write your 3 insight statements.
  5. Include at least 1 photo of the real situation.

Submission Checklist

Upload itemPass standard
Interview notesNotes from 2 or more people, using their real words, not just your summary.
Empathy mapAll four boxes filled (Says, Does, Thinks, Feels) with evidence, not guesses.
3 insight statementsOne each for "I noticed", "I was surprised", "I wonder if", drawn from the research.
Situation photoAt least one photo of the real desk, toolkit, or space.

Assessment And Pass Criteria

Your Week 3 evidence passes when a reviewer can answer yes to all of these:

Common Mistakes

Extension Challenge

Do one extra interview with someone who is not your obvious user, an edge case. For the desk project, that could be someone with very little space or a physical limitation. For the learning pod, that could be a wheelchair user or a parent with a small child. Edge cases expose needs the average user hides, and designing for them usually improves the design for everyone.

When To Ask For Tutor Help

Book a tutor check-in this week if: Bring your raw notes to the session. A tutor can help you find the insight hiding inside them.

Back to course materials