User-centred Research Methods | A2.1

Students must be able toExplain how developing empathy with users through an understanding of their needs and carrying out tasks in a specified environment leads to better design.

User-Centred Design (UCD) is an approach that places the needs, wants and limitations of end-users at the centre of the design process from start to finish. Rather than developing a product in isolation and then hoping users will adapt to it, UCD asks designers to stay in contact with real users. That contact happens before a concept exists, during development, and again after launch.

The term comes from the American cognitive scientist Donald Norman, who developed it in the 1980s. It became widely known through two of his books: User-Centered System Design (1986) and The Psychology of Everyday Things (1988), later renamed The Design of Everyday Things. Norman's complaint was straightforward. Too many products were difficult to use, and too many design changes were made for the sake of style rather than for the person holding the object.

The foundation of UCD is empathy, which means understanding a user's experience as if you were that user. Empathy is not guesswork. You build it through direct contact: watching people work, listening to them describe what frustrates them, and spending time in their environment. A designer who has spent an afternoon watching patients in a hospital waiting room understands that space in a way no second-hand description can match.

Three types of understanding drive UCD:

• Needs: what the user must be able to do. Functional, and usually non-negotiable.
• Wants: what the user would prefer, such as extra features, appearance or convenience. These can be traded off.
• Limitations: the physical, mental, cultural and technological constraints that define what is possible for this user in this situation.

When designers understand all three, they avoid two costly mistakes. The first is a product with too few features, which fails to meet real needs. The second is a product with too many, which adds cost and complexity without meeting any need at all. Extra functions are often cheap to add, so the temptation is real, but the cost appears later as confusion.

Electronic interfaces show this pattern clearly. Microwave ovens, television remotes and smartphones frequently carry far more functions than most owners will ever use. The extra functions crowd out the two or three that people actually need. In a microwave, that confusion is merely annoying. In medical or industrial equipment, the same confusion becomes dangerous.

Products built for the general public are designed the other way around. An ATM has a standardised layout, a large display and a deliberately small set of functions, because its users cannot be trained beforehand and usually have nobody to ask for help.

The environment matters too. Most electronic products state a temperature range they can safely operate in, and many need shielding from strong magnetic fields. A greater risk comes from users applying a normal function in an abnormal situation. Texting while walking is the everyday example. More than a third of young people report having had an accident while doing it.

Research by Jacob Schmookler (1962) found that user need, not technological opportunity, is the most powerful driver of successful innovation.

IDEO's Shopping Cart

A supermarket cart redesign that demonstrates UCD throughout

Read spotlight →

Students must be able toExplain the five stages of UCD and the advantages and disadvantages of UCD when designing products that meet the requirements of a diverse range of user needs and capabilities.

The UCD process is usually structured around five stages. In each one, users are involved directly rather than being treated as passive recipients at the end. Notice that different specialists lead different stages.

1. Research: Understand the user, the task and the environment through field research, interviews and observation. This stage is often led by psychologists, ethnographers and anthropologists, who record how people carry out tasks. The outputs are personas, scenarios and specifications built on real user needs.
2. Concept: Generate and evaluate ideas against those needs. Industrial designers, psychologists and engineers usually work together here. Concepts are shown to users before anyone invests in detailed design.
3. Design: Develop drawings and models, then prototypes at increasing levels of fidelity. Scale, appearance and feel can all be judged at this point, and changes are still quick and cheap to make.
4. Implementation: Build or manufacture the product. Formal user testing now runs with a wider range of end users than before, often guided by psychologists. Findings feed back into the design and into the instruction manual.
5. Launch: Release the product and keep collecting data. Customer feedback and post-launch questionnaires inform the next version.

Henry Petroski's book Invention by Design gives a good example of how careful companies are at the launch stage. When the easy-opening stay-on-tab can top appeared in the 1970s, it replaced a tab that shoppers pulled off and threw away. Because this was a genuine change in behaviour, beverage companies ran consumer studies first to check that people would accept it. Early cans were even printed with instructions explaining how to open the top.

Advantages of UCD:

• Reduces costly late-stage redesigns by catching usability problems early.
• Produces products that feel intuitive, reducing training time and user error.
• Supports accessibility by identifying the needs of diverse users before production.
• Strengthens market competitiveness by aligning features with genuine user demand.

Disadvantages of UCD:

• Careful user research at every stage takes time and money, and most of that cost falls early in the project.
• Users cannot always describe a need they have never experienced. Research has to be interpreted, not simply obeyed.
• User feedback often conflicts. Deciding which findings to act on is a genuine judgement, and it can shift the focus of the project enough that earlier stages have to be repeated.
• Relying too heavily on user feedback tends to produce small improvements rather than breakthroughs.
• Coordinating several disciplines and continuous user involvement makes the project harder to manage.

Students must be able toExplain how different disciplines contribute to a better understanding of target user, task and environment when designing to meet the needs of specific target users.

No single discipline can meet all the needs of a diverse user population. A psychologist understands how people perceive and decide. An engineer understands what is structurally possible. A sociologist understands how culture shapes behaviour. An anthropologist understands how different communities live and work. A UCD team brings these disciplines together so that design decisions are informed by the full complexity of human experience.

Don Norman argues that good design only emerges when the product development process includes the concerns and the expertise of the target user and of the teams who manufacture, distribute, maintain and market the product. This is a real break from traditional practice, where designs were developed largely in isolation. Adriana Chammas, Manuela Quaresma and Claudia Mont'Alvão make the same point in A Closer Look at the User Centred Design (2015), writing that UCD "encourages the use of multidisciplinary expertise in order to provide creative and collaborative ideas between team members, benefiting the project with different perspectives and skills".

Five benefits of a multidisciplinary team:

• Enhanced creativity and innovation: different fields of knowledge produce ideas nobody in the room would have reached alone.
• Improved problem-solving: attacking a challenge from several angles leads to more complete solutions.
• Faster development cycles: errors are caught earlier and fewer dead-end investigations are pursued.
• Improved product quality: every specialist refines the part of the solution they know best.
• Greater market understanding: a wider range of user and market insight makes acceptance more likely.

These benefits come at a price. Several perspectives and several data sources are harder to manage, and they usually produce more design iterations before the team agrees.

Typical contributors to a UCD team include:

• Psychologists: study behaviour, cognition and perception to explain how users process information and make decisions.
• Sociologists: read cultural norms, group dynamics and social behaviour, so that a design works across different social groups.
• Anthropologists: conduct field research and interviews to reveal the cultural influences that shape user behaviour.
• Designers and visual artists: handle aesthetics, visual communication and emotional response, which shape a customer's first impression of the product.
• Materials and manufacturing engineers: select materials and processes, and balance durability against tooling and production cost.
• Software, hardware and systems engineers: turn concepts into working solutions while managing scalability, security and performance.
• Human factors engineers: apply ergonomics to reduce strain and injury and improve comfort and safety.
• Data analysts: find patterns across large sets of test, survey and focus group data that qualitative research alone would miss.
• Marketing and business experts: align design decisions with market trends, brand identity and commercial goals.
• Environmental scientists: assess ecological impact across the life cycle, covering materials, energy use, end of life and regulatory standards.

Case study: Mercury spacesuit. When NASA developed one of the earliest spacesuits in the late 1950s, the engineering team was joined by experts from biology, medicine, design and materials science, and everyone was asked to propose ideas freely. The most effective concept came from a biologist rather than an engineer.

Their collaboration produced solutions a single-discipline team would probably have missed:

• Temperature control: biologists and engineers together developed an outer shell of aluminium-coated nylon, which held body temperature steady against extreme external temperatures.
• Life support: biologists, medical experts and engineers built a dependable closed-loop breathing system around the physiological needs of the astronaut.
• Data management: a "biomed flap" allowed biomedical sensors to connect to the spacecraft's telemetry system.
• Durability and safety: materials scientists and engineers produced a suit that resisted space debris as well as temperature extremes.

Students must be able toExplain how user-centred research methods (field research, task analysis, user observation, interviews, surveys and focus groups) can be used to discover the true nature of a user population.

Each research method collects a different kind of information. Choose a method for what you need to know, not for how easy it is to run. All six generate one of two broad categories of data:

• Qualitative data: non-numerical. It describes qualities, feelings, opinions and behaviours, and it answers why and how. Harder to compare across large samples, but it reveals the reasoning behind what people do.
• Quantitative data: numerical. It can be counted, measured and analysed statistically, and it answers how many and how often. Easy to compare at scale, but it does not explain the reasons behind the pattern.

Field research. Observing users in their real environment, such as a kitchen, a factory or a school. It uncovers behaviour shaped by cultural norms, physical habits and surroundings, none of which users would think to mention in an interview. The risk is that observers may change the behaviour they came to watch.

In practice: supermarkets run field research across several stores at once. They track how customers move through the aisles, how they handle products, and how long they spend in front of a shelf. The results guide product placement and store layout.

Task analysis. Breaking a complex task into a hierarchy of smaller steps to find where errors, delays or frustration occur. It shows which sub-task causes the most friction, and it also exposes how much a user has to hold in mind at each stage. Findings feed straight into redesign decisions.

User observation. Watching users perform a specific task, either in the field or in a controlled setting. It captures hesitation, workarounds and errors that users would never report themselves. Unlike field research, observation is usually structured around one defined task.

In practice: gaming companies watch players to see where a game becomes confusing or frustrating, and which features get used most. The findings are used to adjust difficulty and rework gameplay mechanics.

Interviews. A direct conversation with a user, generating mostly qualitative data. Structured interviews use identical questions for every participant, so answers can be compared. Unstructured interviews follow the conversation and uncover the unexpected. Most real research sits in between, using a semi-structured format: a fixed set of questions with room to follow up.

In practice: telehealth is a young service, so researchers interview patients to understand why some are reluctant to use it. Only a conversation can get at the reasons behind that hesitancy.

Surveys and questionnaires. Distributed to large groups, and efficient for collecting quantitative data quickly. A Likert scale (1 = Strongly Disagree to 5 = Strongly Agree) turns attitudes into numbers that can be averaged and compared. The limitation is that a survey cannot ask a follow-up question, so it never explains why an answer was given.

In practice: a kitchen appliance manufacturer surveys owners on functionality, ease of use, satisfaction and whether they would recommend the product. The numbers show which features to add and which areas are causing dissatisfaction.

Focus groups. A structured, moderated discussion with a carefully selected part of the target audience, typically 6 to 10 people. It generates detailed qualitative data and shows how opinions shift as participants respond to each other. The risks are that one dominant participant can skew the discussion, and that a small group may not represent the wider population.

In practice: a coffee machine manufacturer convenes a focus group of potential buyers to discuss an unreleased model. The discussion surfaces both shared expectations and unusual individual concerns before the design is finalised.

Students must be able toDiscuss how a primary persona, scenarios, population stereotypes and demographics can be used to guide design development, and discuss the advantages and disadvantages of using them when engaging with UCD.

After research data is collected, designers use a small set of tools to turn raw findings into a shared language that guides the whole team.

Personas: Fictional but research-based user profiles that represent a target group. A persona is not a real individual. It is a composite, drawn from patterns that appeared across many users. A well-constructed persona includes a name, age, occupation, goals, frustrations and relevant habits. Personas give every member of a multidisciplinary team a specific human being to design for, which makes abstract or self-referential decisions much harder to justify.

A fuller persona profile often records age, health, gender, interests, activities, life goals, education, motivation, employment, expectations, marital status and any organisations the person belongs to. You will not need every field for every project, but the more concrete the profile, the more decisions it can settle.

Advantages: they build empathy, they keep the team focused on specific user needs, and they make design reviews concrete ("would Maya be able to do this?"). Disadvantages: they date quickly as trends and technologies shift, they can reinforce stereotypes if the underlying research was not rigorous, and they can flatten a diverse population into a single profile.

Personas are widely used, but they are not above criticism. Researchers have pointed out that:

• the size of the user group a persona represents cannot be verified;
• its accuracy as a picture of the real user population cannot be independently checked;
• the method itself still awaits proper peer-reviewed evaluation;
• personas often contain ambiguities, so two team members read the same profile differently;
• a poorly researched persona can carry stereotypes straight into the design process.

Scenarios: Short stories describing how a persona uses a product to reach a goal in a specific situation. A scenario anchors decisions in real use: "Maya is running late and tries to complete the checkout on her phone while standing in a queue." Scenarios expose unusual cases and conflicting priorities that a written specification hides. Building detailed scenarios does take time, and any wrong assumption about the user gets carried along with them.

Use cases: A use case is a written description of how a user will interact with a product, told from the user's point of view. Where a scenario sets the scene, a use case walks through the interaction step by step, which is what makes it useful for judging usability as the user actually experiences it.

Population stereotypes: Culturally shared assumptions about how a product should behave, built up through repeated exposure over many years. These are not personality stereotypes. They are learned expectations about controls, symbols and conventions, and they are a product of standardisation within a society rather than anything intrinsic to the machine. Examples:

• Turning a knob clockwise increases volume, temperature or speed.
• In the UK and Australia, a light switch is pushed down for on. In the USA it is pushed up. Both are population stereotypes, and neither is objectively correct.
• Red means stop or danger. Green means safe or go.
• UK and Australian mains plugs place the earth pin differently. Comparing the two is a useful exercise: which arrangement is safer, and why?

Driving side is the largest example of all. Over 60% of the world drives on the right, and the reason for the split is still not settled. Explanations reach back to Roman chariots, medieval knights, Napoleonic conquest and simple courtesy to passengers. Some countries have switched sides outright: Canada in the 1920s, Sweden in 1967, Burma in 1970 and Samoa in 2009.

Population stereotypes make a product feel intuitive immediately, because it matches expectations built over a lifetime. Break one, even accidentally, and you get confusion and error instead. A user can learn an alternative arrangement with a little effort, but under stress people fall back on the older, deeper habit. That matters most in safety-critical design, such as medical devices and emergency equipment.