Design process and problem solving
What this domain tests
The design process section rewards candidates who show a structured, iterative response to a real need rather than one clever idea. Examiners look for a clear brief, an analysed context, a measurable specification, evidence of research, developed ideas and evaluation against the specification.
Core sequence
- Brief and analysis: identify the user, need, constraints and context; write a short problem statement.
- Specification: turn the brief into measurable criteria. ACCESSFM (Aesthetics, Cost, Customer, Environment, Size, Safety, Function, Material) is a useful checklist.
- Research: existing products, users, materials, standards; record sources.
- Ideation and development: several annotated concepts, then select using criteria; develop the chosen idea with dimensions and materials.
- Prototype, test, evaluate: compare results with the specification and state the next iteration.
Worked example
Brief: a lunchbox for a 7-year-old to carry to school. Specification criteria: capacity at least 1.2 L; empty mass under 350 g; latch survives 5,000 open-close cycles; food-contact material; cost under €4 at 10,000 units; no sharp edges; printed outer surface wipes clean. Two concepts are scored against weighted criteria: a hinged polypropylene clamshell scores higher than a fabric bag because it meets the rigidity and cleaning criteria, although the bag wins on mass. The chosen design is tested by a 1 m drop test and a latch cycling rig. Evaluation notes the latch failed at 3,200 cycles, so the catch is thickened and retested.
Traps
- Writing a specification of vague wishes (“strong”, “nice”) instead of numbers.
- Giving one idea and calling it development.
- Evaluating against personal opinion rather than the specification.
- Confusing the brief (what is needed) with the specification (how success is measured).