Design processes The use of a design process - The iterative design process in industrial or commercial contexts — AQA A-Level Design and Technology: Product Design
Verified courseTeaching note checked against the official specification.
Design processes The use of a design process - The iterative design process in industrial or commercial contexts explained
Commercial design is rarely a lone designer's straight line from brief to shelf.
Read the full explanation
Corporate teams choose a methodology to suit risk, budget and timescale. A staged approach such as a design brief, research, specification, concept generation, development, prototyping, testing and launch gives structure, while iterative working loops back when testing exposes a fault. Collaborative working spreads expertise: a design engineer, ergonomist, marketing specialist and manufacturing engineer may review the same concept, so decisions are shared and checked. The cyclic nature means manufacture and user feedback feed the next revision, so a product is refined across versions rather than fixed at launch. Discuss how these methodologies differ in purpose and effect, using a named product context to show iteration and collaboration in action.
Your focus
- Explain how at least two design methodologies are applied by corporate designers.
- Describe collaborative working and the cyclic nature of commercial design and manufacture with a product example.
- Evaluate the effects of iterative working on a commercial product's development.
Design processes The use of a design process - The iterative design process in industrial or commercial contexts exam tips
Marking Points
- Explains at least two distinct design methodologies used in corporate contexts and contrasts their purpose or suitability.
- Describes collaborative working, naming the roles or disciplines involved and the benefit of shared review.
- Explains the cyclic nature of commercial design and manufacture, showing how testing, manufacture or user feedback returns to earlier stages.
- Applies the discussion to a concrete product or company context rather than describing the process abstractly.
- Evaluates consequences, such as how iteration affects cost, timescale, quality or risk.
- Reaches a supported judgement about why a chosen methodology suits a particular commercial situation.
Examiner Tips
- 💡Anchor each methodology to a real product or company so the discussion stays concrete.
- 💡Use a diagram-style description of the loop to make the cyclic nature explicit in words.
- 💡Reserve time to state a judgement about which methodology suits which commercial situation and why.
Common Mistakes
- Treating the design process as a single linear sequence: correct this by showing the feedback loops that return to research, specification or concept stages.
- Describing collaboration as simply 'working as a team' without naming disciplines: correct this by identifying specific roles and what each contributes.
- Assuming iteration always improves a product: correct this by weighing benefits against added cost and delay.