How does a designer take a promising idea and refine it, step by step, into a workable solution?
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.
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 take a chosen idea and develop it into a workable solution through annotated sketches, modelling and testing, justifying each change against the specification. Development is the stage where a rough idea becomes a detailed, refined design. The marks reward reasoned refinement, where each improvement is driven by a test result or specification point, not by redrawing the same idea more neatly.
The answer
What development is
Development takes one promising idea (chosen at the selection stage) and refines it into a solution that meets the specification. It is the bridge between a rough first sketch and a finished prototype. Development is iterative: the designer improves the idea, tests it, and improves again. Crucially, development is about making the idea better, not just drawing it more tidily.
Annotated detail sketches
The main tool of development is the annotated sketch. The designer draws parts of the idea in detail (the joints, the compartments, the mechanism) and writes notes explaining each decision: why this size, this material, this method. Annotation turns a picture into a worked-out design and forces the designer to think through problems on paper, where they are cheap to fix. Good development sketches explore alternatives and show reasoning.
Modelling to develop in three dimensions
Flat sketches hide problems that appear in three dimensions. Modelling, with card, foam, clay or simple prototypes, lets the designer test size, proportion, fit and function physically. A slot that looks fine on paper may be too small for a real phone; a model reveals it. Modelling at the development stage catches such problems before time is spent on a final prototype.
Testing and refining against the specification
As the idea develops, the designer tests it against the specification and the user, then refines it. A compartment too small is enlarged; a shelf that sags is strengthened; a part too costly is simplified. Each change should be driven by a finding and checked against the specification. This is the iterative loop in action: develop, test, refine, repeat, until the design meets every requirement.
Justifying every change
The mark of strong development is justification. Each change should be explained against the specification or a test result: "I widened the base because the specification requires it not to tip when loaded." Justified development keeps the design on target and makes every decision defensible to a marker or client. Unjustified changes ("made it bigger because I felt like it") look arbitrary and earn little.
Examples in context
Example 1. Developing a children's stacking toy. Annotated sketches detail the peg sizes and colours; a foam model reveals the pegs are too thin for small hands to grip, so they are thickened (justified by the ergonomic specification point and the model finding). Further testing shows sharp edges, which are rounded for safety. Each refinement traces to a finding, turning a rough idea into a safe, usable toy.
Example 2. Developing a tool rack. A first sketch hangs tools on hooks; modelling shows heavy tools pull the rack off the wall, so the fixing is strengthened and the heavy tools moved to a lower slot (justified by the load and stability requirements). Detail sketches then work out the slot sizes for each tool. The developed rack meets the specification because every change answered a tested problem.
Try this
Cue. State the three main activities of the development stage. Answer: producing annotated detail sketches, modelling, and testing against the specification then refining.
Cue. Explain why annotation is important on development sketches. Answer: it explains the reasoning behind each decision, turning a picture into a worked-out, defensible design and forcing problems to be thought through on paper.
Cue. Give a justified change for a stool found to wobble in testing. Answer: widen the leg spread or add a cross-rail because the specification requires it to be stable under load, and testing showed it wobbled.
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 has chosen a basic idea for a bedside organiser and must now develop it. Describe three things the student should do during the development stage, and explain how each improves the design.Show worked answer →
Three development activities:
- Produce annotated detail sketches that explore parts of the idea (the compartments, the joints, the size), explaining each decision. This turns a rough idea into a worked-out design and exposes problems early.
- Make models or prototypes (card or foam) to test size, proportion and function in three dimensions. Modelling reveals issues a flat sketch hides, such as whether a phone actually fits a slot.
- Test the developing design against the specification and improve it, for example resizing a compartment that is too small or strengthening a weak shelf. Each change is justified by a test result or specification point.
What markers reward: three distinct development activities (detailed annotated sketching, modelling, testing and refining), each linked to a clear improvement, showing development as reasoned refinement rather than redrawing the same idea.
Original4 marksExplain why every change made during development should be justified against the design specification.Show worked answer →
Justifying each change against the specification keeps development focused on meeting the user's real requirements rather than the designer's whims. The specification is the agreed list of what the product must do, so checking each change against it ensures the design is moving toward a solution that will pass evaluation, not drifting away from the target.
It also makes the development defensible: a marker (or a client) can see why each decision was made. "I widened the base because the specification requires it not to tip" is a justified change; "I made it bigger because I felt like it" is not. Justified development produces a design that demonstrably meets its requirements.
What markers reward: the idea that the specification is the target, that checking changes against it keeps development on track toward passing evaluation, and that justification makes each decision defensible rather than arbitrary.
Related dot points
- Use idea-generation techniques such as brainstorming, mind mapping, morphological analysis and SCAMPER to produce a wide range of design ideas
A focused answer to the O-Level Design and Technology outcome on generating ideas. Brainstorming, mind mapping, morphological analysis and SCAMPER, and why a wide range of ideas matters.
- Evaluate and select the best idea by judging each against the design specification, using methods such as a weighted evaluation matrix
A focused answer to the O-Level Design and Technology outcome on choosing ideas. Judging ideas against the specification, using an evaluation matrix with weighting, and justifying the choice objectively.
- Use models and prototypes, from quick study models to working prototypes, to test ideas in three dimensions and gather evidence for refinement
A focused answer to the O-Level Design and Technology outcome on modelling. Study models, mock-ups and working prototypes, the materials used, and how models test ideas and gather evidence.
- 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.
- Write a justified design specification from research findings, covering function, ergonomics, materials, safety, cost and aesthetics, with measurable points where possible
A focused answer to the O-Level Design and Technology outcome on specifications. Building justified, measurable specification points from research across function, ergonomics, materials, safety, cost and aesthetics.