2.20445 · Section 2: Preparing for the project (Component 2)

Research and specification

Key learnings

Research every aspect of the brief
Investigate every aspect of the brief, not just what is easy to find: existing similar products; the user; the environment of use (indoors/outdoors, wet, portable); materials and processes; ergonomics and anthropometrics; cost; and safety/standards. Each area must be relevant to THIS brief — pages of generic material or tool research add little. Research that misses a whole aspect leaves gaps that weaken the specification.
User needs — real client, primary data
A brief has two sides: the design need (the problem) and the user needs (what the specific people who will use the product require). Strong work considers BOTH in detail; work that describes the problem but never investigates the user stays in the lower band. Name a real client or user group and gather PRIMARY data — interview or survey them, and measure them or their space for ergonomic data — so the specification genuinely fits the user.
Analyse data, don't just present it
Gathering data is only half the job — the marks come from analysing it. Analysing means drawing a CONCLUSION from the information (a majority, a trend, a pass or fail against a target) and saying what it means for the design. A survey table with no conclusion under it is only presented, not analysed. Simple arithmetic helps: turning "39 of 60 users" into "65%" makes the majority clear. Present, conclude, then convert it into a specification requirement.

Common mistakes

Drawn from real examiner reports.

Only the design need researched

A recurring weakness is treating the brief as only a problem statement, never investigating the user. Candidates write what the product must do but never find out who the users are, what they prefer, or their sizes, so the specification cannot be tied to real user needs. Considering BOTH the design need AND the user needs reaches the higher band; only the problem stays low.

s23 P02 AC1 · w23 P02 AC1

Generic research, not brief-relevant

Quantity is mistaken for quality. Candidates copy pages of generic information — material properties, tool lists — with little to do with the actual problem, and it scores little. Research is judged on RELEVANCE to the brief, not volume. What earns marks is targeted primary research about the user and context. Check: for every piece, ask which spec point it will justify.

s23 P02 AC2

Vague, unjustified spec points

The definition trap: specification point vs a JUSTIFIED one. Each point should be specific, measurable, and justified — tracing back to a research finding. Weak specs use generic words like "nice" or "cheap" that fit any product and are not testable, so they gain little. Turn each finding into a point like "light enough for a 6-year-old to lift", not "must be light".

s23 P02 AC2

Copying the brief as the specification

A common confusion: writing the brief out as the specification. The brief is a short problem statement; the specification is a detailed list of justified requirements drawn from the RESEARCH. Copying the brief adds no researched detail and scores little. The specification must add specific, measurable points — sizes, materials, cost, safety — each justified from a finding.

Specification never reused later

The specification is not a box to tick and forget — it is reused across the whole project. During development, ideas are judged against it; during evaluation, the product is tested against each point. Candidates who write a specification then ignore it lose those marks. This is why every point must be specific and testable — a vague one cannot judge an idea or test a product.

w23 P02 AC2

Only secondary research, no user data

Some folders rely entirely on secondary sources — internet pages, textbook data — and never gather first-hand data from the actual users. Examiners expect PRIMARY research: interviews, surveys and measuring the users. Secondary research helps compare existing products, but without primary user data the specification rests on assumptions, not evidence.

w23 P02 AC2

Brief and specification are the same

A sharp confusion: treating brief and specification as interchangeable. The brief is a SHORT statement of the problem — what, for whom, why. The specification is a DETAILED list of measurable, justified requirements written AFTER research. The brief says what problem and for whom; the specification says exactly what the solution must do and be.

Analysing just means making a chart

A common wrong belief: that drawing a chart or table counts as analysing the data. It does not — that is only presenting it. Analysing means drawing a CONCLUSION: reading what the data tells you (the majority, a trend, a pass or fail) and saying what it means for the design. Charts with no conclusions under them are unanalysed, and the reasoning marks are missed.

Exam tips

Justify every spec point from research
Write each specification point so it is specific and measurable (a size, mass or target) AND justified, saying which research finding it comes from. A strong point reads finding, then requirement, then reason. Do not repeat the brief or write generic points.
Cover both design need and user
Consider BOTH sides of the brief — the design need and the user needs — and gather primary data on the users. Folders that investigate only the design need stay in the lower band; the higher band needs evidence about the specific user feeding the specification.
State the conclusion, then the point
For each research finding, write the conclusion it leads to, then the specification requirement it justifies — do not leave raw data. Simple arithmetic sharpens the conclusion: "39 of 60 users" becomes "65%", a clear majority. Present, conclude, then specify.
Write points you can test later
Make every specification point testable — a defined size, mass or cost — because the same specification is reused to judge ideas in development and to test the product in evaluation. A generic point like "must be nice" cannot be tested, so it is useless later and scores little.

Revision notes