Notes · Design and TechnologyUK · A-Levels

Design methods and processes

This chapter sets out how designing is actually done: the iterative process of exploring, creating and evaluating in cycles; identifying needs and writing briefs and specifications; researching users and products; generating and developing ideas; and modelling, prototyping, testing and evaluating. It is the methodological heart of the subject and the backbone of the NEA.

5 sections~17 min reading time3 competenciesLevel Standard 4 · Advanced 1

T·0999 / 18

Exam profile

AO1 · Identify, investigate and outline design possibilities and write a brief and specificationAO2 · Design, develop and prototype solutions that are fit for purposeAO3 · Analyse and evaluate design decisions and outcomes throughout the iterative process

Operators:explaindescribeidentifygeneratedevelopevaluatejustify

basic level

AS-Level expects the design process understood and applied - a brief, a specification, ideas, a model and an evaluation.

higher level

The full A-Level expects genuinely iterative working, a rigorous specification, well-evidenced research, and testing and evaluation that drive real improvement - as demonstrated in the NEA.

Depth

Text

Contents · 5 sections

Design methods and processes

The iterative design process#

AdvancedAQA 7552 3.2.1DfE GCE D&T - design methods and processes

The iterative design process

Fig. 1The iterative design process as a cycle of exploring, creating and evaluating: identify and research the need, specify it, generate and develop ideas, prototype and test them, evaluate, and loop back - each pass refining the design.

Modern designing is iterative: it proceeds through repeated cycles of exploring, creating and evaluating, rather than in a single straight line from problem to solution. A designer explores the problem and users, creates and develops ideas and models, evaluates them against the need, and then loops back to explore and create again in the light of what was learned - refining the design through many cycles. Iteration is what makes a design converge on a genuinely good solution.

This contrasts with the older linear (or waterfall) model, in which each stage is completed once and the process runs straight through - identify, research, specify, design, make, evaluate - with the evaluation coming only at the end. The linear model is simple but risky: a problem found at the end is expensive to fix and there is little chance to improve. Iterative working catches problems early and repeatedly and treats evaluation as continuous, not final.

A full cycle typically moves through identifying and exploring the need, researching users and products, writing a specification, generating ideas (ideation), developing and modelling the best, prototyping and testing them, and evaluating against the specification - and then round again. Crucially the loop is not one-way: testing may send the designer back to develop, evaluation back to research, so the process is genuinely cyclical, with each pass improving the design.

Iterative design is central to the NEA and to how professional designers work, because it builds evaluation and user feedback into every stage and so produces solutions that really fit the need. A candidate demonstrates it by showing repeated cycles of trying, testing and improving - not a single tidy run from brief to product. Evidence of learning from each cycle, and of the design changing as a result, is exactly what higher-level work shows.

Worked example

Applying iterative design

A team is designing a new bike helmet. Explain how an iterative process would develop it and contrast this with a linear approach.

Explore and create the first cycle
Explore users and the need (safety, comfort, ventilation), write a specification, generate ideas, and model an early prototype - then evaluate it by testing fit and impact.
Learn and iterate
Testing reveals the ventilation is poor and the fit is uncomfortable, so the team loops back - researching head shapes again, developing new vent and strap designs, prototyping and re-testing - improving the helmet with each cycle.
Contrast with linear
A linear approach would design and make the helmet once and evaluate only at the end, when the ventilation and fit faults would be expensive to fix and there would be no chance to improve; iteration finds and fixes them early and repeatedly.

Result: Iterating through explore-create-evaluate cycles lets the helmet's ventilation and fit be found and improved test by test, producing a far better product than a single linear run that evaluates only at the end.

Typical mistakes

Describing the design process as a one-way linear sequence with evaluation only at the end.
Treating iteration as doing the same thing twice, rather than learning from each cycle and changing the design as a result.

Active revision

Explain, with reference to a product of your choice, how an iterative design process of exploring, creating and evaluating would produce a better outcome than a single linear run from brief to product.

Active recall

Recall the key points — then reveal.

Sources: GCE AS and A level subject content for design and technology (Department for Education) · AQA A-level Design and Technology: Product Design (7552) specification (AQA)

Identifying needs, briefs and specifications#

StandardAQA 7552 3.2.1DfE GCE D&T - briefs and specifications

Specification criteria: ACCESS FM

Fig. 2ACCESS FM is a checklist for a comprehensive specification - aesthetics, cost, customer, environment, size, safety, function and materials - each criterion made measurable and justified so it can be designed to and tested against.

Designing begins by identifying a genuine need or want and the client and users it belongs to. A need is something required to solve a real problem (a way for an older person to open jars); a want is something desired. Identifying the client (who the design is for or commissioned by) and the users (who will actually use it, who may differ from the client) focuses the whole project on real people and a real problem rather than a vague idea.

The design brief is a short statement of the problem and what the design should achieve - the starting point agreed with the client. It sets the direction without over-constraining the solution. From the brief and research, the designer writes a design specification: a detailed, measurable list of criteria the final product must meet - its function, size, cost, materials, aesthetics, safety, target user and environmental requirements - against which every idea and the final product will be judged.

A useful framework for a specification is ACCESS FM: Aesthetics, Cost, Customer, Environment, Size, Safety, Function and Materials. Working through each heading ensures the specification is comprehensive and covers appearance, budget, the user, sustainability, dimensions, safety, what it must do, and what it is made from. A good specification is measurable and justified - each criterion tied to the need and the research, not plucked from the air - so it can actually be tested against later.

The specification is the backbone of the whole project: ideas are generated to meet it, developed against it, and the final product is evaluated against it. A vague or unmeasurable specification ('it should be nice and cheap') cannot guide design or judge success; a precise, justified one ('it must cost under 15 pounds to make, suit users aged 8 to 12, and withstand a 1 metre drop') drives the design and makes objective evaluation possible. Writing a strong specification is one of the most important skills in the subject.

Worked example

Writing a measurable specification

From a brief to design a lunchbox for primary-school children, write measurable specification points using ACCESS FM and justify them.

Function and size
Function: it must hold a sandwich, a drink and two snacks and keep them separate. Size: it must fit a standard school bag (no larger than 220 x 150 x 80 mm) - justified by the user's bag and lunch needs.
Safety, materials and cost
Safety: no sharp edges and food-safe materials; Materials: durable, food-safe, dishwasher-proof polymer such as polypropylene; Cost: manufacturing cost under 4 pounds so it can retail affordably - each measurable and tied to a child user and a mass market.
Aesthetics, customer, environment
Aesthetics: bright, appealing colours a child will like; Customer: easy for a 5-to-11-year-old to open and close unaided; Environment: made from a recyclable single polymer - justified by inclusivity and sustainability.

Result: Each ACCESS FM heading yields a measurable, justified point (size under 220 x 150 x 80 mm, cost under 4 pounds, food-safe recyclable polymer, child-openable), giving a specification that can guide the design and be objectively tested against.

Typical mistakes

Writing vague, unmeasurable specification points ('cheap', 'nice-looking') that cannot guide design or be tested against.
Confusing the brief (the starting problem) with the specification (the detailed criteria), or failing to justify criteria from research.

Active revision

Write five measurable specification points for a children's lunchbox using ACCESS FM headings, and justify two of them from the needs of the user.

Active recall

Recall the key points — then reveal.

Sources: AQA A-level Design and Technology: Product Design (7552) specification (AQA)

Research#

StandardAQA 7552 3.2.1DfE GCE D&T - research

Types of research

Fig. 3Research is primary (gathered first-hand: surveys, interviews, observation, product analysis) or secondary (from existing sources), and either quantitative (numerical) or qualitative (descriptive) - a good project uses a mix and acts on it.

Research gathers the information a designer needs to understand the problem, the users and the market, so the specification and ideas rest on evidence rather than assumption. It divides into primary research, which the designer gathers first-hand (surveys, questionnaires, interviews, observation of users, and analysis and disassembly of existing products), and secondary research, which uses information others have already gathered (books, the internet, reports, standards, existing market data). Both are needed.

Research is also either quantitative (numerical data that can be measured and compared, such as survey percentages or anthropometric measurements) or qualitative (descriptive insight into opinions, feelings and behaviour, such as interview responses or observed frustrations). Quantitative data shows how many and how much; qualitative data shows why and how. A good project uses both - numbers to size the market and measure the users, and qualitative insight to understand what they really need.

User research is especially valuable because it grounds the design in real people. Observing users struggling with an existing product, interviewing them about their needs, and testing prototypes with them reveals problems and opportunities that a designer would never guess. Product analysis - taking apart and evaluating existing products against criteria such as ACCESS FM - reveals how competitors solve the problem, what works and what does not, and where an improvement lies.

Research must be relevant, reliable and actually used, not decorative. Weak projects gather generic information that never influences the design; strong ones gather targeted primary and secondary research, analyse it, and draw conclusions that directly shape the specification and ideas. A candidate should show the link from research to decision - 'my user research showed X, so my specification requires Y' - which is exactly the evidence-led designing the subject rewards.

Worked example

Planning and using research

A designer is researching a new ergonomic peeler for users with arthritis. Describe the research and show how it shapes the design.

Primary research
Observe and interview users with arthritis using existing peelers to see where they struggle (grip, force, control), and measure hand sizes and grip strength (anthropometric and quantitative data) - first-hand insight into the real difficulty.
Secondary research
Study existing ergonomic and assistive products, relevant anthropometric data tables and any standards, and analyse competitor peelers by disassembly against ACCESS FM to see how others solve the problem.
Turn research into decisions
Because the user research shows low grip strength and pain, the specification requires a large soft-grip handle needing minimal force and suiting the 5th-percentile grip; the product analysis shows a gap for an affordable, attractive version - shaping both the specification and the idea.

Result: Observation, interviews and grip measurements (primary) plus anthropometric data and product analysis (secondary) reveal the real difficulty and lead directly to specification points - a large, low-force soft grip - showing research driving design decisions.

Typical mistakes

Confusing primary (gathered first-hand) with secondary (from existing sources) research.
Gathering generic research that never influences the design, instead of targeted research that drives decisions.

Active revision

For a project to redesign a garden tool for older users, describe two primary and one secondary research method you would use and explain how each would shape the specification.

Active recall

Recall the key points — then reveal.

Sources: GCE AS and A level subject content for design and technology (Department for Education) · AQA A-level Design and Technology: Product Design (7552) specification (AQA)

Ideation and development#

StandardAQA 7552 3.2.1DfE GCE D&T - ideation and development

Ideation is the generation of many possible ideas to meet the specification, deliberately favouring quantity and range early on. Divergent thinking widens the pool of ideas - through sketching, brainstorming, mind-mapping, mood boards and techniques such as SCAMPER (substitute, combine, adapt, modify, put to another use, eliminate, reverse) - so the designer does not fixate on the first idea. A wide range of genuinely different ideas gives the best chance of a strong solution.

Development then narrows and deepens: convergent thinking selects the most promising ideas, often against the specification, and works them up in detail - refining form, construction, materials, mechanisms, ergonomics and manufacture through sketching, modelling and testing. Development is where an idea becomes a workable design, and it is iterative: each version is evaluated and improved, so a single strong concept emerges from repeated refinement.

Ideas are selected and refined against the specification and through feedback, not by the designer's whim. Comparing ideas against the specification criteria (sometimes in an evaluation matrix scoring each idea on each criterion) makes selection objective, and user and client feedback guides which directions to pursue. This keeps ideation and development anchored to the real need rather than to the designer's first preference.

The movement from many ideas (ideation) to one developed design (development) mirrors the explore-create-evaluate cycle at the heart of iterative design. Weak projects jump to a single idea and make it; strong ones show a genuine range of ideas, a justified selection, and real development with each version tested and improved. Evidence of this divergent-then-convergent, iterative working is what distinguishes higher-level design work in the NEA.

Worked example

From many ideas to a developed design

A designer must ideate and develop a concept for a modular desk organiser. Explain the process from generating ideas to a developed design.

Diverge to generate ideas
Use brainstorming, mind-mapping and rapid sketching (and a technique such as SCAMPER) to produce a wide range of genuinely different concepts for the organiser - stacking, modular, wall-mounted, folding - valuing quantity and variety.
Converge to select
Score the concepts against the specification criteria in an evaluation matrix (function, cost, size, aesthetics, manufacture) and gather user feedback, selecting the modular concept that best meets the need objectively rather than by preference.
Develop iteratively
Work the chosen concept up in detail - refining the module size, connection method, materials and manufacture - modelling and testing each version and improving it, so a workable design emerges from repeated refinement.

Result: Divergent sketching and brainstorming generate a wide range of concepts, an evaluation matrix and feedback converge on the best against the specification, and iterative development turns it into a workable design - the divergent-then-convergent, iterative pattern of strong design work.

Typical mistakes

Jumping to a single idea and making it, with no genuine range of alternatives generated.
Selecting an idea by preference rather than by comparing it objectively against the specification and feedback.

Active revision

Explain how a designer would generate a range of ideas for a desk tidy and then select and develop one, referring to divergent and convergent thinking and the specification.

Active recall

Recall the key points — then reveal.

Sources: AQA A-level Design and Technology: Product Design (7552) specification (AQA)

Modelling, prototyping, testing and evaluation#

StandardAQA 7552 3.2.1DfE GCE D&T - prototyping and evaluation

Modelling and prototyping turn ideas into things that can be tested. Models test specific aspects (form, size, a mechanism) and prototypes test whether the whole design functions and meets the specification. Making physical (and virtual) prototypes reveals problems - of fit, ergonomics, strength, function and manufacture - that cannot be seen on paper, and lets them be fixed before committing to a final product. Prototyping is how a design is de-risked.

Testing gathers evidence of how well the design meets its requirements. Functional testing checks it does its job; user testing puts it in front of real users to check fit, usability and appeal; and material or destructive testing checks strength and durability. Tests should be planned to check specific specification points, and their results recorded honestly - a test that reveals a failure is as valuable as one that passes, because it drives improvement.

Evaluation judges the design against the specification and the user need, objectively and honestly. It uses the test results and feedback to say how well each criterion is met, what works, what does not, and what should change - feeding the next iteration. Evaluation is continuous in iterative design, not just a final report, and it must be evidence-based (measured against the specification) rather than a vague 'I think it went well'.

Together, modelling, prototyping, testing and evaluation close the design loop and drive iteration: a prototype is tested, evaluated against the specification, and the findings send the designer back to improve the design, which is prototyped and tested again. Showing this evidence-led cycle - and real improvement resulting from it - is the essence of the NEA and of good designing. The final evaluation should reach honest, justified conclusions and identify further improvements.

Worked example

Testing and evaluating against the specification

A prototype adjustable phone stand has been built. Explain how it would be tested and evaluated and how this drives improvement.

Plan tests against the specification
Test the specific criteria: does it hold phones of the specified size range without slipping (functional test with several phones)? Is it stable when tapped (stability test)? Can users adjust it easily (user testing)? Each test targets a specification point.
Record and evaluate the results
Suppose the stand holds most phones but slips with the heaviest and is slightly unstable at its steepest angle. Evaluate honestly against the specification: the grip and stability criteria are only partly met, the adjustment criterion is met.
Drive the next iteration
The findings send the designer back to develop - adding a rubberised grip and widening the base - and the improved prototype is tested again; evaluation is continuous and evidence-based, and the design changes as a result.

Result: Planned tests against each specification point reveal the stand slips with heavy phones and is unstable at steep angles; the honest evaluation drives a specific improvement (rubber grip, wider base) and a re-test - closing the design loop and improving the product.

Typical mistakes

Evaluating vaguely ('it works well') instead of measuring the prototype against each specification criterion.
Treating evaluation as a final step only, rather than continuous feedback that drives iteration and improvement.

Active revision

A prototype phone stand has been made. Describe two tests you would carry out against its specification and explain how the results would drive the next iteration of the design.

Active recall

Recall the key points — then reveal.

Sources: GCE AS and A level subject content for design and technology (Department for Education) · AQA A-level Design and Technology: Product Design (7552) specification (AQA)

References & sources

Sources

Department for Education

GCE AS and A level subject content for design and technology

AQA

AQA A-level Design and Technology: Product Design (7552) specification

Design methods and processes

5 sections~17 min reading time3 competenciesLevel Standard 4 · Advanced 1

Design methods and processes

Key points

Applying iterative design

Key points

Writing a measurable specification

Key points

Planning and using research

Key points

From many ideas to a developed design

Key points

Testing and evaluating against the specification

Sources

Design methods and processes

Key points

Applying iterative design

Key points

Writing a measurable specification

Key points

Planning and using research

Key points

From many ideas to a developed design

Key points

Testing and evaluating against the specification

Sources