Skip to main content
SingaporeDesign and TechnologySyllabus dot point

Why do designers loop back through earlier stages, and how does iteration improve a design over several cycles?

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.

Generated by Claude Opus 4.87 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

SEAB wants you to explain that designing is iterative: designers loop back through earlier stages instead of moving once through a straight line. You should be able to describe how testing and evaluation produce feedback that feeds into development, why catching faults early is cheaper and less risky, and how a design improves across several cycles. This idea sits at the heart of both the written paper and the Design Project.

The answer

What "iterative" means

Iterative means repeating. An iterative design process is one in which the designer travels through stages such as develop, model, test and evaluate, then loops back to develop again, going round the cycle several times. Each pass is an iteration. The process is not a one-way line from idea to product; it is a loop the designer travels until the solution is good enough.

The feedback loop

The engine of iteration is feedback. When a prototype is tested or evaluated against the specification, the results reveal what works and what does not. Those results are feedback, and they feed back into an earlier stage, usually development. The designer modifies the design to fix the problems, makes a new prototype, and tests again. Test, learn, change, repeat.

How each cycle refines the design

A first attempt almost always has faults: a weak joint, an awkward grip, a part too large, a cost too high. The first iteration fixes the most serious faults. Testing the improved version often reveals smaller problems, which the next iteration addresses. Over several cycles the design converges on a solution that meets the specification. The final product is therefore the result of accumulated improvements, not a single lucky guess.

Why early iteration is cheaper and safer

Fixing a fault in a prototype is cheap: you change a model or remake one item. Fixing the same fault after manufacture is expensive: every unit already made shares the fault, so the maker may have to scrap a batch, re-tool, and recall products, all while losing the trust of users. Iteration front-loads the problem-finding into cheap prototypes, which is why designers test thoroughly before committing to production.

Where iteration appears in your project

In the Design Project, iteration is visible in the Design Journal: early ideas are developed, modelled and tested, and the journal records how feedback led to changes. Examiners look for evidence of real iteration, where a problem found in testing clearly drove a specific improvement, rather than a tidy straight line from first idea to final product.

Examples in context

Example 1. A reusable shopping bag handle. A first handle is comfortable empty but cuts into the hand when the bag is heavy. Testing with a loaded bag is the feedback; the next iteration widens the handle and adds padding; re-testing confirms comfort under load. Two cycles turn an idea that failed under real use into one that meets the specification.

Example 2. A toy for a toddler. Safety testing of a first prototype finds small parts that could come loose, a serious fault. The iteration redesigns the parts to be larger and permanently fixed, and the new prototype passes the safety test. Finding the fault in a prototype rather than in sold toys avoids a costly and dangerous recall, showing why early iteration matters.

Try this

  • Cue. Define "iteration" in the design process. Answer: repeating a cycle of develop, model, test and evaluate, looping feedback from testing back into development to refine the design over several passes.

  • Cue. A prototype torch is bright but the switch is hard to find in the dark. Describe one iteration. Answer: loop back to development, redesign the switch to be larger or raised so it can be felt in the dark, make a new prototype, and re-test in darkness.

  • Cue. Give one reason designers test prototypes before manufacturing. Answer: to find and fix faults while they are cheap to fix in a single prototype, rather than after they have been repeated in a whole production batch.

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 student designing a pencil case tests a first prototype and finds the zip jams and the case is too small. Using the idea of iteration, describe what the student should do next and explain why working this way produces a better final design.
Show worked answer →

The student should treat the test results as feedback and loop back to the development stage rather than carrying on to the final product. They would modify the design to fix the two faults: choose a smoother or larger zip and a better seam to stop the jam, and increase the internal dimensions so the case holds the intended contents. They would then make and test a second prototype, check it against the specification, and repeat if new problems appear.

Working iteratively produces a better final design because each cycle removes faults that testing reveals. Problems are caught and fixed in cheap prototypes rather than in a finished, mass-made product, and the design steadily improves until it meets the specification, instead of relying on the first attempt being perfect.

What markers reward: looping back to development with specific fixes for both faults, making and re-testing a new prototype, and the reasoning that iteration fixes faults early and refines the design over cycles.

Original4 marksExplain why it is cheaper and less risky to discover a design fault during prototyping than after a product has been manufactured.
Show worked answer →

During prototyping a fault can be fixed by changing a sketch, a model or a single prototype, which costs little time and few materials. After manufacture, the same fault is repeated in every unit made, so fixing it may mean scrapping or recalling a whole batch, re-tooling, and re-making, which is expensive and damages the maker's reputation.

Catching faults early through iteration therefore reduces both cost and risk: each loop through develop, model and test removes problems while they are still cheap to remove. This is why designers test prototypes thoroughly before committing a design to production.

What markers reward: the contrast between fixing one prototype versus a whole production batch, the costs of re-tooling and recall, and the link to iteration catching faults while they are still cheap to fix.

Related dot points