How does a designer move from a brief to a viable product, and why is the process iterative rather than linear?
The design process and the iterative design, make and test cycle: the brief, research, specification, idea generation, development, prototyping, evaluation and the feedback loops that link them.
An SQA Higher Design and Manufacture answer on the design process and the iterative design, make and test cycle, covering the brief, research, specification, idea generation, development, prototyping and evaluation, and why the stages feed back into each other rather than running in a straight line.
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 key area is asking
The SQA wants you to explain how a designer works from a starting brief to a viable design proposal, naming the stages of the design process and, crucially, explaining why it is iterative: the stages feed back into each other in a design, make and test cycle rather than running once in a straight line. In the question paper this appears as "explain" or "describe" items worth 3 to 6 marks, and the whole process underpins the design assignment.
The stages of the design process
The stages are linked, and a designer moves back and forth between them rather than ticking them off in order:
- The brief. A short statement of the problem or need, often agreed with a client. It says what is wanted but usually not how to achieve it, leaving the designer free to explore.
- Research. Gathering information to understand the problem: studying the users (their needs, sizes and abilities), the market (price points, competitors), existing products (what works and what fails) and the materials and processes available.
- The specification. A measurable list of requirements drawn from the brief and research. Each point should be testable, for example "must cost under 20 pounds to manufacture" or "must support a load of 15 kg".
- Idea generation. Producing a wide range of possible solutions quickly, often as freehand sketches, so options are not closed off too soon.
- Development. Taking the strongest ideas and refining them: working out dimensions, materials, joints and details, and combining the best features of several ideas.
- Modelling and prototyping. Making models or working prototypes to test ideas in three dimensions before committing to manufacture.
- Evaluation. Judging ideas and prototypes against the specification and through user testing, then feeding the findings back into the design.
Why the order matters but is not fixed
The stages have a logical order (you cannot evaluate against a specification you have not yet written), but the process is not a one-way street. Research can continue throughout, the specification is often revised as understanding grows, and evaluation happens at every stage, not just at the end.
Why the process is iterative
There are two main reasons the work loops:
- Testing reveals problems that were hidden on paper. A sketch may look fine, but a foam model can show the handle is the wrong size, or a working prototype can show a joint is too weak. The designer returns to development or idea generation to fix the fault, then tests again.
- Information and requirements change. User feedback or new research can change the specification, which forces earlier decisions to be revisited. The specification is a living document, not a one-time list.
Each pass through the cycle reduces risk and uncertainty, so by the time the design is committed to manufacture the major problems have already been found and solved cheaply on models rather than expensively on tooling.
Where this fits in the course
This key area is the backbone of the Design area of the course and of the design assignment, where you must show a genuine design, make and test process: researching, writing a specification, generating and developing ideas, modelling and evaluating. The question paper also asks about it directly, so being able to name the stages and explain the feedback loops earns marks in both components.
Try this
Q1. Describe the stages a designer follows from receiving a brief to producing a design proposal. [4 marks]
- Cue. Brief, research, specification, idea generation, development, modelling/prototyping, evaluation - and note that the stages link rather than run once.
Q2. Explain why a designer makes models and prototypes during development. [3 marks]
- Cue. They test ideas in three dimensions, reveal problems hidden on paper, and let faults be fixed cheaply before tooling is ordered.
Q3. Explain why the specification is revisited during the design process. [3 marks]
- Cue. Research and user feedback change what the product must do, so the specification is updated, which forces earlier decisions to be reviewed - part of iteration.
Exam-style practice questions
Practice questions written in the style of SQA exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.
SQA Higher4 marksExplain why the design process is described as iterative.Show worked answer →
Worth about 4 marks, so the marker wants two developed reasons, each a
point plus a consequence. The mark scheme rewards the idea that the
process loops back on itself, not just a list of stages.
Testing reveals problems. When a designer makes a model or prototype and
tests it against the specification, faults appear that were not obvious on
paper, for example a handle that is uncomfortable or a joint that is too
weak. The designer returns to the development or idea-generation stage to
fix them, so the work cycles rather than runs in a straight line.
Requirements change as understanding grows. Research and user feedback at
one stage often change the specification, which forces earlier decisions
to be revisited. Each loop refines the proposal and reduces risk before
expensive tooling is committed.
A strong answer states that iteration produces a better, more viable
product because errors are caught early and the design is improved with
every cycle.
SQA Higher3 marksDescribe the purpose of writing a design specification before generating ideas.Show worked answer →
Worth about 3 marks. The markers want the function of the specification,
not just a definition.
It sets measurable targets. The specification turns the brief and
research into a checklist of requirements (size, materials, cost, safety,
performance) that ideas must meet, so the designer has clear criteria to
design against.
It guides idea generation. Because the specification lists what the
product must do, it focuses creativity on solutions that are viable and
keeps out ideas that cannot meet the constraints.
It is the yardstick for evaluation. Later, ideas and prototypes are judged
against the specification, so writing it first makes objective evaluation
possible. A top answer notes that without it, evaluation becomes a matter
of opinion.
Related dot points
- The design factors a product must satisfy: function and performance, aesthetics, ergonomics and anthropometrics, the market, economics and cost, ease of manufacture, durability and safety, and how they are balanced and prioritised.
An SQA Higher Design and Manufacture answer on the design factors a product must satisfy, covering function and performance, aesthetics, ergonomics and anthropometrics, market, economics, ease of manufacture, durability and safety, and how a designer balances and prioritises them for a viable commercial product.
- Graphic techniques and modelling used through the design process: freehand sketching, pictorial and orthographic working drawings, CAD, and physical models and prototypes, and the role of each in generating, developing, testing and communicating a design.
An SQA Higher Design and Manufacture answer on the graphic techniques and modelling used through the design process, covering freehand sketching, pictorial and orthographic working drawings, CAD, and physical models and prototypes, and when each is used to generate, develop, test and communicate a design.
- Evaluation techniques used through the design process: evaluating ideas and products against the specification, user trialling and testing, comparison and selection methods, and using the results to refine the design.
An SQA Higher Design and Manufacture answer on evaluation techniques, covering how a designer judges ideas and products against the specification, uses user trialling and testing, compares and selects ideas objectively, and feeds the results back to refine the design.
- Overview of the Higher Design and Manufacture coursework assignment: a candidate-led design, make and test task that applies the design process and knowledge of materials and manufacture to produce and evaluate a design proposal and outcome.
An SQA Higher Design and Manufacture overview of the coursework assignment, a candidate-led design, make and test task that applies the design process and knowledge of materials and manufacture to research, develop, make and evaluate a design proposal under SQA conditions.