Needs, wants and opportunities in QCE Design Unit 3
“Identifying and analysing needs, wants and opportunities - the difference between an expressed want, an underlying need and a latent opportunity, how empathy data is gathered and analysed to surface them, and how this analysis frames the human-centred design problem in the explore phase”
A want is what a person says they would like, a need is the underlying requirement that the want points to, and an opportunity is an unmet or latent gap a designer can address. Human-centred design treats needs as a higher priority than wants, because solving the stated want often misses the real problem. You surface all three by gathering empathy data through interview, observation and immersion, then analysing it - grouping findings, separating expressed from latent, and tracing each want back to the need beneath it. This analysis frames the design problem and feeds straight into the design brief and criteria. Markers reward needs that are evidenced by data, not assumed.
Jump to a section
What this dot point is asking
QCAA wants you to be able to identify and analyse the needs, wants and opportunities of an identified person or group, and to do it from data rather than guesswork. This sits at the front of the explore phase in Unit 3 human-centred design. The marks come from showing that you can tell an expressed want apart from a deeper need, that you used real empathy data to find them, and that your analysis defined the right design problem before any ideas appeared.
The answer
Why this distinction matters
The most common reason a human-centred design fails is that the designer solved the want the user named instead of the need underneath it. The classic illustration is the user who asks for a faster horse: the want is a faster horse, the need is to travel further in less time, and the opportunity is a new mode of transport. If you only hear the want, you never reach the opportunity. QCAA frames Unit 3 around exactly this discipline - putting human needs above other influences.
Wants
A want is the surface-level, expressed preference - what the person tells you they would like. Wants are easy to collect because people volunteer them, but they are shaped by what the person already knows exists. A want is a clue, not an instruction. Treating every want as a literal specification produces incremental, unimaginative designs.
Needs
A need is the underlying requirement that the want is trying to satisfy. Needs are more stable than wants and more revealing. They come in layers:
- Expressed needs - stated directly, similar to wants but framed as a requirement.
- Observed needs - revealed by what a person does, which often differs from what they say.
- Latent needs - real but unspoken, because the person has normalised a frustration or cannot articulate it.
Latent needs are where the strongest design opportunities hide, and they are only reachable through careful empathy research, not a single survey question.
Opportunities
An opportunity is the gap a designer chooses to act on - an unmet need, an underserved situation, or a frustration nobody has solved well. Identifying an opportunity is a decision: from all the needs you uncover, you select the one that is most worth solving for this person in this context. A well-chosen opportunity is specific, evidenced and meaningful to the identified user.
Using data, not assumption
QCAA is explicit that analysis must rest on data. You gather empathy data through interview (open "why" questions, likes and dislikes), observation (watching the person in their real context), and immersion or experiences (simulating the person's situation, such as wearing gloves to mimic reduced grip). You then analyse that data rather than leaping to a solution:
- Group and cluster related findings to see patterns.
- Separate expressed from latent - what was said versus what was revealed.
- Trace wants to needs - for each want, ask what underlying need it serves.
- Prioritise the needs that matter most to the user.
The output is a defensible statement of the need and the opportunity, each backed by a specific piece of evidence.
How this frames the design problem
The analysed need and chosen opportunity become the foundation of the design problem statement, the design brief and the design criteria. Every later decision - ideation, prototyping, the resolved proposal - should trace back to a need you evidenced here. A marker reading your folio checks that the line from "this person needs X, shown by Y" to "my design does Z" is unbroken.
Worked example
Identified user: a one-handed cook recovering from a stroke.
Want (expressed in interview): "I want a lighter chopping knife."
Observation: the user struggles not with the knife weight but with the board sliding while they cut, because they cannot hold it steady with the other hand.
Latent need (revealed, not stated): a way to stabilise food preparation with a single hand.
Opportunity chosen: a one-handed food-preparation surface, not a lighter knife.
The analysis - clustering the interview want against the observed behaviour - shows the real need was stability, not weight. Designing a lighter knife would have answered the want and missed the need entirely. The folio quotes the observation as evidence, which is what lifts this from assumption to data-driven analysis.
A want is what a person says they would like, a need is the underlying requirement beneath it (expressed, observed or latent), and an opportunity is the unmet gap a designer chooses to address. Human-centred design prioritises needs over wants, surfaces them from interview, observation and immersion data, and uses the analysis to frame the design problem, brief and criteria.
- Designing the want, not the need
- Taking a stated preference as a literal specification produces shallow designs and misses the real opportunity.
- Assuming the need instead of evidencing it
- Every need in the folio should point to a specific interview quote, observation or immersion finding. Unevidenced needs read as guesswork.
- Stopping at expressed needs
- The richest opportunities are latent - normalised frustrations the user never mentions. Observation and immersion reach them; a survey rarely does.
- Choosing a vague opportunity
- "Make cooking easier" is not an opportunity. A specific, evidenced gap for a specific user is.
- Never returning to the analysis
- If your resolved design cannot be traced back to a need you identified here, the human-centred thread is broken.
Exam-style questions
Questions in the style of QCAA exam questions on this dot point, each with a worked answer. They are written by ExamExplained unless tagged "Past paper"; the year shows the paper a question is modelled on.
Practice8 marksUsing the stimulus, analyse the data about an identified person to distinguish an expressed want, an underlying need and a latent opportunity, and explain how this analysis frames the human-centred design problem.Show worked answer →
An 8 mark analyse-and-explain answer rewards correctly separating the three and showing how they frame the problem.
Analyse: an expressed want is what the user asks for (a bigger cup holder); the underlying need is the deeper requirement behind it (to keep a drink secure while moving); a latent opportunity is an unmet possibility the user has not articulated (a spill-proof, one-handed solution that also frees a hand). Use evidence from the stimulus to justify each label rather than asserting it.
Explain: framing the problem around the underlying need and latent opportunity, not the surface want, opens a wider and more innovative solution space. Markers reward analysis grounded in the data and a problem statement that targets need and opportunity rather than the literal want.
Practice6 marksEvaluate the risk of designing directly for an expressed want rather than analysing the underlying need. Justify your reasoning with an example.Show worked answer →
A 6 mark evaluate answer needs a judgement supported by reasoning.
Evaluate: solving the expressed want alone often produces a literal but shallow response that misses the real problem; users frequently ask for a faster horse when they need faster transport. Designing for the want can also lock in the user's own assumptions and foreclose better solutions.
Justify: analysing the underlying need reframes the problem and exposes latent opportunities, yielding more innovative, human-centred responses. Markers reward recognising the want-versus-need gap, an apt example, and a clear conclusion that analysis of need should drive the brief.