2. Human-Centred Design and UX Strategy

Introduction and Context

User experience (UX) design is concerned with the quality and meaning of people’s interactions with products, services, systems, and organisations. In digital environments, UX includes much more than visual appearance. It encompasses whether users can understand a service, complete a task efficiently, recover from errors, trust the organisation, and achieve a meaningful outcome. Human-centred design places these human needs at the centre of product and service decisions while recognising that successful solutions must also support organisational objectives, technical realities, and social responsibilities.

For full-stack developers, this perspective is essential. A technically robust application can still fail if its information architecture is confusing, its interaction model conflicts with user expectations, or its value is unclear. Conversely, a well-researched experience can create development complexity if feasibility and architecture are ignored. UX strategy therefore connects discovery, design, delivery, measurement, and organisational priorities.

This chapter examines design thinking, the Double Diamond, Lean UX, and agile discovery as complementary approaches rather than competing recipes. It also explains how user needs are connected to value propositions, product strategy, key performance indicators (KPIs), and digital transformation. The central argument is that UX is not merely a design activity performed before development; it is a strategic, evidence-informed way of reducing uncertainty and creating sustainable value.

Learning Objectives

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

1. Explain the meaning, principles, and strategic importance of human-centred design.

2. Distinguish design thinking, the Double Diamond, Lean UX, and agile discovery.

3. Plan discovery activities that connect user needs with business and technical objectives.

4. Develop problem statements, personas, journey maps, value propositions, hypotheses, and experiments.

5. Translate UX outcomes into product goals and meaningful KPIs.

6. Evaluate trade-offs involving desirability, viability, feasibility, accessibility, ethics, and sustainability.

7. Apply human-centred methods to digital transformation initiatives and full-stack product development.

From User Needs to Strategic Value

Human-centred design begins with the proposition that people affected by a system should inform its design. This does not mean accepting every stated request literally. Users may describe a desired feature when their underlying need is different. A customer asking for a downloadable form may actually need confidence that an application has been successfully submitted. A support employee requesting a dashboard may need prioritisation, not simply more data. Discovery seeks to uncover these underlying goals, behaviours, constraints, and contexts.

A useful distinction is between a need, a problem, and a solution. A need describes an outcome or condition important to a person. A problem describes an obstacle preventing that outcome. A solution is a proposed response. Confusing these levels leads teams to build features before understanding the situation. For example, “users need a mobile app” is a solution assumption; “commuters need to know whether a delayed service will affect their connection” is closer to a problem and desired outcome.

UX strategy links three forms of value:

• User value: the usefulness, usability, accessibility, trust, and emotional or social benefit experienced by users.
• Business value: revenue, retention, cost reduction, compliance, brand strength, operational efficiency, or strategic differentiation.
• Technical and organisational value: maintainability, data quality, platform capability, employee effectiveness, and alignment with enterprise architecture.

A viable product must balance these dimensions. A feature may be desirable but too costly to operate; profitable but harmful to users; or technically feasible but irrelevant to the organisation’s strategic direction. The role of UX strategy is to make these relationships visible and support informed decisions.

Important Concepts and Terminology

Human-centred design (HCD) is an approach that develops systems through an explicit understanding of users, tasks, environments, and effects, with users involved throughout design and evaluation. It is iterative: research informs design, design produces prototypes, and evaluation leads to refinement.

User experience includes perceptions and responses arising before, during, and after interaction with a product or service. It includes functional, emotional, social, and contextual dimensions.

Usability refers to the extent to which specified users can achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context. Usability is important, but it is only one part of the wider user experience.

Desirability, viability, and feasibility provide a practical decision lens. Desirability asks whether people want or need the solution; viability asks whether it supports a sustainable organisational model; feasibility asks whether it can be built and operated with available technology, skills, time, and resources.

Accessibility concerns the ability of people with diverse abilities to perceive, understand, navigate, and interact with a product. It is a quality requirement and a matter of inclusion, rights, and professional responsibility.

Empathy in design means developing an evidence-based understanding of people’s perspectives and circumstances. It does not mean assuming that the designer’s experience represents the user’s experience.

A persona is a research-informed representation of a meaningful user group. A persona should synthesise patterns in goals, behaviours, barriers, and contexts rather than inventing decorative demographic details.

A journey map represents stages of an experience, user actions, thoughts, emotions, touchpoints, pain points, and opportunities. It helps teams see the experience across channels and organisational boundaries.

A value proposition explains for whom a product creates value, which problem or job it addresses, what benefit it provides, and why it is preferable to alternatives.

A hypothesis is a testable statement about a user, behaviour, problem, or expected outcome. It prevents assumptions from being treated as facts.

An MVP, or minimum viable product, is the smallest coherent product or experiment that can test a significant value assumption and generate learning. It is not necessarily a poorly finished or feature-poor version of the final product.

A KPI is a measurable indicator used to assess progress toward an important objective. A UX metric becomes strategically useful when its relationship to an outcome is understood.

Design Thinking as a Way of Framing Uncertainty

Design thinking is commonly described through five activities: empathise, define, ideate, prototype, and test. These activities are not a rigid sequence. Teams may return to research after testing, redefine the problem after ideation, or prototype during early exploration. The model is valuable because it encourages teams to delay premature commitment and alternate between expanding and narrowing their understanding.

During empathise, researchers seek evidence through interviews, observation, diary studies, contextual inquiry, support-log analysis, analytics, and other appropriate methods. The purpose is not to collect opinions indiscriminately but to understand behaviour, motivation, constraints, and context.

During define, evidence is synthesised into a focused opportunity. A strong problem statement identifies a user group, a meaningful situation, an unmet need, and the consequence of leaving it unresolved. “How might we” questions can then frame opportunities without prescribing a solution. For example: “How might we help first-time applicants understand what information they need before beginning an application?”

During ideate, teams generate multiple possible responses. Divergent thinking is useful before evaluation because early criticism can cause teams to settle on familiar solutions. Ideas are subsequently assessed against user value, strategic fit, feasibility, risk, and evidence.

During prototype, teams create representations that are sufficiently realistic to answer a question. A paper sketch may test structure; a clickable wireframe may test navigation; a coded prototype may test performance or integration. The fidelity of a prototype should match the uncertainty being investigated.

During test, representative participants attempt realistic tasks while researchers observe behaviour and probe understanding. Testing is not a demonstration in which a participant is persuaded to approve the design. Evidence includes hesitation, workarounds, errors, misunderstandings, and successful strategies. Findings should be connected to design decisions and confidence levels.

The strength of design thinking lies in its treatment of ambiguity. Its limitation is that broad workshop activities can become superficial if they are disconnected from evidence, delivery constraints, and measurable outcomes. Design thinking should therefore be integrated with product management, engineering, analytics, and governance.

The Double Diamond: Divergence, Convergence, and Decision Points

The Double Diamond, associated with the Design Council, represents four broad modes: discover, define, develop, and deliver. The first diamond concerns ensuring that the right problem is being addressed; the second concerns developing and implementing the right response.

In discover, a team expands its understanding through research and environmental analysis. It may examine user behaviour, market alternatives, operational processes, policies, technologies, and stakeholder perspectives. Discovery should include people who are often excluded from mainstream research, such as users with disabilities or those with limited connectivity.

In define, evidence is narrowed into a prioritised challenge. Teams identify patterns, tensions, opportunity areas, and decision criteria. A useful output is a clear design challenge linked to organisational objectives but not reduced to a predetermined feature.

In develop, multiple concepts are generated, prototyped, compared, and evaluated. Collaboration across design, engineering, product, data, security, and operations is important because each discipline sees different risks and possibilities.

In deliver, a selected approach is implemented, launched, monitored, and improved. Delivery is not the end of learning. Production analytics, customer feedback, usability studies, incident reports, and operational data may reveal that the initial definition requires revision.

The diamonds emphasise that teams should both open up and narrow down. A common failure is to converge too early: a stakeholder suggests a solution, development begins, and later research is used only to justify the decision. Another failure is endless divergence without commitment. Each phase therefore needs explicit decision points, evidence standards, owners, and time boundaries.

Lean UX and Agile Discovery

Lean UX adapts UX practice to environments characterised by rapid release cycles, cross-functional teams, and incomplete information. It shifts attention from producing large collections of design documents to creating shared understanding, testing assumptions, and measuring outcomes. Lean UX is particularly compatible with agile development because research, design, coding, and validation can occur in repeated learning cycles.

A typical Lean UX cycle begins with an outcome or business objective, such as reducing abandoned applications. The team identifies assumptions about users, needs, behaviours, and solutions. These assumptions are expressed as hypotheses, for example: “We believe that showing application progress and required documents before form completion will reduce abandonment among first-time applicants.” The team then designs the smallest experiment capable of testing the hypothesis, such as a prototype usability test, an A/B experiment, or a limited release. Results inform the next cycle.

Lean UX promotes collaborative activities such as assumption mapping, collaborative sketching, design studios, story mapping, and hypothesis-driven roadmaps. It does not eliminate research or documentation. Instead, documentation is proportionate to risk and purpose. A safety-critical service requires stronger evidence and traceability than a low-risk promotional page.

Agile discovery is the continuous investigation that occurs alongside delivery. It may include customer interviews, technical spikes, competitive review, data analysis, service blueprinting, accessibility checks, and prototype evaluation. A dual-track model often separates but connects a discovery track and a delivery track. Discovery explores and validates upcoming work; delivery builds and releases work that has sufficient evidence and clarity. The tracks interact continuously rather than operating as isolated departments.

Agile discovery creates several managerial requirements. Teams need protected research capacity, access to users and data, clear decision rights, and a shared definition of evidence. Product backlogs should not become lists of unexamined stakeholder requests. Each significant item should be connected to an outcome, a user problem, a hypothesis, and an acceptance or evaluation method.

Connecting Research with Product Strategy

Research becomes strategically useful when it changes a decision. A research repository may contain extensive interview transcripts yet have little influence if insights are not synthesised and communicated. Teams should distinguish raw data from insight. A quotation is data; a repeated pattern showing that users postpone an application because eligibility rules are unclear is an insight. An opportunity is a possible area for value creation; it is not yet a solution.

A practical synthesis sequence is to gather observations, code recurring behaviours and barriers, cluster related evidence, identify patterns, and formulate implications. Teams should record the strength and source of evidence. Quantitative analytics may show where users abandon a task, while qualitative research may explain why. Neither type automatically replaces the other.

Product strategy translates organisational ambition into choices about target users, problems, value, capabilities, positioning, investment, and sequencing. UX contributes by clarifying user outcomes and the experience required to achieve them. A product strategy should answer questions such as:

• Which user groups and situations are priorities?
• What important problem will the product solve better than alternatives?
• What organisational outcome will this create?
• Which capabilities are essential now, and which can wait?
• What evidence would justify further investment?

The Value Proposition Canvas can support this work by relating a customer profile—jobs, pains, and gains—to a value map—products and services, pain relievers, and gain creators. The canvas is a thinking tool, not proof of product-market fit. Its assumptions must be tested with users and market evidence.

A useful prioritisation approach considers user impact, strategic alignment, confidence in evidence, effort, risk, and urgency. Frameworks such as impact-effort mapping or weighted scoring can structure discussion, but numerical scores should not create false precision. A low-confidence high-impact opportunity may deserve research rather than immediate development.

From Outcomes to KPIs

UX teams sometimes measure what is easy to count rather than what matters. Page views, feature usage, and time on site can be useful diagnostic indicators, but they are not automatically signs of value. For example, increased time on a checkout page may indicate engagement or confusion. Metrics require interpretation and a clear relationship to an objective.

A hierarchy can connect strategy to measurement:

1. Strategic objective: the organisational result, such as improving access to public services.

2. Product outcome: the change the product should create, such as increasing successful self-service completion.

3. User behaviour: an observable action, such as completing an application without assisted support.

4. Experience indicator: a measure of ease, confidence, comprehension, or accessibility.

5. Operational metric: a measure such as response time, error rate, support volume, or availability.

A balanced measurement set may include completion rate, abandonment rate, task success, time on task, error frequency, accessibility defects, customer effort, satisfaction, retention, conversion, support contacts, and system performance. The chosen metrics must reflect the product context. In a healthcare or public-service system, equitable access and safe completion may be more important than conversion or revenue.

Teams should define a baseline, target, measurement period, user segment, and method. They should also watch for Goodhart’s law: when a measure becomes a target, it can cease to be a useful measure. Optimising for shorter task time could encourage removal of necessary explanations. Ethical measurement avoids dark patterns, respects consent, and examines outcomes across demographic and accessibility groups.

Human-Centred Design in Digital Transformation

Digital transformation is not simply the replacement of paper with software. It involves changes to operating models, capabilities, data flows, decision-making, and relationships with customers or citizens. Human-centred design helps organisations understand the experience of transformation from multiple perspectives: external users, employees, managers, partners, and affected communities.

Service blueprinting is useful when an experience depends on visible interactions and backstage processes. It maps user actions, frontstage touchpoints, backstage activities, systems, policies, and support processes. A redesigned online form may fail if staff cannot process its data, identity verification is unreliable, or exception handling is undefined. UX strategy therefore extends beyond the interface to the service system.

Transformation programmes should begin with outcomes rather than technology procurement. Cloud platforms, artificial intelligence, automation, and data integration may enable change, but they do not establish that change is desirable or safe. Discovery should identify the problem, assess readiness, map affected groups, and examine process and governance implications. Small pilots can test value while revealing operational and ethical risks before large-scale investment.

For full-stack teams, this means involving engineers early. Technical discovery can investigate API constraints, data quality, authentication, performance, observability, security, and integration risk. Design discovery can investigate user goals, language, accessibility, trust, and workflow. Joint discovery produces more realistic concepts than either discipline working alone.

An Illustrative Case: Redesigning a University Scholarship Service

Background

A fictional university, Northbridge University, offers a scholarship application service used by domestic and international students. The existing service consists of a downloadable document, email submission, and manual follow-up. The university wants to improve access, reduce administrative workload, and increase the proportion of eligible students who complete applications.

Situation and Problem

The initial proposal from administration is to build a mobile application. However, preliminary evidence shows that students abandon the process because eligibility rules are difficult to interpret, required documents vary by scholarship, and applicants receive little confirmation after submission. Some students use shared devices or have limited connectivity. Administrative staff also re-enter information into several systems.

The team reframes the challenge: “How might we help eligible students understand their options, prepare the right evidence, and submit with confidence while reducing avoidable administrative work?” This problem statement is broader and more useful than the original request for a mobile app.

Analysis

Discovery combines interviews with students and staff, observation of application processing, review of support emails, analysis of completion data, and a technical assessment of existing identity and student-record systems. A journey map identifies uncertainty during eligibility checking, repeated data entry during application, and anxiety after submission. A service blueprint reveals that staff manually verify information that already exists in university systems.

The team develops several hypotheses:

• If eligibility information is presented through plain-language questions, more students will correctly identify suitable scholarships.
• If the system provides a personalised document checklist, fewer applications will be delayed.
• If applicants receive a clear status and next-step message, support enquiries will decrease.
• If verified student data is reused with consent, completion effort and administrative re-entry will fall.

Approach and Strategy

The product strategy prioritises a responsive web service rather than a native mobile application because students use varied devices and the core need is accessible, cross-platform task completion. A prototype tests the eligibility flow and document checklist with students representing different levels of digital confidence and accessibility needs. Engineers investigate identity integration, secure document storage, notification services, and data retention requirements.

The initial MVP includes a guided eligibility pathway, a personalised checklist, save-and-return capability, accessible document upload, confirmation, and application-status information. Less essential features, such as social sharing and a dedicated mobile app, are excluded until evidence justifies them.

The team defines outcomes and measures: increased successful completion among eligible applicants, reduced incomplete submissions, reduced repetitive support enquiries, improved task success in usability testing, and equitable performance across relevant user groups. A dashboard combines product analytics with qualitative feedback and operational data.

Outcome

In this illustrative case, the first release reveals that students understand the checklist but struggle with a particular document category. The team revises the terminology and adds examples rather than merely increasing technical functionality. Staff report fewer duplicate data-entry tasks, while a monitored accessibility review identifies a keyboard-navigation defect before wider rollout. The case demonstrates that discovery changed both the product concept and the operational process.

Learning Points

The case illustrates five principles. First, the stated solution may not represent the underlying need. Second, user experience depends on service processes and organisational systems. Third, prototypes and technical spikes should occur together. Fourth, an MVP should test a value proposition, not simply contain a small number of features. Finally, success must be judged through user, business, operational, and equitable outcomes.

Challenges, Risks, and Common Mistakes

Human-centred work faces organisational and methodological risks. Stakeholders may treat research as a formality after a strategic decision has already been made. Teams may recruit only convenient participants, excluding people with different abilities, languages, resources, or levels of confidence. Interviewers may ask leading questions or interpret aspirations as evidence of future behaviour. Usability tests may be conducted with unrealistic tasks or participants who are too familiar with the product.

Another risk is solutionism, in which teams jump from a complaint to a feature. There is also feature inflation, where every stakeholder request enters the backlog without a clear outcome. Excessive personas and journey maps can create a false impression of rigour when they are not based on research. Conversely, excessive insistence on perfect evidence can delay valuable learning.

Lean approaches can be misunderstood as permission to skip accessibility, security, documentation, or quality assurance. Speed is not a sufficient justification for releasing an unsafe or discriminatory service. Likewise, agile iteration does not excuse constant change without strategic direction. Teams need a stable outcome and flexible methods for learning how to achieve it.

Common mistakes include measuring activity instead of impact, treating satisfaction as the only UX metric, ignoring post-launch behaviour, and failing to communicate uncertainty. Professional teams make assumptions visible, record decisions, identify evidence gaps, and revisit conclusions when conditions change.

Ethical, Governance, and Professional Considerations

Human-centred design involves people’s information, identities, vulnerabilities, and experiences. Research must use informed consent, explain participation and data use, minimise collection, and protect confidentiality. Sensitive interviews require appropriate storage, access controls, and retention practices. Participants should not be pressured by power relationships, such as students being recruited by their assessors.

Designers and developers must consider privacy by design, inclusive language, accessibility standards, security, and the consequences of failure. Automated recommendations or eligibility decisions require transparency, routes for appeal, and monitoring for unfair outcomes. Personalisation can improve relevance but may also create surveillance or exclusion. Dark patterns—interfaces that manipulate users into choices they would not otherwise make—conflict with professional integrity.

Governance should clarify who owns research data, who approves high-risk experiments, how accessibility defects are prioritised, and how product decisions are documented. In regulated contexts, legal and sector-specific requirements may determine consent, records, security, retention, and auditability. Ethical review is not a final checklist; it should influence problem framing and product strategy from the beginning.

Technology, Analytics, and AI in UX Practice

Digital tools support recruitment, collaborative mapping, prototyping, analytics, session recording, accessibility testing, feature flagging, and experimentation. Their value depends on the quality of questions and interpretation. Analytics can identify patterns at scale, while research explains meaning and context. Automated tools can detect some accessibility or performance issues but cannot replace evaluation with people who have diverse needs.

AI can assist with transcript summarisation, clustering, content alternatives, code prototyping, conversational interfaces, and predictive analysis. However, AI-generated synthesis may omit minority perspectives, reproduce bias, or present uncertain inferences as facts. Teams should preserve source evidence, review outputs critically, protect confidential data, and disclose consequential uses. AI should augment professional judgement rather than determine user needs autonomously.

Emerging practice increasingly combines continuous discovery, design systems, experimentation platforms, service design, and responsible AI governance. Personalised and multimodal interfaces create new opportunities but also increase the importance of transparency, consent, explainability, and accessibility. As products become interconnected, UX strategy must address not only an individual screen but also data relationships, algorithmic decisions, and long-term trust.

Best Practices for Professional Application

Effective human-centred UX strategy can be supported by the following practices:

• Begin with outcomes and user situations, not predetermined features.
• Include users, engineers, product leaders, operations, security, and accessibility specialists early.
• Use mixed evidence: qualitative research, quantitative data, technical investigation, and service analysis.
• Make assumptions explicit and test the riskiest ones first.
• Match research and prototype fidelity to the decision being made.
• Treat accessibility, privacy, security, and inclusion as design requirements.
• Connect every major initiative to a measurable outcome and a learning plan.
• Revisit the experience after release using analytics, feedback, support data, and evaluation.
• Document rationale, uncertainty, rejected alternatives, and ethical considerations.
• Prefer a coherent, evidence-based MVP over a large collection of loosely justified features.

Chapter Summary

Human-centred design places people’s goals, contexts, abilities, and welfare at the centre of product and service decisions. UX strategy connects user value with business value, technical feasibility, and organisational capability. Design thinking supports exploration and reframing; the Double Diamond clarifies divergence and convergence; Lean UX emphasises assumptions, hypotheses, experiments, and outcomes; and agile discovery integrates learning with iterative delivery.

Effective practice moves from research to synthesis, problem framing, value propositions, prototyping, testing, implementation, and measurement. Product strategy becomes stronger when it identifies priority users, meaningful problems, strategic outcomes, and evidence-based sequencing. KPIs should connect organisational objectives with user behaviour, experience quality, and operational performance. In digital transformation, service blueprints and cross-functional discovery reveal how interfaces depend on processes, data, people, and governance. Ethical research, accessibility, privacy, security, and responsible use of analytics and AI are fundamental conditions of professional practice.

Key Terms

Human-centred design: An iterative approach that designs systems from an explicit understanding of people, tasks, contexts, and effects.

User experience: The perceptions, responses, and outcomes associated with interaction with a product or service.

Usability: The effectiveness, efficiency, and satisfaction with which specified users achieve goals in a specified context.

Design thinking: An iterative approach involving empathising, defining, ideating, prototyping, and testing.

Double Diamond: A model of discover, define, develop, and deliver, showing cycles of divergence and convergence.

Lean UX: A collaborative, outcome-oriented approach that tests assumptions through rapid learning cycles.

Agile discovery: Continuous research and validation conducted alongside iterative product delivery.

Persona: A research-informed representation of a meaningful user group.

Journey map: A representation of stages, actions, perceptions, touchpoints, and pain points in an experience.

Service blueprint: A map connecting user actions with frontstage interactions, backstage processes, systems, and support.

Value proposition: A statement of the value a product offers to a defined user group and why it is preferable to alternatives.

Hypothesis: A testable statement about a user, behaviour, problem, or expected outcome.

Minimum viable product: The smallest coherent product or experiment capable of testing an important value assumption.

Desirability: The extent to which users need, want, or value a proposed solution.

Viability: The extent to which a solution can support a sustainable organisational model.

Feasibility: The extent to which a solution can be built and operated with available resources and technology.

KPI: A measurable indicator used to assess progress toward an important objective.

Accessibility: The ability of people with diverse abilities to perceive, understand, navigate, and use a product.

Goodhart’s law: The warning that a measure can become unreliable when it is made the target of optimisation.

Review Questions

Short Answer Questions

1. Distinguish between a user need, a problem, and a solution assumption.

2. What are the four modes represented by the Double Diamond?

3. Why should prototype fidelity correspond to the uncertainty being investigated?

4. Define a value proposition and identify two questions it should answer.

5. Why is usability only one dimension of user experience?

Long Answer Questions

1. Explain how design thinking and Lean UX can be used together in an agile product team.

2. Discuss how UX research can influence product strategy rather than merely improve interface design.

3. Explain the relationship between strategic objectives, product outcomes, user behaviour, and UX metrics.

4. Analyse the role of service blueprinting in digital transformation projects.

5. Discuss the ethical responsibilities involved in UX research, analytics, personalisation, and AI-supported design.

Analytical / Application Questions

1. A bank proposes a mobile application because customers frequently call its contact centre. Design a discovery plan that tests whether the proposed app addresses the underlying problem.

2. An online government service has a high completion rate but disproportionately high abandonment among users with disabilities. Which evidence, metrics, and design actions should the team prioritise?

3. A product team wants to release an AI-based recommendation feature but has limited evidence of user value. Use desirability, viability, feasibility, ethics, and experimentation to recommend a staged strategy.

22. Multiple Choice Questions with Answers

Question 1

A team discovers that users requesting a mobile app are actually struggling to understand application eligibility. What is the most human-centred response?

A. Build the mobile app immediately because it was requested.

B. Reframe the problem around understanding eligibility and investigate suitable solutions.

C. Ignore the request because users should not suggest solutions.

D. Add more features to the existing application without research.

Correct Answer: B. Reframe the problem around understanding eligibility and investigate suitable solutions.

Question 2

Which activity best represents convergence in the Double Diamond?

A. Interviewing a wide range of users to explore contexts

B. Generating many possible concepts without evaluation

C. Prioritising evidence into a focused design challenge

D. Collecting unrestricted stakeholder suggestions

Correct Answer: C. Prioritising evidence into a focused design challenge

Question 3

A prototype is being used to determine whether users understand the navigation structure. Which prototype is generally most appropriate initially?

A. A high-performance production system

B. A paper or low-fidelity clickable representation

C. A complete back-end implementation

D. A final visual design with no interaction

Correct Answer: B. A paper or low-fidelity clickable representation

Question 4

Which statement best describes a Lean UX hypothesis?

A. A guaranteed prediction of market success

B. A list of features requested by senior management

C. A testable statement linking a user, behaviour, intervention, and expected outcome

D. A technical specification for database implementation

Correct Answer: C. A testable statement linking a user, behaviour, intervention, and expected outcome

Question 5

Why might a high time-on-task measure indicate a UX problem rather than success?

A. Users may be confused or encountering unnecessary steps.

B. Time-on-task is always unrelated to user behaviour.

C. Longer task time always proves greater engagement.

D. The measure can only be used for marketing pages.

Correct Answer: A. Users may be confused or encountering unnecessary steps.

Question 6

In the scholarship case, why was a responsive web service prioritised over a native mobile application?

A. Native applications cannot support accessibility.

B. The evidence indicated a cross-platform task-completion need rather than a need for a specific app format.

C. Responsive websites never require technical integration.

D. Mobile applications are unsuitable for all university services.

Correct Answer: B. The evidence indicated a cross-platform task-completion need rather than a need for a specific app format.

Question 7

Which combination most accurately represents the three strategic lenses used in UX decision-making?

A. Speed, popularity, and visual quality

B. Desirability, viability, and feasibility

C. Revenue, advertising, and market share only

D. Coding, testing, and deployment

Correct Answer: B. Desirability, viability, and feasibility

Question 8

A team has extensive interview transcripts but cannot explain what decision the research changed. What is the main weakness?

A. The team has too much technical feasibility evidence.

B. The research has not been synthesised into actionable insights.

C. The team should eliminate qualitative research.

D. The team should replace interviews with a logo redesign.

Correct Answer: B. The research has not been synthesised into actionable insights.

Question 9

Which KPI structure is most appropriate for an accessible public-service application?

A. Only page views and advertising impressions

B. Only average session duration

C. Successful completion, accessibility performance, errors, support demand, and equitable outcomes

D. Only the number of features released

Correct Answer: C. Successful completion, accessibility performance, errors, support demand, and equitable outcomes

Question 10

What is the most responsible use of AI in UX research?

A. Allowing an AI system to make final decisions about user needs without review

B. Uploading confidential research data to any public tool for convenience

C. Using AI to assist synthesis while preserving source evidence, reviewing bias, and protecting data

D. Treating AI-generated summaries as more reliable than participant evidence

Correct Answer: C. Using AI to assist synthesis while preserving source evidence, reviewing bias, and protecting data