Skip to main content
SingaporeDesign StudiesSyllabus dot point

What are the stages designers move through to turn a problem into a resolved design?

Describe the stages of the design process - empathise, define, ideate, prototype and test - and explain why it is iterative rather than linear

A focused answer on the design process for O-Level Design Studies. The stages of design thinking from empathise to test, why the process is iterative and cyclical, and how each stage feeds the next.

Generated by Claude Opus 4.88 min answer

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

Have a quick question? Jump to the Q&A page

Jump to a section
  1. What this dot point is asking
  2. The answer
  3. Examples in context
  4. Try this

What this dot point is asking

This dot point asks you to describe the stages of the design process and explain why it is iterative. Design thinking is a structured, human-centred way of solving problems, usually described in five stages: empathise, define, ideate, prototype and test. You should be able to name the stages, say what happens at each, and explain that the process loops back on itself rather than running once in a straight line. The big idea is that good design is a disciplined, repeatable process, not a single flash of inspiration, and that working in loops produces better, better-tested outcomes.

The answer

Empathise: understand the user

The process begins with understanding the people the design is for. Designers observe, ask questions, and put themselves in the users' position to learn their real needs, behaviours and frustrations. Empathy keeps the design grounded in genuine human needs rather than the designer's assumptions.

Define: frame the problem

Research is then interpreted to write a clear, specific problem statement. A good definition focuses the work: instead of "make a better water bottle", it might be "help busy commuters drink more water during the day". A sharp problem statement makes the later stages far more productive.

Ideate: generate ideas

With the problem defined, designers generate as many ideas as possible. The aim is quantity and range, deferring judgement so unusual ideas are not killed too early. Techniques such as brainstorming, sketching and mind-mapping help diverge widely before converging on the strongest directions.

Prototype: make it tangible

The most promising ideas are turned into rough, quick prototypes - sketches, paper models, mock-ups - cheap enough to change or throw away. Prototyping makes an idea tangible so it can be examined and tested, revealing problems that are invisible on paper.

Test: learn and refine

Prototypes are tested with real users to see what works and what does not. The feedback is the point: it tells the designer what to keep, change or rethink. Testing often sends the designer back to an earlier stage, which is exactly how the design improves.

Why it is iterative, not linear

Although the stages are usually listed in order, designers loop back constantly. Testing may reveal that the problem was defined wrongly, sending the team back to define or empathise; ideation may need to start again. Each loop refines the design, so problems are caught early and the final outcome is far stronger than a single first attempt. The process is best pictured as a cycle, not a one-way line.

Examples in context

Example 1. A public transport app. A team empathises by watching commuters miss connections, defines the problem as confusing route information, ideates many interface ideas, prototypes screens on paper, and tests them with travellers. Early tests send them back to redefine, and after several loops the app shows the next service clearly, illustrating the full cycle.

Example 2. Redesigning a confusing form. Faced with a form people fill in wrongly, a designer empathises by watching users struggle, defines the unclear questions as the problem, ideates clearer wording and layout, prototypes a revised form, and tests it. The error rate drops only after iterating, showing why repetition, not a single redraft, produces the fix.

Try this

  • Cue. Pick an everyday frustration (a hard-to-open package, a confusing sign) and write a one-sentence problem statement for it as you would in the define stage. Check that it focuses on the user's need, not a solution.

  • Cue. For that problem, list ten possible ideas in five minutes without judging any of them. Notice how deferring judgement lets you reach more unusual ideas than stopping at the first good one.

  • Cue. Describe a time you improved something over several attempts. Map your attempts onto the prototype-test-refine loop and explain how iterating produced a better result than your first try.

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 marksOutline the five stages of the design thinking process and, for each, state in one sentence what a designer does.
Show worked answer →
  1. Empathise. The designer researches and observes the users to understand their needs, behaviours and frustrations.

  2. Define. The designer interprets the research to frame a clear, specific problem statement that the design must solve.

  3. Ideate. The designer generates a wide range of possible ideas and solutions without judging them too early.

  4. Prototype. The designer turns the most promising ideas into rough, testable models or mock-ups.

  5. Test. The designer tries the prototypes with users, gathers feedback, and uses it to refine or rethink the design.

What markers reward: the five stages in a sensible order, a correct one-line description of the activity at each stage, and language that shows understanding rather than copied labels.

Original4 marksExplain why the design process is described as iterative rather than linear, and give one benefit of working this way.
Show worked answer →

The design process is iterative because designers move back and forth between stages and repeat the cycle, rather than completing each stage once in a straight line. Testing a prototype often sends the designer back to ideate or even to redefine the problem, and a design usually improves over several loops.

One benefit: problems and weaknesses are found and fixed early through repeated testing and refinement, so the final design is better resolved and more likely to meet users' real needs than a single first attempt.

What markers reward: the idea of looping back and repeating stages (not a one-way sequence), and a clear benefit such as catching problems early, improving through feedback, or reducing the risk of a flawed final design.

Related dot points