Design process and problem solving
What the domain tests
The Design process and problem solving domain examines whether you can move from an identified need to a justified solution. Expect questions on design briefs, specifications, idea generation, modelling, testing and evaluation, and on how constraints such as cost, safety, materials and user needs shape decisions. The process is iterative: evidence from testing should send you back to earlier stages, not merely confirm a chosen idea.
Core rules and concepts
- A design brief states the problem and intended user; a specification converts it into measurable requirements.
- Research should separate facts, user opinions and assumptions.
- Generate several distinct concepts before detailed development; annotate sketches with function, materials and dimensions.
- Use models and tests to answer specific questions, not just to make a display model.
- Evaluate against the specification and record modifications.
Worked example
A candidate must design a desk holder for a solar study lamp. The brief is “hold the lamp securely at a useful angle for a learner.” A weak spec says “make it strong.” A stronger spec states: supports 0.8 kg; lamp angle adjustable through 30–60°; base footprint under 180 × 120 mm; stable when pushed sideways; low-cost local materials; no sharp edges. Two concepts-a plywood wedge and a bent-wire frame-are modelled. A sideways push test shows the wedge tips, so the base is widened and rubber feet added. The evaluation cites the measured angle range and stability test, then notes that cable routing still needs improvement.
Traps that cost marks
Do not present one idea as the whole process. Avoid unmeasurable specifications (“attractive”, “easy to use”) unless you define how they will be judged. Do not ignore a constraint you listed earlier. Evaluation must refer to evidence and the spec, not personal preference.