Skip to content
Lesson 3 of 10beginner9 min read

Design Research

Design research is the disciplined effort to find out how people actually behave, so that design decisions rest on evidence rather than on the team's imagination.

01

Definition

Design research is the systematic gathering of evidence about people, their context and their behavior, in order to inform design decisions. It covers generative work, which explores what problems exist and how people currently cope, and evaluative work, which tests whether a specific design functions. Its methods range from interviews and contextual observation to diary studies, surveys, log analysis and usability testing. What makes it research rather than opinion collection is method: a stated question, a sample chosen deliberately, a procedure that limits the researcher's influence on the answer, and analysis that can be reviewed by someone else and challenged.

02

Why It Exists

Design research exists because designers are not their users and cannot become them by effort of will. Teams know their product's internal logic, use it daily, and share vocabulary that customers have never heard. That expertise makes it almost impossible to predict where a newcomer will falter. Research also exists to break the authority of opinion inside organizations, where the most senior view otherwise decides. Evidence about what a specific group of people did, watched by several members of the team, settles arguments that would otherwise go in circles. And it exists because the cost of discovering a fundamental mistake after launch is far higher than the cost of six conversations beforehand.

03

Examples

  • Interviewing ten warehouse staff about how they currently track stock before designing a replacement system.
  • Observing nurses on a ward and noticing that the chart is filled in later from memory, which no interview revealed.
  • A diary study tracking how families decide on weekly grocery purchases across a month.
  • Analyzing search queries inside a help center to find the questions the product itself fails to answer.
04

History

The methods were borrowed rather than invented. Anthropology and sociology contributed ethnographic observation and interviewing; psychology contributed experimental design and protocols for studying attention and memory; human factors research in wartime and postwar aviation and industry contributed systematic observation of operators and errors. Market research supplied surveys and segmentation, with different aims. In the 1990s these were assembled into a practitioner discipline for software. Mike Kuniavsky's Observing the User Experience codified field methods for product teams, and Nielsen Norman Group's publishing made evaluative technique widely available. Contextual inquiry, developed by Hugh Beyer and Karen Holtzblatt, established the practice of interviewing people while they work rather than afterward.

05

In Modern Design

Research today is spread across specialists and generalists. Dedicated researchers run complex, strategic and sensitive studies; designers and product managers run lighter evaluative sessions themselves. Research repositories attempt to keep findings usable past the sprint that produced them, which is a real problem, since most organizations rediscover the same insight repeatedly. Remote tools have made recruiting and observation cheaper and geographically broader, at the cost of context — you see a screen, not a desk, a ward, or a bus. Ethics and data protection have become explicit obligations: informed consent, purpose limitation, secure handling of recordings, and care when studying people in vulnerable situations.

06

Real-World Example

A team redesigning a benefits application assumed the main difficulty was the form's length. Sitting with applicants in a community center produced a different picture: people abandoned the form because a single question asked for an employer reference number they did not have and could not obtain without a phone call during working hours. The form's length was irrelevant to abandonment. No amount of layout improvement would have addressed it; the fix was to allow the field to be completed later and to explain where the number could be found. The finding was available only by watching people attempt the task with their own documents, in their own circumstances.

07

Key Principles

  • Start from a question you could be wrong about, not a conclusion you want supported.
  • Watch behavior where it happens; what people report doing and what they do differ systematically.
  • Ask about the past and the specific, not the hypothetical — predictions about future behavior are unreliable.
  • Small samples are fine for finding problems; they cannot tell you how common something is.
  • Recruit for relevant difference, including people who struggle, not for convenience.
  • Treat consent, privacy and the participant's dignity as part of method, not paperwork.

Why it matters

Research determines whose reality the product is built around. Without it, teams design for a confident, technically literate person who resembles themselves, and everyone else adapts or leaves. With it, the people who struggle become visible early enough to change something. Research also reduces the most expensive kind of waste, which is not a badly built feature but a well-built irrelevant one. Its limits should be stated honestly: research is interpretive, samples are small, participants perform for observers, and findings can be selected to support a decision already made. Knowing those limits is part of using it well, not a reason to skip it.

Then vs Now

Then

Methods were borrowed from anthropology, psychology and human factors, and studies were run in person, in labs or in the field, by specialists.

Now

Remote tools make recruiting and observation broad and cheap, designers run lighter studies themselves, and consent, privacy and finding reuse have become explicit obligations.

Try it yourself

Choose a routine task someone near you performs regularly — booking a shift, doing a weekly shop, logging expenses. Ask to watch them do it, for real, without helping. Before you start, write your prediction of the three hardest steps. While watching, note only what happens, not why you think it happens, and ask the question that begins tell me about the last time you did this. Afterward, compare your predictions against what you saw, and list every step you did not know existed. Those unknown steps are the value research adds, measured directly.

Test yourself

5 questions, one at a time

Answers are revealed at the end, so you can think without being nudged.

Sources

  • Observing the User Experience: A Practitioner's Guide to User Research — Mike Kuniavsky (2012) · Book
  • Contextual Design: Defining Customer-Centered Systems — Hugh Beyer and Karen Holtzblatt (1997) · Book
  • User research methods and guidance · Institution