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

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