What are the ordered stages of the design process, and why does following them lead to a better product?
Describe the stages of the design process from a design situation to a finished product, and explain why the process is a loop rather than a straight line
A clear, step-by-step answer to the N(A)-Level D&T outcome on the design process. The ordered stages from situation to evaluation, what each stage produces, and why designers loop back to improve their work.
Reviewed by: AI editorial process; not yet individually human-reviewed
Have a quick question? Jump to the Q&A page
Jump to a section
What this dot point is asking
SEAB wants you to know the design process as an ordered set of stages, to say what each stage produces, and to explain why designers treat it as a loop they can step back through rather than a one-way line. This is the backbone of the whole subject: your coursework follows these stages, and the written paper asks you to name them and use them.
The answer
The stages in order
The design process turns a problem into a tested product. The usual stages, in order, are:
- Design situation. The starting point: a real context where a need or problem exists, for example "students have nowhere tidy to keep stationery on a small desk".
- Design brief. A short written statement of the problem and who it is for. It says what you are going to design and why.
- Research and investigation. Gathering information: what users need, what similar products already do, and what materials or sizes suit the task.
- Specification. A list of clear, measurable points the product must meet, drawn from the research.
- Generating ideas. Producing several different initial ideas as quick sketches with notes.
- Developing and refining. Choosing the most promising idea and improving it with reasons, often using models.
- Planning and making. Working out the steps, tools and materials, then making the product safely and accurately.
- Testing and evaluation. Checking the finished product against the specification and suggesting improvements.
What each stage produces
Each stage hands something concrete to the next. The brief produces a problem statement; research produces evidence; the specification produces a checklist; idea generation produces sketches; development produces a chosen, improved design; making produces the product; evaluation produces a judgement and ideas for improvement. If a stage produces nothing useful, the next stage has nothing to work with.
Why it is a loop, not a line
The process is iterative. That means you can return to an earlier stage when you learn something new. If a model fails a test, you loop back to development. If the specification turns out to be unrealistic, you revisit it. Looping back is not a mistake; it is how a design gets better. This is why the process is drawn with arrows that can go backwards.
Examples in context
Example 1. A desk tidy. The situation is a cluttered desk. The brief is to design a tidy for pens and small items. Research shows common pen sizes and what users dislike about existing tidies. The specification fixes a footprint and a number of compartments. Ideas are sketched, one is developed, a card model is tested, the tidy is made, then evaluated against the specification.
Example 2. A phone stand. A maker jumps straight to making without research and produces a stand that tips over. Returning to the development stage with a wider base fixes it. This shows the value of looping back rather than keeping the first attempt.
Try this
Q1. Put these four stages in the correct order: specification, design brief, research, generating ideas. [2 marks]
- Cue. Design brief, research, specification, generating ideas. The specification is built from the research, so it comes after it.
Q2. State what the designer produces at the testing and evaluation stage. [1 mark]
- Cue. A judgement of how well the product meets the specification, plus suggested improvements.
Q3. Explain, with an example, why a designer might return to an earlier stage. [3 marks]
- Cue. Because the process is iterative. For example, a test shows the product is too heavy, so the designer returns to development to choose a lighter material before making the final version.
Exam-style practice questions
Practice questions written in the style of SEAB exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.
Original6 marksList the main stages of the design process in the correct order, from being given a design situation to finishing the product. For any two of the stages, state what the designer produces at that stage.Show worked answer →
A correct order: (1) design situation, (2) design brief, (3) research and investigation, (4) specification, (5) generating ideas, (6) developing and refining the chosen idea, (7) planning and making, (8) testing and evaluation.
Two outputs, for example: the design brief stage produces a short written statement of the problem and who it is for; the specification stage produces a list of measurable points the product must meet.
What markers reward: the stages in a sensible order, and correct outputs named for the chosen stages (a brief is a statement of the problem; a specification is a list of requirements). Small wording differences are accepted if the order and meaning are right.
Original4 marksExplain why the design process is often drawn as a loop with arrows that go backwards, rather than a straight line.Show worked answer →
The design process is iterative, which means a designer often returns to an earlier stage after learning something new. For example, when testing a model you may find a fault, so you go back to develop the idea again before making the final product. Looping back lets you improve the design instead of being stuck with the first attempt.
What markers reward: the word iterative or the idea of returning to earlier stages; a clear example of going back (such as test results sending you back to development); and the reason, which is that revisiting stages improves the final product.
Related dot points
- Write a clear design brief from a given design situation, stating the problem, the intended user and the purpose of the product
A practical answer to the N(A)-Level D&T outcome on writing a design brief. How to read a design situation, identify the problem and the user, and write a short brief that sets the direction for the project.
- Write a design specification as a list of clear, measurable requirements drawn from research, and use it to guide and later test the design
A focused answer to the N(A)-Level D&T outcome on writing a specification. How to turn research into measurable requirements covering function, size, materials, safety, cost and appearance, and how the specification is used to test the product.
- Generate a range of different initial ideas in response to a specification, using techniques such as brainstorming and thumbnail sketches
A clear answer to the N(A)-Level D&T outcome on generating initial ideas. Techniques such as brainstorming, mind maps and thumbnail sketches, how to stay creative, and how to annotate ideas so they earn marks.
- Test a finished product against each point of the specification and record clear pass or fail results
A focused answer to the N(A)-Level D&T outcome on testing a product. How to turn each specification point into a fair test, record clear pass or fail results, and use them to judge whether the product solved the problem.
- Analyse a design situation to identify the key problems, the people affected, and the questions research must answer
A clear answer to the N(A)-Level D&T outcome on analysing a design situation. How to break a situation into the problem, the people and the constraints, and turn it into research questions before you start designing.