3.3.6 Prototype development sits in AQA GCSE Design and Technology under Designing and making principles. At this point in the course, students need to show that ideas are not just sketched and admired from a safe distance. They need to be developed into prototypes that respond clearly to client wants and needs.
This topic matters because it connects design decisions, practical making, testing, and evaluation. It is useful for written exam answers, but it is especially important in coursework-style thinking, where students must justify how a prototype has been improved, refined, and made more fit for purpose. This page helps teachers explain the specification precisely, teach it in a classroom-ready way, and mark responses with confidence.
At a Glance
🧭 Specification snapshot
Subject: Design and Technology
Qualification: GCSE
Curriculum: AQA
Specification point: 3.3.6 Prototype development
What students must know: A prototype can be a product or a system and should be developed in response to client wants and needs.
Key exam focus: How development decisions improve function, usability, aesthetics, and suitability for the intended user.
Common student challenge: Students often describe what a prototype looks like, rather than explaining how it has been developed and why that development matters.
Understanding the Topic
Prototype development is about turning ideas into a workable outcome that can be tested, evaluated, and improved.
What the specification is really asking for
- Students should understand that a prototype is more than an early sketch or a rough model.
- In AQA language, the prototype may be a product or a system.
- The prototype should be developed in response to client wants and needs.
- Development should involve decision-making, testing, feedback, and refinement.
- Students should be able to explain why changes were made, not just state that changes happened.
What teachers should emphasise
- A prototype must connect directly to the design brief.
- Development should improve one or more of the following:
- function
- usability
- aesthetics
- accuracy
- user suitability
- manufacturability
- Good prototype development is usually iterative. Students test something, learn from it, then adjust it.
- The strongest answers link every modification back to the client or the intended user.
A simple way to frame it for students
A useful classroom sentence is:
A prototype is developed when a designer makes deliberate changes to improve how well a product or system meets the client’s wants and needs.
That wording helps students avoid vague comments such as “it was changed to make it better”, which is technically true but not very mark-friendly.
Key Terms and Concepts
| Term | Explanation |
|---|---|
| Prototype | A developed version of a design idea used to test, evaluate, and demonstrate how a product or system will work. |
| Client wants | Preferences the client would like the outcome to include, such as style, colour, or additional features. |
| Client needs | Essential requirements the product or system must meet in order to function successfully. |
| Iteration | Repeated improvement based on testing, feedback, or review. |
| Evaluation | Judging how well a prototype performs against the design brief, specification, or user requirements. |
| Refinement | Making specific changes to improve performance, appearance, accuracy, or user experience. |
| Function | How well the prototype does its intended job. |
| Aesthetics | The visual appearance of the prototype, including style, form, colour, and finish. |
| Ergonomics | How comfortably and efficiently a user can interact with the prototype. |
| Testing | Checking performance in a structured way to identify strengths, weaknesses, and next improvements. |
How to Teach This Topic
Teaching moves
- Start with a design brief and ask students to identify the client’s non-negotiables.
- Show a rough idea, then a developed prototype, and ask: What changed, and why?
- Use quick comparison tasks where students decide whether a feature is responding to a want or a need.
- Model how testing leads to refinement. For example, “The handle slipped in use, so the grip texture was changed.”
- Encourage students to justify changes using sentence stems such as:
- “This was developed so that…”
- “This better meets the client’s need for…”
- “Testing showed that…”
Useful classroom prompts
- Which part of this prototype clearly responds to the client’s needs?
- Which improvement is functional, and which is aesthetic?
- What evidence would justify this development decision?
- If the prototype failed during testing, what should be refined next?
- How would the answer change if the client were a different user group?
💡 Teacher tip
Ask students to annotate prototype images with three headings: change made, reason for change, and benefit to the user. This keeps explanations specific and stops answers drifting into generic product description.
Helpful teaching sequence
- Define the design brief and user needs.
- Introduce an initial idea or model.
- Identify weaknesses through testing or feedback.
- Develop the prototype with clear modifications.
- Evaluate whether the new version better meets the brief.
Scaffolding ideas
- Give weaker students a partially completed sentence grid linking problem, change, and benefit.
- Use before-and-after prototype photos so students can practise explaining development decisions.
- Ask students to sort statements into description or justification.
Extension activities
- Ask students to rank prototype changes from most important to least important and defend the order.
- Set a mini brief where students redesign a classroom item for a specific client and explain three prototype refinements.
- Use peer critique to generate third-party feedback for further development.
How to Mark This Topic Effectively
Strong responses do not simply identify features. They explain how prototype development improves the outcome for a user or client.
| What strong answers include | What weaker answers often do |
|---|---|
| Clear reference to the client, user, or design brief | Talk about the product in general terms with no user focus |
| Specific development decisions | List features without explaining any change |
| A reason why the change improves function, usability, or aesthetics | Use vague phrases such as “makes it better” or “looks nicer” |
| Evidence from testing, feedback, or evaluation | Ignore how the prototype was reviewed or refined |
| Relevant technical vocabulary | Rely on everyday language that lacks precision |
✅ Marking guidance
Reward answers that make a clear chain of logic:
development decision
reason linked to client wants or needs
benefit to function, usability, or quality
Common mistakes to watch for when marking
- Confusing a model with a prototype.
- Describing the final product without explaining how it was developed.
- Giving aesthetic comments only, with no reference to function.
- Mentioning testing without showing what changed as a result.
- Naming a client need but not linking the design change to it.
What examiners tend to reward
- Direct answers to the wording of the question.
- Specific examples rather than generic statements.
- Logical explanation of why a refinement improved the design.
- Awareness that prototype development is responsive and iterative.
Example Student Responses
Example question
Question: Explain two ways a designer could develop a prototype so that it better meets client wants and needs. [4 marks]
Marking guidelines
- Award up to 2 marks per explained development.
- A typical full-mark point includes:
- one clear development decision
- one linked explanation of how it better meets the client’s wants or needs
Strong response
The designer could add a textured grip to the handle because testing showed that the prototype was difficult to hold securely. This would better meet the client’s need for safety and ease of use. The designer could also reduce the size of the product so it fits into the storage space the client asked for. That change responds directly to the client’s need for practicality in a small room.
Why this is strong
- Gives two clear developments.
- Links each one to a specific client need.
- Explains the benefit of each change.
- Uses evidence from testing in a relevant way.
Weak response
The designer could change the handle and make the product smaller. This would improve it and make it better for the client. The prototype would also look nicer and work well.
Why this is weak
- Mentions changes, but the explanation is too vague.
- Does not clearly identify the client’s wants or needs.
- Uses weak phrases such as “make it better”.
- Gives little detail about why the changes improve the prototype.
Practice Questions
- Identify one reason why a designer might test a prototype before final manufacture. [2 marks]
- Marking guidance: reward identification of testing and a linked reason such as checking function, safety, size, or user suitability.
- Explain how feedback from a client could influence prototype development. [4 marks]
- Marking guidance: reward explanation of a change made because of feedback and how it better meets wants or needs.
- Analyse how prototype development can improve both function and aesthetics. [6 marks]
- Marking guidance: expect balanced analysis, specific examples, and clear links to design decisions.
- Evaluate the importance of refining a prototype after testing. [8 marks]
- Marking guidance: reward judgement, use of evidence, consideration of user needs, and explanation of consequences if refinement does not happen.
📝 Quick revision use
These questions work well as:
do-now retrieval tasks
paired discussion prompts
mini whiteboard practice
exit-ticket exam practice
Common Misconceptions
- “A prototype is just a sketch.”
- Correction: A sketch communicates an idea. A prototype is a developed version used for testing and evaluation.
- “If it looks good, it is a strong prototype.”
- Correction: A strong prototype must meet the client’s needs in function as well as appearance.
- “Development happens once at the end.”
- Correction: Prototype development is usually iterative and should respond to testing and feedback.
- “Client wants and client needs mean the same thing.”
- Correction: Needs are essential requirements. Wants are preferences that improve appeal or suitability.
- “Testing is separate from development.”
- Correction: Testing should lead directly to development and refinement.
FAQ
How is a prototype different from a model?
A model is often used to explore or communicate an idea. A prototype is usually more developed and is used to test how well a product or system works in relation to the brief.
Do students need to mention both wants and needs in every answer?
Not always. However, strong answers usually make it clear whether a development responds to an essential need, a preferred feature, or both.
What is the most common weakness in student answers on this topic?
Students often describe features without explaining why the feature was developed or how it improves the design for the client.
Should students refer to testing in prototype development answers?
Yes, where relevant. Testing gives a reason for change, which makes the explanation stronger and more convincing.
What vocabulary helps students sound more precise?
Useful terms include prototype, iteration, refinement, evaluation, ergonomics, function, aesthetics, client brief, and user needs.
Save time on the marking that follows
🚀 Marking.ai helps teachers turn student responses into faster, more consistent marking with clear feedback. Once students have practised explaining prototype development, it can help you review the quality of their answers and spot where explanation, justification, or technical vocabulary still needs work.