What are the stages of the design process in O-Level Design Studies?

The design process is usually taught as a cycle of five stages: empathise (understand the user and the problem), define (write a clear brief and specification), ideate (generate many ideas through sketching and brainstorming), prototype (build rough models to make ideas testable), and test (try the design with users and evaluate it against the specification). The key point for NP05 is that it is iterative, not linear: testing feeds back into earlier stages, so a designer loops through these steps several times, refining the design each time rather than completing them once in order.

What is the difference between a design brief and a design specification?

A design brief is the starting statement of the problem: it says who the design is for, what it must achieve and roughly the context, but it is often broad and a little vague. A design specification comes after research and turns the brief into a precise, testable list of requirements, such as size, materials, budget, target audience, function and the success criteria the final design must meet. In short, the brief frames the problem and the specification defines exactly what a successful solution looks like, so you can later judge the design against it.

Why do designers prototype before making a final product?

Prototyping lets a designer fail fast and cheaply. Building a rough, low-fidelity model (paper, card or a quick mock-up) makes an abstract idea something you can hold, show to users and test, which exposes problems early while they are still easy and inexpensive to fix. Catching a flaw on a paper prototype costs almost nothing; finding the same flaw after a product is manufactured is far more costly. Prototypes turn opinions into evidence and drive the iteration that improves the design.

Why is the design process described as iterative rather than linear?

It is iterative because designing is a loop of learning, not a one-way checklist. When you test a prototype you learn things that send you back to ideate again, redefine the specification, or even re-empathise with users you misread. Each pass through the cycle improves the design, so a designer expects to repeat the stages several times. Treating the process as linear (research once, design once, make once) is a common O-Level mistake, because it leaves no room to act on feedback.

How does the design process support the Design Project coursework in NP05?

The Design Project is essentially the design process made visible. The design journal documents each stage - research and brief, the specification, idea sketches, chosen concept, prototypes, testing and evaluation - so the examiner can see your design thinking and how you responded to feedback. Showing genuine iteration, where testing clearly changed your design, is what distinguishes a strong project from one that simply records a single idea taken straight to a finished outcome.

SingaporeDesign Studies

The Design Process: O-Level Design Studies (NP05) module overview, from the design brief and research through ideation, specifications, prototyping and testing to iteration

A module overview of the Design Process for O-Level Design Studies (NP05): how a designer moves from a brief and research, through ideation, a written specification and prototypes, to testing and iteration. Covers why the process is cyclical rather than linear and how each stage feeds the next, the backbone of the Design Project coursework.

Generated by Claude Opus 4.89 min readSEAB-NP05Updated 2026-06-13

Reviewed by: AI editorial process; not yet individually human-reviewed

Jump to a section

How the design process fits together
The design thinking process
Research and the design brief
Design specifications and constraints
Ideation and sketching
Prototyping and mock-ups
Testing, evaluation and iteration
A worked walkthrough: a reusable shopping bag
How the design process is examined
Check your knowledge

How the design process fits together

The design process is the spine of O-Level Design Studies (NP05). It is the structured way a designer moves from a fuzzy problem to a resolved, tested solution, and it underpins both the written paper and the Design Project coursework, where your design journal records each stage. The single most important idea is that the process is iterative, a cycle you travel round several times, rather than a straight line you walk once. Each pass teaches you something that improves the next.

This module covers every stage in turn, each with its own focused page and practice questions. See the full set at /sg-o-level/design-studies/syllabus, and the strands below.

The design thinking process

Everything starts with a mental model of the whole cycle. The design thinking process walks through the five stages - empathise, define, ideate, prototype and test - and explains why the process is iterative rather than linear. Knowing the shape of the cycle lets you place every other skill in this module: research belongs to empathise and define, sketching to ideate, mock-ups to prototype, and user feedback to test.

Research and the design brief

A designer cannot solve a problem they do not understand. Research and the design brief covers reading and interpreting a brief, the difference between primary research (gathering new information yourself, such as user interviews or surveys) and secondary research (using existing sources), plus user research, market research and visual research with mood boards. The brief frames who the design is for and what it must do; research fills in the detail you need before you design anything.

Design specifications and constraints

Research is turned into a precise target by the specification. Design specifications and constraints shows how to write a design specification with measurable success criteria, and how constraints such as budget, time, materials and audience shape your decisions. A good specification is testable: later you can hold the finished design up against it and judge, point by point, whether it succeeds.

Ideation and sketching

With a clear target, you generate options. Ideation and sketching covers brainstorming, mind-mapping and SCAMPER, thumbnail sketches and annotation, and why designers deliberately produce a wide range of ideas before committing to one. Quantity first, then judgement: generating many quick, annotated ideas surfaces better solutions than polishing the first idea that comes to mind.

Prototyping and mock-ups

Ideas become testable when you build them. Prototyping and mock-ups explains the purpose of prototypes, the difference between low-fidelity (rough, quick, cheap) and high-fidelity (detailed, closer to the final) prototypes, and the principle of failing fast and cheap. A paper prototype made in minutes can reveal a flaw that would be expensive to fix later.

Testing, evaluation and iteration

Finally, you find out whether the design works and use that to improve it. Testing, evaluation and iteration covers user testing, evaluating against the specification, gathering qualitative and quantitative feedback, and acting on it. The crucial distinction is between feedback (evidence about how the design performs against criteria) and mere opinion, and between changing the design because of evidence and changing it on a whim.

A worked walkthrough: a reusable shopping bag

Seeing the cycle applied to one brief makes it concrete.

Designing a reusable shopping bag for families

step Empathise and research

The brief asks for a reusable shopping bag aimed at families. You interview a few parents (primary research) and look at bags already on sale (secondary and visual research). You learn that bags tear at the handles, are awkward to carry when full, and are forgotten at home.

step Define the specification

From the research you write testable criteria: must carry at least 10 kg without the handles failing, must fold small enough to keep in a handbag, must cost under a set budget, must use a durable, washable material, and must appeal to families. These success criteria let you judge the final design objectively.

step Ideate

You sketch a wide range of thumbnails - tote shapes, fold-flat designs, clip-on handles, bright family-friendly prints - and annotate each with its pros and cons against the specification, rather than settling on the first idea.

step Prototype

You make a low-fidelity paper-and-fabric mock-up of the most promising fold-flat design. It is rough, but it shows the folding mechanism and rough proportions for a few cents of materials.

step Test and iterate

You ask parents to fold and load the prototype. The handles dig into hands when the bag is full, so you go back to ideate, widen the straps, and prototype again. The second test passes the load and comfort criteria. The loop, not the first idea, produced the working design.

How the design process is examined

Know the cycle and that it is iterative. Be able to name the stages, say what a designer does at each, and explain why testing feeds back into earlier stages rather than ending the process.
Distinguish brief, research and specification. The brief frames the problem, research informs the design, and the specification turns both into testable success criteria.
Show, do not just describe. In the Design Project, the design journal must make your iteration visible: testing should clearly change your design, not just decorate a single fixed idea.

Check your knowledge

A mix of recall and application questions covering the design process. Attempt them under timed conditions, then check against the solutions.

Name the five stages of the design process and, for each, state in one sentence what a designer does. (5 marks)
Explain the difference between a design brief and a design specification. (2 marks)
Explain the difference between primary and secondary research, with one example of each. (2 marks)
Explain why designers generate many ideas before choosing one. (2 marks)
Explain the difference between a low-fidelity and a high-fidelity prototype. (2 marks)
Explain why the design process is described as iterative rather than linear. (2 marks)

Solutions

Q1: Empathise: understand the user and the problem through research. Define: write a clear brief and a testable specification. Ideate: generate a wide range of ideas through sketching and brainstorming. Prototype: build rough models so ideas can be tested. Test: try the design with users and evaluate it against the specification.
Q2: The brief states the problem broadly (who it is for and what it must achieve); the specification, written after research, turns the brief into a precise, testable list of requirements and success criteria against which the final design is judged.
Q3: Primary research is new information you gather yourself, for example interviewing parents about a shopping bag; secondary research uses existing sources, for example reading reviews of bags already on sale. Both inform the design before you start.
Q4: Generating many quick, annotated ideas explores a wider range of possible solutions and surfaces stronger options, whereas polishing the first idea risks committing to a weak solution before better ones are considered.
Q5: A low-fidelity prototype is rough, quick and cheap (such as a paper mock-up) and is used early to test concepts; a high-fidelity prototype is detailed and close to the final product, used later to test look, feel and function more precisely.
Q6: Because testing produces feedback that sends the designer back to earlier stages to refine the design, so the stages are repeated in a loop rather than completed once in order; treating it as linear leaves no room to act on feedback.

Sources & how we know this

Singapore-Cambridge GCE O-Level Design Studies (NP05) syllabus — Singapore Examinations and Assessment Board (2026)