Design Methodology and Project Process: Brief, Research, Ideation, Prototyping
This domain tests the project process: interpreting a brief, researching, generating and selecting ideas, sketching, prototyping, evaluating, and communicating a solution. The exam rewards evidence of a reasoned process, not a single beautiful final drawing.
The process
- Brief: identify client, user, context, constraints, deliverables, budget, and success criteria. Restate the problem in one sentence and list what is fixed versus open.
- Research: gather user needs, precedents, technical requirements, and regulations. Use observation, interviews, personas, journey maps, and benchmarking.
- Ideation: diverge before converging. Use brainstorming, mind maps, morphological charts, SCAMPER, and quick thumbnails. Defer judgement during divergence.
- Selection: define criteria such as feasibility, cost, usability, sustainability, and originality; score options against them.
- Prototyping: low-fidelity first (paper, card, foam, wireframes), then higher fidelity. Test with real users and record failures.
- Evaluation and communication: compare results with the brief; present process, evidence, and final proposal.
The Double Diamond model describes diverge-converge twice: discover/define, then develop/deliver. It is a map, not a rigid sequence; iteration is expected.
Worked example
Brief: a reusable cup for a music festival, sold at €8, stackable, branded, and washable on site. Research shows people abandon cups when queues are long and cups do not fit holders. Constraints: food-safe material, 300 ml, existing washing racks. Ideation produces three concepts: collapsible silicone, rigid polypropylene with a lid, and a deposit-return cup with a clip. Criteria scoring favours rigid PP: stackable, dishwasher-safe, cheap, and brandable. Prototype in card and then 3D print; test grip, stack height, and washing-rack fit. Evaluation reveals the lid is unnecessary; remove it to cut cost and material. Final presentation shows sketches, decision matrix, prototype photos, and test findings.
Traps
Do not jump from brief to final idea. Do not write a vague brief that cannot be evaluated. Do not prototype only at the end. Do not hide failed tests; examiners value evidence of iteration. Do not present a solution without linking it back to user needs and constraints.