What are the stages of the design process, and why do designers move through them in a structured but iterative way?
Describe the stages of the design process from identifying a situation to evaluating a solution, and explain why the process is iterative rather than strictly linear
A focused answer to the O-Level Design and Technology outcome on the design process. The stages from situation and brief to research, ideas, development, realisation and evaluation, and why the process loops back.
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 describe the stages of the design process in order, from first identifying a situation and a user need through to evaluating a finished solution, and to explain why designers treat the process as iterative: a loop they travel several times rather than a one-way line. You should be able to name each stage, say what happens in it, and show how the stages connect.
The answer
The design process is a structured method
Designing is not guessing. The design process is a structured sequence of stages that takes a designer from a real problem to a tested solution. Working through the stages makes sure the final product actually meets a genuine need, is properly researched, and has been improved before it is made. In Design and Technology you use this same process in the Design Project and you are asked to explain it in the written paper.
The stages in order
A common version of the process, suited to O-Level, runs through these stages:
- Identify the situation and need. Recognise a problem and the people affected by it. State what the user actually needs.
- Write the design brief. A short statement of what is to be designed and for whom, setting the direction.
- Research and investigate. Gather evidence: study users, existing products, materials and measurements (anthropometric and ergonomic data).
- Write the specification. Turn the research into a list of clear, measurable requirements the solution must meet.
- Generate ideas. Produce a wide range of possible solutions, usually as annotated sketches.
- Develop and refine. Take the strongest idea and improve it, testing each change against the specification.
- Realise the prototype. Plan and make a working model or product using suitable materials and processes.
- Test and evaluate. Test the prototype against the specification and the user, identify improvements, and feed them back in.
Why the order matters
Each stage feeds the next. Without a clear need, the brief is vague; without research, the specification is guesswork; without a specification, you cannot judge whether an idea is any good. Skipping research or specification is the most common reason a project drifts and a product fails to meet the user.
Why the process is iterative
The arrows do not only point forward. When testing reveals a problem, the designer loops back to an earlier stage, usually development, and tries again. This looping is what "iterative" means. Each cycle improves the design, so the final solution is the product of several refinements. Problems caught early, on paper or in a model, are far cheaper to fix than problems found in a finished product.
Examples in context
Example 1. A folding study table for a small bedroom. The designer starts from the situation (a student with little floor space), researches room sizes and user posture, writes a specification (must fold flat to under 100 mm, support a laptop and books, set up in under 30 seconds), generates ideas, develops a hinge mechanism, builds a prototype, then finds in testing that the hinge wobbles and loops back to strengthen it. The iterative loop turns a shaky first idea into a stable product.
Example 2. A water bottle for cyclists. Research into how cyclists drink while riding sets requirements for one-handed opening and a secure cage fit. Several ideas are sketched, one is developed and modelled, user testing on a real bike shows the cap is hard to open with sweaty hands, and the design loops back to a textured, larger cap. Evaluation against the specification confirms the final design works.
Try this
Cue. List the eight stages of the design process in order. Answer: situation and need, brief, research, specification, ideas, development, realisation, evaluation. Check you have included specification and evaluation, the two most often forgotten.
Cue. Explain why a designer writes a specification before generating ideas. Answer: the specification turns research into measurable targets, so ideas can be judged and compared against clear requirements rather than personal preference.
Cue. Define "iterative" in the context of the design process. Answer: the designer loops back through earlier stages (especially development) whenever testing reveals a problem, refining the design over several cycles rather than moving once through a straight line.
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 marksA school canteen needs a better way for students to carry a tray, a drink and a bag at the same time. (a) Identify the design situation and the need. (b) List, in order, the stages a designer would work through to solve this problem.Show worked answer →
(a) The situation is the crowded canteen where students struggle to carry several items at once; the need is a product that lets a student carry a tray, a drink and a bag together safely and comfortably.
(b) A sensible order of stages: identify the situation and need; write a design brief; carry out research and investigation; write a specification; generate a range of ideas; develop and refine the best idea; model and realise a prototype; test and evaluate it against the specification, then loop back to improve.
What markers reward: a clearly named situation and a need stated as a user requirement (not just "a tray holder"), and the stages listed in a logical order that includes specification, development and evaluation, not only "design" and "make".
Original5 marksExplain, with reference to the design process, why a designer rarely moves straight from the first idea to the final product. Use the word 'iterative' in your answer.Show worked answer →
The design process is iterative, meaning a designer loops back through earlier stages rather than moving once through them in a straight line. A first idea is tested against the specification and almost always reveals problems: a part may be weak, too costly, hard to make, or uncomfortable to use. The designer returns to development to modify the idea, models and tests again, and repeats until the solution meets the specification.
This looping matters because problems are cheaper and easier to fix on paper or in a model than in a finished product. Each cycle of develop, model, test and evaluate improves the design, so the final product is the result of several refinements, not a single lucky guess.
What markers reward: correct use of "iterative" as looping back through stages, the idea that testing reveals problems that feed back into development, and the reason that fixing faults early is cheaper and produces a better final solution.
Related dot points
- Analyse a design situation to identify the user, the problem and the needs and wants, and distinguish a need from a proposed solution
A focused answer to the O-Level Design and Technology outcome on analysing a situation. Identifying the user, the problem, needs versus wants, and why a need must be stated separately from any solution.
- Write a clear design brief from an analysed situation, and turn research into a measurable design specification against which solutions can be judged
A focused answer to the O-Level Design and Technology outcome on briefs and specifications. What a design brief states, how a specification is written as measurable points, and how the two differ.
- Explain the iterative nature of designing, where evaluation and testing feed back into earlier stages, and describe how each cycle refines a solution
A focused answer to the O-Level Design and Technology outcome on iteration. How testing and evaluation feed back into development, why early loops are cheaper, and how cycles refine a design.
- Develop and refine a chosen idea through annotated sketches, modelling and testing, justifying each change against the specification
A focused answer to the O-Level Design and Technology outcome on development. Refining a chosen idea through annotated sketches, modelling and testing, with each change justified against the specification.
- Evaluate a product or prototype systematically against each point of the design specification, reaching evidenced judgements and identifying improvements
A focused answer to the O-Level Design and Technology outcome on evaluation. Judging a product point by point against the specification, using evidence, and identifying improvements.