The Design Process: how N(A)-Level Design and Technology students move from a design situation to a brief, a specification and a finished, evaluated product

What this module covers

The Design Process is the backbone of N(A)-Level Design and Technology (SEAB 7055): it is the method you follow in the Design Project, and it is tested directly in the written paper. The process turns a messy real-world situation into a clear problem, then into ideas, a made product and an honest evaluation. This module has three dot points that cover the ordered stages, how to write a design brief, and how to write a specification you can later test against. Getting these right early protects the whole project, because every later stage depends on a clear brief and a measurable specification.

See the full set of dot points for this module under /sg-n-level/design-and-technology/syllabus/the-design-process.

The stages of the design process

The stages of the design process dot point sets out the ordered route from a design situation to a finished, evaluated product: situation, brief, research, specification, ideas, development, planning and making, then testing and evaluation. Each stage produces something concrete, a brief is a statement of the problem, a specification is a list of requirements, and so on. Crucially, the process is a loop, not a straight line: when testing reveals a fault you go back and improve the idea, which is what designers mean by iterative design.

Writing a design brief

Writing a design brief turns a given design situation into a short, focused statement of what to design. A good brief names the intended user, states the problem or purpose, and hints at a key requirement, without listing detailed measurements (those belong in the specification). Because the user shapes every later decision, naming them keeps the project anchored to a real need.

Writing a design specification

Design specifications takes the research findings and turns them into a list of clear, measurable requirements covering function, size, materials, safety, cost and appearance. The power of a measurable specification appears at the end of the project: it becomes a checklist for testing the finished product, where each point gives a clear pass or fail rather than an opinion.

How this module is examined

• Know the order. You may be asked to list the stages in sequence and state what one or two of them produce.
• Separate brief and specification. A brief states what to design and for whom; a specification lists measurable, testable points.
• Write measurable points. Specification points must be checkable with a measurement or a yes/no test, never vague opinions.
• Explain the loop. Be ready to say why the process is iterative, with an example of going back to improve a design after testing.

Check your knowledge

Short questions across the module. Attempt them, then check the worked solutions.

1. List, in order, the main stages of the design process from situation to evaluation. (3 marks)
2. State the difference between a design brief and a design specification. (2 marks)
3. Decide whether each belongs in the brief or the specification: "design a tidy case for a student's pens"; "must be no longer than 200 mm". (2 marks)
4. Explain why the design process is drawn as a loop rather than a straight line. (2 marks)
5. Give one reason a design brief should name the user. (1 mark)