Foundations of User Research and Human-Centred Design

Introduction

Digital products succeed when they help people accomplish meaningful goals while also supporting organisational objectives. A technically sophisticated product may still fail if users cannot understand it, do not trust it, or cannot complete important tasks. User research and human-centred design provide systematic ways to understand people, frame design problems, generate solutions, and evaluate whether those solutions work.

This chapter introduces the foundations of User Experience (UX), User Interface (UI), user research, human-centred design, usability, customer experience (CX), and evidence-based design. It also distinguishes user needs from business requirements. These distinctions are essential because design decisions often involve several groups: end users, customers, employees, managers, regulators, technical teams, and business owners. A responsible designer must understand their relationships without treating them as interchangeable.

Learning Objectives

By the end of this chapter, you should be able to:

• define UX, UI, user research, human-centred design, usability, and CX;
• explain how these concepts relate to one another;
• distinguish user needs, user requirements, and business requirements;
• describe the main stages of a human-centred design process;
• select appropriate forms of research evidence for a design decision;
• explain why usability and experience must be evaluated in context;
• recognise ethical, organisational, and practical limitations of user research; and
• apply these concepts to an early-stage digital product problem.

1. The Design Problem: Building for People in Context

Design is not simply the production of attractive screens. It is the intentional shaping of interactions, services, information, and technologies so that people can achieve goals in particular situations. A banking application, for example, is used by people with different levels of financial knowledge, devices, accessibility needs, time pressures, and security concerns. A design that works in a quiet office may fail when used on a mobile phone in a crowded station.

Human-centred design therefore treats the user and the user’s context as central sources of design knowledge. It asks questions such as:

• Who is trying to accomplish what goal?
• What circumstances influence the interaction?
• What barriers, expectations, and capabilities affect behaviour?
• What evidence supports the proposed design decision?
• How will the design affect people who are less visible or less powerful?

The word “user” can be useful but incomplete. People may be direct users, indirect users, purchasers, administrators, affected non-users, or members of a wider community. For example, a patient uses a health portal, a clinician may enter information into it, a family member may depend on its output, and a hospital may be responsible for its governance. Good research identifies these relationships rather than assuming that one user profile represents everyone.

2. Essential Concepts

User Experience (UX)

User experience is the perceptions, emotions, responses, and outcomes that arise before, during, and after a person interacts with a product, service, system, or organisation. UX includes practical performance, but it also includes confidence, trust, satisfaction, frustration, perceived value, and the meaning a person attaches to the experience.

UX is broader than an interface. It includes onboarding, customer support, waiting times, error recovery, pricing, privacy communication, delivery, and what happens after use. A well-designed interface cannot fully compensate for a service that repeatedly fails to deliver what it promises.

UX is also situated. The same feature may produce different experiences for different people or in different contexts. A confirmation step may feel reassuring when transferring money but irritating when completing a low-risk form. Consequently, UX cannot be judged only by a designer’s intention; it must be investigated through the experiences of relevant people.

User Interface (UI)

The user interface is the part of a product through which people perceive information and control actions. In a digital product, UI includes layout, typography, colour, icons, controls, navigation, content, feedback, and interaction states. UI design is concerned with making information and actions understandable, perceivable, and controllable.

UI is an important component of UX, but the terms are not synonyms. UI asks, among other questions, whether a button is visible and whether a hierarchy is clear. UX asks broader questions, such as whether the user can complete the whole task, whether the service is trustworthy, and whether the task is valuable in the first place.

Usability

Usability is the extent to which specified users can use a product in a specified context to achieve specified goals with effectiveness, efficiency, and satisfaction. This definition highlights four conditions: the users must be identified, the context must be described, the goals must be clear, and evaluation must consider more than speed alone.

• Effectiveness concerns whether users complete the intended goal accurately and completely.
• Efficiency concerns the resources required, such as time, effort, or number of actions.
• Satisfaction concerns users’ perceived comfort, confidence, and acceptability.

Usability is often evaluated through task-based testing, observation, interviews, analytics, accessibility assessment, and expert inspection. It is not identical to visual appeal. A visually simple design may be unusable if its labels are ambiguous or if it hides critical information.

Customer Experience (CX)

Customer experience is the customer’s overall perception of a relationship with an organisation across touchpoints and over time. Touchpoints may include advertising, sales, a website, a physical store, delivery, billing, support, and complaint handling. UX commonly focuses on interaction with a product or service, whereas CX includes the broader relationship and commercial journey.

The two overlap. A poor checkout UX can damage CX, while a reliable support process can improve CX even when a product has minor interface problems. UX professionals therefore need to understand the wider journey rather than optimising one screen in isolation.

User Research

User research is the systematic investigation of people, their goals, behaviours, contexts, needs, constraints, and interpretations in relation to a design problem. It produces evidence that informs decisions and reduces unsupported assumptions.

Research may be qualitative, quantitative, or mixed-method. Qualitative methods explore meanings and processes, while quantitative methods measure patterns, frequency, magnitude, or relationships. Neither category is automatically superior. The appropriate method depends on the decision, the stage of work, the population, and the type of uncertainty.

Human-Centred Design (HCD)

Human-centred design is an approach in which the needs, capabilities, limitations, experiences, and perspectives of people are considered throughout the design and development process. HCD is iterative: teams investigate a situation, define a problem, develop possible responses, evaluate them, and revise their understanding.

HCD does not mean giving every individual preference equal authority, nor does it mean ignoring business or technical constraints. It means that decisions affecting people should be informed by credible understanding of those people and tested against their real contexts.

3. How the Concepts Relate

These concepts can be understood as overlapping but distinct layers:

The layers are connected but cannot be reduced to one another. For example, a product can have a polished UI but poor usability; a usable application can still create a poor UX if it violates privacy expectations; and a good UX at one touchpoint can be undermined by poor CX elsewhere.

4. Human-Centred Design as an Iterative Process

A practical HCD process is often represented through four recurring activities:

1. Understand and specify context of use. Identify users, tasks, environments, tools, social conditions, and constraints.
2. Specify user requirements. Translate evidence into needs, desired outcomes, accessibility considerations, and success conditions.
3. Produce design solutions. Generate and prototype alternative responses.
4. Evaluate designs against requirements. Test with representative participants and revise the design.

These activities are not strictly linear. Evaluation may reveal that the original problem was framed incorrectly. New research may be required, and requirements may change as the team learns more.

A related design-thinking vocabulary uses the terms empathise, define, ideate, prototype, and test. These labels are useful for teaching and workshop planning, but they should not be treated as a universal recipe. Real projects often move backwards and forwards between activities, and “empathy” must be supported by disciplined research rather than assumed from personal intuition.

Divergent and Convergent Thinking

Design work alternates between expansion and selection. During divergent thinking, a team explores several interpretations, user groups, and possible solutions. During convergent thinking, it prioritises evidence, constraints, feasibility, and potential value. Premature convergence can cause a team to defend its first idea. Endless divergence can prevent delivery. Effective facilitation makes the movement between the two explicit.

The Double Diamond as a Communication Model

The Double Diamond describes four broad movements: discover, define, develop, and deliver. The first diamond concerns understanding and framing the problem; the second concerns exploring and refining solutions. It is a communication model rather than a mandatory project plan. Its value lies in showing that teams should not move directly from a vague problem to a single solution without investigation.

5. User Needs and Business Requirements

A central professional skill is distinguishing what people need from what an organisation wants to achieve.

User Needs

A user need is a condition or outcome necessary for a person to accomplish a meaningful goal. It should describe the desired outcome rather than prematurely prescribing a feature. For example:

• “A commuter needs to know whether a train is delayed before leaving work.”
• “A patient needs to understand what preparation is required before an appointment.”
• “A first-time customer needs confidence that payment has been completed.”

A need is not necessarily the same as a stated preference. A person may request a particular feature because it is the solution they know, while research may reveal a more fundamental need.

Business Requirements

A business requirement describes an organisational objective, constraint, obligation, or success condition. Examples include increasing completed applications, reducing support costs, meeting a legal obligation, protecting revenue, or integrating with an existing system.

Business requirements are legitimate design inputs, but they should not be disguised as user needs. “Increase newsletter sign-ups by 20%” is a business objective. It does not explain whether subscribing is valuable to users or whether the proposed method is respectful.

Product and Technical Requirements

A product requirement describes what a product or service must do. A technical requirement describes implementation conditions, such as supported platforms, security controls, response expectations, or integration constraints. These requirements may be necessary, but they should be connected to user and organisational outcomes.

Resolving Tensions

Tensions are normal. A business may want more data, while users may want minimal data collection. A marketing team may want prominent promotional content, while users need a clear route to complete a task. The designer’s responsibility is not to choose users or the business automatically, but to make trade-offs visible and evaluate their consequences.

A useful requirement statement identifies:

• the affected people;
• the goal or outcome;
• the evidence supporting it;
• constraints and dependencies;
• risks and ethical implications; and
• how success will be evaluated.

6. Evidence-Based Design

Evidence-based design means making design decisions with explicit reference to credible information rather than relying primarily on taste, hierarchy, or untested assumptions. Evidence can come from several sources:

• interviews and contextual conversations;
• observation and field studies;
• diary studies;
• surveys;
• behavioural analytics;
• customer-support records;
• accessibility evaluations;
• usability tests;
• expert reviews;
• market and domain research; and
• experiments or comparative tests.

Evidence is not automatically objective. Every method samples particular people, contexts, and questions. A survey may show what respondents report, while observation may reveal what they actually do. Analytics may show that users abandon a task but cannot, by themselves, explain why. Evidence should therefore be interpreted in relation to its collection method and limitations.

Research Questions and Method Choice

Begin with a decision, not a method. “Should the onboarding process be redesigned?” is less useful than “Why do new users fail to complete onboarding, and which intervention is likely to help?” The second question can lead to interviews, funnel analysis, usability testing, or a combination.

Triangulation

Triangulation compares evidence from different methods, researchers, data sources, or perspectives. If support tickets, usability tests, and analytics all indicate confusion at the same step, confidence in the diagnosis increases. Triangulation does not guarantee truth, but it helps reveal contradictions and reduces dependence on one imperfect source.

From Data to Insight

Data are observations or records. Findings are patterns identified in the data. Insights connect a finding to a meaningful implication for design. For example:

• Data: several participants reread the delivery options.
• Finding: participants were uncertain about the difference between two options.
• Insight: the service should explain the consequence and cost of each option before selection.

An insight should not overclaim. A small usability study can reveal serious problems, but it cannot establish the percentage of the whole population affected without suitable quantitative evidence.

7. Practical Research Foundations

Sampling

Participants should be recruited because their experience is relevant to the research question. Important dimensions may include experience level, task frequency, accessibility needs, language, age, location, and relationship to the service. Convenience sampling is sometimes necessary in early exploratory work, but its limitations must be documented.

Avoid treating a persona as a demographic stereotype. A useful persona is an evidence-based representation of a relevant pattern of goals, behaviours, constraints, and contexts. Personas should be revised when evidence changes.

Interviews and Observation

Interviews are valuable for exploring perceptions, histories, motivations, and interpretations. Good interviews use open questions, probes, and neutral wording. Asking “What happened the last time you paid a bill?” usually produces more useful evidence than asking “Would you like an easier bill-payment feature?”

Observation reveals workarounds, interruptions, physical environments, and differences between reported and actual behaviour. Researchers must explain their role, avoid unnecessary disruption, and protect sensitive information.

Usability Testing

In usability testing, participants attempt realistic tasks while a researcher observes behaviour and collects comments or measures. Tasks should state a goal without revealing the exact interface path. For example, “Find out when your parcel will arrive and change the delivery date” is preferable to “Click the tracking menu.”

A test can be moderated or unmoderated, remote or in person, formative or summative. Early formative tests often use small samples to identify severe problems and improve a prototype. Results should be treated as diagnostic evidence, not as a simplistic vote on whether the design is good.

Accessibility and Inclusive Research

Accessibility is part of quality, not an optional enhancement. Research should include people with disabilities and consider assistive technologies, motor limitations, sensory differences, cognitive load, literacy, language, and situational impairments. Designs should support perceivable information, operable controls, understandable content, and compatibility with relevant technologies.

Inclusive research also considers recruitment barriers, compensation, privacy, cultural context, and the power relationship between researcher and participant. A participant should not be treated as a source of free labour or personal disclosure.

8. A Worked Applied Case

Illustrative Case: Municipal Recycling Service

Background. A city introduces an online service that tells residents how to dispose of household items. The service receives many visits, but call-centre staff report that residents remain uncertain about disposal rules.

Problem. The organisation initially proposes adding more pages and a prominent registration request. This is a business-led solution, not yet a validated user need. The research question becomes: “How do residents identify disposal instructions, where do they become uncertain, and what information do they need at the moment of decision?”

Analysis. The team reviews search logs and call-centre records, interviews residents, and observes people attempting tasks on mobile phones. Evidence shows that users often search by the name of an object, such as “paint tin,” while the service is organised by material categories. Some residents also interpret “recycling” as meaning every item can enter the same bin. The problem is therefore not simply a lack of content. It involves vocabulary, categorisation, confidence, and local variation.

Approach. The team creates a search-first prototype. It uses familiar object names, asks clarifying questions when an item has several disposal routes, displays location-specific instructions, and explains the reason for restrictions. The prototype is tested with residents who have different levels of digital confidence and with screen readers. Registration is removed from the critical task because it does not serve the immediate user goal.

Outcome. In subsequent testing, participants find instructions more quickly and make fewer incorrect selections. The organisation gains a clearer basis for improving the service and can later measure changes in avoidable calls and incorrect disposal. The case does not prove that one interface solves all waste-management problems; policy clarity, collection capacity, and communication outside the website remain relevant.

Learning points. The case demonstrates the distinction between a business request and a user need, the importance of context and vocabulary, the value of combining behavioural and qualitative evidence, and the need to test accessibility. It also shows that reducing a business activity, such as registration, may improve the wider organisational outcome if it removes friction from the primary task.

9. Challenges, Ethics, and Governance

User research involves ethical responsibilities because researchers may collect personal, behavioural, health, financial, or location data. Participants should understand the purpose of the research, what participation involves, how data will be used, and that participation is voluntary. Consent should be informed and proportionate, not hidden in complex language.

Researchers should collect only data necessary for the stated purpose, protect it appropriately, limit access, and establish retention and deletion practices. Sensitive information should not be copied into design documents without need. When recording sessions, obtain explicit permission and explain who will see the recordings.

Power differences require care. Employees may feel unable to refuse a manager’s request. Children and vulnerable adults require additional safeguards. Compensation should recognise participants’ time without becoming coercive. Researchers must also consider whether a design could enable surveillance, exclusion, addiction, discrimination, or manipulation.

Dark patterns are interface practices that steer people toward outcomes they did not intend, such as obscuring cancellation or making privacy-protective choices difficult. A design can meet a narrow business metric while damaging trust and autonomy. Ethical design therefore evaluates long-term effects, not only immediate conversion.

Research quality also has governance implications. Teams should record recruitment criteria, research questions, methods, limitations, key findings, and decisions. This creates traceability: stakeholders can understand why a decision was made and whether later evidence should change it.

10. Contemporary Practice and AI

Contemporary UX work increasingly uses artificial intelligence for search, recommendation, content generation, transcription, summarisation, and conversational interfaces. AI can accelerate analysis and create prototypes, but it does not remove the need for human research. Generated summaries may omit minority perspectives, reproduce bias, or present uncertain interpretations as facts.

When AI is used in research or design, teams should consider:

• whether participant data are being sent to a third-party system;
• whether consent covers such processing;
• how outputs will be checked against source material;
• whether the system behaves differently across languages or groups;
• how users can understand, challenge, or correct automated decisions; and
• what happens when the system is wrong.

AI interfaces also create new UX questions concerning disclosure, explainability, uncertainty, human handover, error recovery, and appropriate reliance. Automation should not be treated as inherently human-centred. Its value depends on whether it supports people’s goals without transferring unreasonable risk or responsibility to them.

11. Best-Practice Principles

A beginning UX practitioner should develop the following habits:

1. Start with a real decision or problem, not a preferred research method.
2. Separate observations, interpretations, and recommendations.
3. Describe users and contexts specifically rather than relying on an abstract “average user.”
4. Test assumptions early, when changes are less expensive.
5. Include accessibility and exclusion risks from the beginning.
6. Use multiple evidence sources when the decision is important.
7. Present uncertainty honestly and identify what the research cannot establish.
8. Connect user needs to measurable organisational and product outcomes.
9. Treat prototypes as learning tools rather than miniature final products.
10. Revisit requirements when evidence challenges the original framing.

Chapter Summary

UX concerns the perceptions, responses, and outcomes that arise across interaction with a product or service. UI concerns the interface through which information and actions are presented. Usability focuses on effectiveness, efficiency, and satisfaction for specified users in specified contexts. CX extends attention to the customer’s relationship with an organisation across touchpoints.

User research systematically investigates people, behaviours, goals, contexts, and constraints. Human-centred design uses this understanding throughout an iterative process of investigating context, specifying requirements, creating solutions, and evaluating them. User needs describe meaningful human outcomes, whereas business requirements describe organisational objectives or constraints; both matter but must not be confused.

Evidence-based design uses appropriate, critically interpreted research rather than personal preference. Interviews, observation, surveys, analytics, usability testing, accessibility evaluation, and triangulation each answer different questions. Ethical practice requires informed consent, privacy protection, inclusive recruitment, honest reporting, and attention to harmful or manipulative outcomes. The central professional lesson is that good design is not merely what a team can build or what a stakeholder requests. It is a reasoned response to evidence about people, their contexts, and the outcomes that matter.

Key Terms

Customer experience (CX): The customer’s overall perception of an organisation across interactions and over time.

Divergent thinking: Expanding the range of possible interpretations, ideas, or solutions.

Evidence-based design: Design decision-making informed by credible and relevant evidence.

Human-centred design: An iterative approach that considers people, their needs, capabilities, and contexts throughout design.

Insight: An evidence-supported interpretation that has implications for action or design.

Interaction design: The design of behaviours, actions, feedback, and flows through which people use a system.

Persona: An evidence-based representation of a relevant user pattern.

Prototype: A representation of a proposed design used to explore or evaluate ideas.

Requirement: A documented condition, capability, objective, or constraint that a product or service must address.

Research question: A focused question that guides the collection and interpretation of evidence.

Satisfaction: The extent to which an interaction is perceived as comfortable, acceptable, or pleasing.

Stakeholder: A person or group that affects, is affected by, or has an interest in a product or service.

Task: A goal-directed activity performed by a person within a context.

Triangulation: Comparing evidence from different sources or methods to strengthen interpretation.

UI: The user interface through which people perceive information and control a system.

Usability: The extent to which specified users achieve specified goals effectively, efficiently, and satisfactorily in context.

User need: A necessary human outcome or condition related to a meaningful goal.

User research: Systematic investigation of people, behaviours, goals, contexts, and constraints relevant to design.

UX: The perceptions, emotions, responses, and outcomes associated with interaction with a product, service, or system.

Review Questions

Short Answer Questions

1. Define user experience and explain why it is broader than UI.
2. What are the three commonly cited dimensions of usability?
3. Distinguish a user need from a business requirement.
4. What is the purpose of triangulation in user research?
5. Name the four recurring activities in a human-centred design process.

Long Answer Questions

1. Compare UX, UI, usability, and CX, using a digital service as an example.
2. Explain how a team can move from research data to a defensible design insight.
3. Discuss why human-centred design should be iterative rather than strictly linear.
4. Explain the ethical responsibilities involved in recruiting participants and handling research data.
5. Describe how accessibility should influence both research planning and design evaluation.

Analytical / Application Questions

1. A retailer asks the design team to add more promotional pop-ups because sales are below target. Formulate a research question, identify possible user needs, and propose two suitable research methods.
2. Analytics show that many users abandon an online application at the identity-verification step. Explain what analytics can establish, what they cannot establish, and how you would investigate the cause.
3. A product manager proposes requiring registration before users can find urgent service information. Analyse the conflict between the business objective and the user need, and recommend an evidence-based way to decide whether registration belongs in the flow.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes UX from UI?

A. UX concerns only visual styling, while UI concerns research.

B. UX concerns the broader experience and outcomes, while UI concerns the interface used for interaction.

C. UX applies only to physical products, while UI applies only to services.

D. UX and UI are identical terms for screen design.

Correct Answer: B. UX concerns the broader experience and outcomes, while UI concerns the interface used for interaction.

Question 2

Usability is most accurately concerned with whether specified users can achieve specified goals with which combination?

A. Popularity, novelty, and profitability

B. Beauty, originality, and technical complexity

C. Effectiveness, efficiency, and satisfaction

D. Speed, advertising reach, and market share

Correct Answer: C. Effectiveness, efficiency, and satisfaction

Question 3

Which is a user need rather than a business requirement?

A. Increase completed purchases by 15%.

B. Reduce call-centre operating costs.

C. Collect an email address from every visitor.

D. Understand the total cost before confirming payment.

Correct Answer: D. Understand the total cost before confirming payment.

Question 4

What is the primary purpose of user research?

A. To confirm that a stakeholder’s preferred solution is correct

B. To systematically investigate people, contexts, behaviours, and needs relevant to design

C. To replace all business analysis with participant opinions

D. To guarantee that a product will be commercially successful

Correct Answer: B. To systematically investigate people, contexts, behaviours, and needs relevant to design

Question 5

Which activity belongs in a human-centred design process?

A. Evaluating designs against user requirements

B. Avoiding prototypes until development is complete

C. Treating the first solution as final

D. Defining requirements without investigating context

Correct Answer: A. Evaluating designs against user requirements

Question 6

A team wants to understand why users abandon a form. Which combination is most appropriate for an initial investigation?

A. Only a logo redesign

B. Analytics combined with usability testing or interviews

C. A decision based solely on the manager’s experience

D. A survey asking users whether they like the company

Correct Answer: B. Analytics combined with usability testing or interviews

Question 7

What does triangulation mean in user research?

A. Using only three participants in every study

B. Comparing evidence from different sources or methods

C. Converting all qualitative data into financial data

D. Testing only three alternative interfaces

Correct Answer: B. Comparing evidence from different sources or methods

Question 8

Which practice best supports ethical user research?

A. Collecting as much personal data as possible for future use

B. Recording participants without informing them

C. Explaining participation, protecting data, and obtaining informed consent

D. Recruiting only people who agree with the design team

Correct Answer: C. Explaining participation, protecting data, and obtaining informed consent

Question 9

A prototype is primarily used to:

A. Represent and evaluate a proposed design before full implementation

B. Prove that no further research is required

C. Replace accessibility testing

D. Guarantee technical performance in production

Correct Answer: A. Represent and evaluate a proposed design before full implementation

Question 10

Why should AI-generated research summaries be checked against source material?

A. AI cannot produce any text at all

B. AI outputs may omit perspectives, reproduce bias, or state uncertain interpretations as facts

C. Source material is always less accurate than generated text

D. Checking sources eliminates the need for participant consent

Correct Answer: B. AI outputs may omit perspectives, reproduce bias, or state uncertain interpretations as facts