User Research Methods
Before OXO redesigned its now-famous Good Grips vegetable peeler in 1990, the company's founder watched his wife struggle to peel potatoes because her arthritis made gripping a thin metal handle painful. That single observation, not a survey, not a focus group, but watching a real person struggle with a real object, led to the soft, fat, rubberized handle now copied by kitchen tools worldwide. That's the power of user research: it replaces guessing with evidence.
What You'll Learn
- The difference between qualitative and quantitative user research - Four core methods: interviews, contextual inquiry, surveys, and usability testing - Why designers research before they sketch, not just after - How to run a basic usability test on an object you already own
Qualitative vs. Quantitative Research
Quantitative research answers "how many" and "how much" using numbers: click rates, survey ratings, time-to-complete-a-task. Qualitative research answers "why" using words and observation: what a user says, how their face reacts, where they hesitate. Good industrial design uses both. Numbers might show that 40% of users abandon a task using a product, but only watching someone struggle in person reveals that they abandon it because the on/off switch is hidden underneath the device.
Four Core Methods
1. Interviews: One-on-one conversations where a designer asks open-ended questions like "Walk me through the last time you used this" rather than yes/no questions that limit what you learn. 2. Contextual inquiry: Watching someone use a product in their actual environment (their kitchen, their workshop, their commute) rather than in a sterile lab, because people behave differently once they're home and comfortable. 3. Surveys: Structured questionnaires sent to many people at once, useful for confirming a pattern seen in a smaller group of interviews, but weak at explaining why the pattern exists. 4. Usability testing: Giving someone a specific task ("open this jar," "assemble this shelf") and observing, without helping, exactly where they succeed, hesitate, or fail.
Henry Ford is often quoted (accurately or not) as saying that if he'd asked customers what they wanted, they'd have said 'a faster horse.' The lesson holds regardless of the quote's origin: people are good at describing problems they've experienced but often bad at inventing solutions. Good researchers dig into the underlying problem, not just the requested feature.
Research Happens Before Sketching, Not After
A common mistake is designing a product first and then testing it to confirm it's good. Professional industrial design teams, including firms like IDEO, front-load research at the very start of a project: they interview and observe real users before a single sketch is drawn, so the constraints they discover (a hand too weak to twist a cap, a shelf too high for a wheelchair user to reach) shape the design from day one instead of becoming expensive fixes after manufacturing has already begun.
A design team notices from survey data that 40% of users struggle to turn on a blender, but doesn't know why. What method should they use next to find out why?
Match each research method to its best description.
Terms
Definitions
Drag terms onto their definitions, or click a term then click a definition to match.
Why did OXO's Good Grips peeler redesign succeed, according to the lesson's opening story?
Run a 5-Minute Usability Test
Choose a household object (a can opener, a phone app, a backpack zipper). Ask a family member who hasn't used that exact one before to complete one specific task with it while you silently observe and take notes, without helping unless they're truly stuck. Record: how long it took, every moment of hesitation, and their comment afterward about what was confusing. Write a short redesign recommendation based on what you observed.
Want to keep learning?
Sign up for free to access the full curriculum — all subjects, all ages.
Start Learning Free