By the end of this topic, you should be able to...
compare their ideas with the design specifications and user needs as they refine their solutions.
Guiding Question
How do designers approach problem-solving?
What Is Iterative Analysis?
You have generated a rich range of ideas through ideation. You have explored diverse directions, applied multiple creative techniques, and produced concepts that respond to your problem statement. You have perhaps made initial sketches, rough models, or digital representations of your most promising ideas.
Now comes a question that separates good designers from great ones:
How do you know which idea is actually better — and why?
This is the question that iterative analysis answers.
Iterative analysis is the disciplined process of systematically comparing design ideas against two standards — the design specification and the needs of the user — at every stage of the design process, using what is learned from each comparison to refine and improve the solution before comparing again.
The word iterative is critical here. Analysis is not a single event that happens once at the end of the design process. It is a repeating cycle — compare, learn, refine, compare again — that continues until the design genuinely meets both the specification criteria and the user's real needs.
Think of iterative analysis as the feedback loop of the design process. Just as a navigator constantly checks their position against their destination and adjusts their course accordingly, a designer constantly checks their evolving solution against their specification and user needs — adjusting, refining, and improving with each comparison.
Key insight: A design that has never been compared against its specification and tested against user needs is not a refined design — it is an unchecked assumption. Iterative analysis transforms assumptions into evidence-based decisions.
The Two Standards of Iterative Analysis
Iterative analysis compares design ideas against two distinct but complementary standards. Understanding the difference between them — and why both are necessary — is fundamental to effective design practice.
Standard 1: The Design Specification
The design specification — constructed in B2.1.9 from primary and secondary research — defines the measurable, testable criteria that the design solution must meet. It represents the objective, evidence-based benchmark for design success.
Comparing ideas against the design specification answers the question:
"Does this idea have the potential to meet the defined criteria for success?"
This comparison is primarily analytical and objective — it asks whether the design meets measurable thresholds, performs required functions, and satisfies the essential and desirable criteria established through research.
Standard 2: User Needs
User needs — identified through primary research, personas, journey mapping, and user testing — represent the lived, experiential reality of the people the design is intended to serve. They capture not just what the specification says the design must do, but how the design actually feels, performs, and serves users in reality.
Comparing ideas against user needs answers the question:
"Does this idea actually work for the people it is designed for — in the way they need it to work?"
This comparison is primarily empathetic and experiential — it asks whether the design genuinely serves the user's physical capabilities, emotional needs, and contextual reality, rather than merely satisfying written criteria.
Why Both Standards Are Necessary
The design specification and user needs are complementary — neither is sufficient alone:
Design Specification | User Needs | |
|---|---|---|
Nature | Objective, measurable, written | Experiential, qualitative, lived |
Source | Research data and analysis | Real users in real contexts |
Risk if used alone | May miss experiential qualities not captured in written criteria | May miss measurable performance requirements |
Question answered | "Does the design meet its defined criteria?" | "Does the design actually work for real users?" |
Method of comparison | Analytical evaluation against criteria | User testing, observation, feedback |
Real design principle: A design can meet every criterion in the specification and still fail to serve the user — because specifications, however carefully written, cannot capture every dimension of human experience. And a design can feel wonderful to users during initial testing but fail to meet critical safety or performance standards. Both comparisons are essential — together they provide a complete picture of how well a design solution is performing.
The Iterative Analysis Cycle
Iterative analysis is not a linear process — it is a repeating cycle of four connected activities:
1: Compare Against the Design Specification
Systematically evaluate the current design concept or prototype against each criterion in the design specification:
Does the design meet this criterion? (Essential criteria — pass or fail)
To what degree does the design approach this criterion? (Desirable criteria — degree of achievement)
What specific aspects of the design are preventing full achievement of this criterion?
What modifications would bring the design closer to meeting this criterion?
Tools for specification comparison:
Specification Compliance Matrix
A specification compliance matrix provides a systematic, visual record of how well a design concept meets each specification criterion:
Criterion | Type | Target | Current Performance | Status | Action Required |
Grip force ≤ 8N | Essential | ≤ 8 Newtons | ~14 Newtons estimated | ❌ Fail | Increase mechanical advantage — redesign lever geometry |
One-handed operation | Essential | Full operation possible | Partial — stabilisation still requires second hand | ❌ Fail | Integrate jar stabilisation mechanism |
Handle diameter 35–45mm | Essential | 35–45mm | 38mm | ✅ Pass | No action required |
Dishwasher safe | Essential | Materials withstand 70°C | Material TBC | ⚠️ Unconfirmed | Confirm material specification |
Domestic aesthetic | Desirable | Non-clinical appearance | Current form reads as medical | ⚠️ Partial | Refine form language — reduce clinical associations |
Weight ≤ 150g | Desirable | ≤ 150g | ~180g estimated | ⚠️ Partial | Explore material substitution to reduce weight |
The compliance matrix makes the gap between current performance and specification requirements immediately visible — turning analysis into a clear, prioritised action list for refinement.
Annotated Design Evaluation
Alongside the compliance matrix, annotated design drawings provide a powerful analytical tool — identifying specific features of the design and evaluating each against relevant specification criteria directly on the drawing.
Effective annotated evaluations:
Identify specific design features with leader lines or callouts
State which specification criterion each feature relates to
Evaluate how well the feature meets the criterion
State what modification is needed to improve performance
Example annotation: "Handle cross-section currently circular — provides insufficient torsional resistance for users with reduced grip strength. Specification requires no more than 8N grip force. Modify to oval cross-section — increases resistance to rotation without requiring increased grip force. Refer to Specification Criterion 3."
2: Compare Against User Needs
Comparing design ideas against user needs requires direct engagement with users — not just analytical evaluation of written criteria. This is where the designer goes back to the people their design is intended to serve.
Methods for comparing against user needs:
User Testing of Models and Prototypes
Present physical models or prototypes to representative users — ideally users who match the characteristics of the persona — and observe and record their interaction.
What to observe and record:
Which interactions are intuitive — performed without hesitation or error?
Which interactions cause hesitation, confusion, or difficulty?
What workarounds does the user instinctively develop?
What unexpected uses does the user attempt?
What is the user's emotional response — confidence, frustration, delight, anxiety?
Feedback Questionnaires
After user testing, structured questionnaires gather specific, comparative feedback about the design's performance against user needs:
Question | Response Scale |
"How comfortable was the product to hold?" | 1 (Very uncomfortable) — 5 (Very comfortable) |
"How confident did you feel using the product independently?" | 1 (Not at all confident) — 5 (Very confident) |
"How well did the product address the difficulties you previously experienced with similar products?" | 1 (Not at all) — 5 (Completely) |
"What would you change about this design?" | Open response |
"Would you use this product in your daily life?" | Yes / No / With modifications |
Comparative User Testing
Present multiple design concepts simultaneously to users — asking them to compare and rank the concepts against their own needs and preferences.
This reveals not just how well each design performs individually but which design direction users genuinely prefer and why — insights that specification analysis alone cannot provide.
Think-Aloud Protocol
Ask users to verbalise their thoughts as they interact with the design — a technique called the think-aloud protocol. This generates rich qualitative data about the user's moment-by-moment experience:
"I'm trying to grip this... it's a bit slippery... I'm not sure which end to hold... oh, this part twists? I wasn't expecting that... I'd probably put this down and ask for help at this point."
Think-aloud data reveals exactly where and why the design fails to meet user needs — providing precise, located insights for refinement.
3: Identify Refinement Priorities
After comparing against both standards, analyse the findings to identify prioritised refinement actions:
Priority 1 — Critical failures:Design aspects that fail essential specification criteria or that completely prevent user operation must be addressed before any other refinement. These are non-negotiable.
Priority 2 — Significant gaps:Design aspects that significantly fall short of essential criteria or that cause major user difficulty are addressed next.
Priority 3 — Enhancement opportunities:Design aspects that partially meet desirable criteria or that users identified as improvable but not problematic are addressed in subsequent iterations.
Key principle: Refinement resources — time, materials, testing capacity — are always limited. Iterative analysis prioritises refinement effort toward the changes that will most significantly improve the design's performance against both standards.
4: Refine the Design
Using the prioritised refinement actions identified through analysis, modify the design — adjusting dimensions, changing materials, rethinking mechanisms, simplifying interactions, or reconsidering form — to address the identified gaps and failures.
Each refinement should be:
Specific — addressing a clearly identified gap from the analysis
Justified — explained with reference to the analysis finding that prompted it
Traceable — recorded so that the evolution of the design is visible and documented
Then — return to Phase 1 and compare again.
This is the iterative loop: compare, learn, refine, compare again. Each cycle produces a design that is closer to meeting both standards — closer to genuinely serving the user.
Documenting Iterative Analysis
Documenting the iterative analysis process is as important as conducting it. The documentation creates a visible record of design evolution — showing how the design changed, why it changed, and what evidence drove each change.
Effective iterative analysis documentation includes:
Version Tracking
Clearly label each design iteration — Version 1, Version 2, Version 3 — and maintain a record of what was changed between versions and why.
Version | Key Changes Made | Evidence That Prompted Change |
V1 → V2 | Increased handle diameter from 28mm to 38mm; changed cross-section from circular to oval | Specification Criterion 3 (handle diameter); user testing revealed slipping during wet-hand operation |
V2 → V3 | Integrated jar stabilisation base; reduced overall weight by substituting aluminium component with polymer | Specification Criterion 1 (one-handed operation); user feedback identified two-handed requirement as primary barrier |
V3 → V4 | Refined surface texture pattern; adjusted lever geometry to increase mechanical advantage ratio from 3:1 to 5:1 | User testing revealed residual grip force requirement still exceeded some participants' capability; specification compliance matrix showed Criterion 2 still failing |
Before-and-After Comparative Drawings
Side-by-side annotated drawings showing what changed between design iterations — with explicit reference to the analysis findings that prompted each change.
Updated Specification Compliance Matrix
After each refinement, update the compliance matrix to show improved performance — creating a visual record of the design progressively meeting more criteria across iterations.
Real-World Examples of Iterative Analysis in Universal Design
OXO Good Grips
The development of the original OXO Good Grips peeler involved multiple documented iterations, each driven by comparison against specification criteria and user testing:
Iteration 1 — Initial concept:A soft rubber handle of larger diameter than standard peelers.
Specification comparison findings:
Handle diameter: ✅ Met criterion (38mm within specified range)
Grip force requirement: ❌ Failed — rubber compound too soft, deformed under grip, reducing mechanical efficiency
Wet-hand performance: ⚠️ Partial — improved but inconsistent
User testing findings:
Users with arthritis reported improved comfort ✅
Users reported handle felt "too squishy" and lacked confidence of control ❌
Users with severe arthritis still reported difficulty maintaining consistent peeling motion ❌
Refinement actions:
Reformulate rubber compound — increase Shore hardness to maintain shape under grip pressure while retaining compliance
Add longitudinal fin pattern to handle surface — increase grip security without increasing required grip force
Increase handle length — improve leverage and reduce wrist strain during peeling motion
Iteration 2 — Refined concept:Firmer Santoprene compound with fin-pattern surface and extended handle length.
Specification comparison findings:
Grip force requirement: ✅ Now meets criterion — fin pattern provides mechanical grip engagement
Wet-hand performance: ✅ Fin geometry channels water away from contact surface
Handle diameter: ✅ Maintained within specified range
User testing findings:
Users with arthritis reported dramatically improved confidence and control ✅
Users reported fins "felt secure without having to squeeze hard" ✅
One participant noted difficulty distinguishing which end of the handle to grip ⚠️
Refinement action:
Add visual and tactile differentiation between grip zone and non-grip zone of handle
This documented cycle of comparison, analysis, and refinement — repeated across multiple iterations — produced a final design that met every essential specification criterion and addressed every critical user need identified through testing.
Microsoft Adaptive Controller
Microsoft's development of the Xbox Adaptive Controller involved extensive iterative analysis in collaboration with disability organisations and disabled gamers:
Key iterative analysis findings across multiple rounds:
Iteration | Specification Issue Identified | User Need Issue Identified | Refinement Made |
Round 1 | External port spacing too narrow for some plug designs | Users with limited vision could not distinguish port types by sight | Increased port spacing; added tactile differentiation between port types |
Round 2 | Button activation force marginally above specification threshold | Users with spasticity reported accidental button activation | Reduced activation force AND added optional activation threshold adjustment |
Round 3 | Cable management insufficient — cables tangled during repositioning | Users reported frustration and loss of confidence when repositioning the controller | Integrated cable guides and velcro management strips on controller underside |
Round 4 | Controller weight within specification | Users with fatigue conditions reported difficulty repositioning controller during extended play | Added non-slip base surface to reduce need for repositioning |
Each round of iterative analysis involved direct user testing with diverse disability profiles — ensuring that refinements served the full range of intended users, not just the most frequently tested profile.
Universal Design outcome: The iterative analysis process — by consistently comparing against both specification criteria and the diverse needs of real users — produced a controller that successfully accommodated a far wider range of physical capabilities than any single round of analysis could have achieved.
Inclusive Playground Equipment
When Kompan — a global playground equipment manufacturer — developed their range of inclusive playground equipment for universal use, their iterative analysis process included systematic comparison against both specification criteria and the needs of children with diverse abilities:
Round 1 analysis findings:
Specification comparison:
Wheelchair transfer height: ❌ Exceeded maximum specification — too high for independent wheelchair transfer
Surface texture: ✅ Met slip resistance criteria
Structural strength: ✅ Met load specification
User needs comparison (testing with children with diverse abilities):
Children with visual impairments could not navigate to equipment independently ❌
Children using wheelchairs could reach equipment but could not transfer independently ❌
Children with autism reported sensory overstimulation from bright colours and complex forms ❌
Children without disabilities found equipment insufficiently challenging ⚠️
Refinement priorities identified:
(Critical) Redesign transfer height — lower platforms to enable independent wheelchair transfer
(Critical) Add tactile pathway guidance from playground entrance to each equipment piece
(Critical) Develop calmer sensory environment through considered colour and form simplification
(Enhancement) Develop graduated challenge features that scale with user capability
Round 2 analysis findings:
After refinements:
Wheelchair transfer height: ✅ Now meets specification
Tactile pathways: ✅ User testing shows improved independent navigation by visually impaired children
Sensory environment: ✅ Children with autism reported reduced distress ✅
Challenge scaling: ⚠️ Initial implementation insufficient — requires further development
Universal Design outcome: By the third iteration, the playground equipment met all essential specification criteria and addressed the primary needs of children across all tested ability profiles — while the iterative analysis documentation provided a compelling, evidence-based account of how each design decision had been made in response to specific user needs.
Iterative Analysis vs Final Evaluation
Students often confuse iterative analysis with final evaluation. They are related but distinct activities:
Iterative Analysis | Final Evaluation | |
|---|---|---|
When | Throughout the design process — at every stage | At the conclusion of the design process |
Purpose | To identify gaps and drive refinement | To assess whether the final solution has succeeded |
Outcome | Design modifications and improvements | A judgement of the design's success and remaining limitations |
Direction | Forward-looking — "What needs to change?" | Reflective — "How well did it work?" |
Standard | Design specification + user needs | Design specification + user needs |
Key principle: Iterative analysis feeds the design process — it is the mechanism by which designs improve. Final evaluation concludes the design process — it is the mechanism by which success is assessed. A thorough iterative analysis process makes final evaluation more straightforward — because by the time the final design is reached, most gaps have already been identified and addressed.
Key Takeaway
Iterative analysis is the disciplined, repeating process of comparing design ideas and evolving prototypes against two essential standards — the design specification and the user's real needs — at every stage of the design process. Using tools including specification compliance matrices, annotated design evaluations, user testing, questionnaires, and think-aloud protocols, iterative analysis makes the gap between current design performance and required design performance visible, specific, and actionable. By systematically identifying what fails, what partially meets requirements, and what succeeds — and by using those findings to drive prioritised, evidence-based refinements — iterative analysis transforms an initial concept into a progressively more resolved solution. The iterative loop — compare, learn, refine, compare again — is the mechanism through which good design intentions become genuinely successful design outcomes.
Practical Application
Iterative analysis is one of the most directly and heavily weighted components of your Internal Assessment (IA) — it is the evidence that demonstrates genuine design thinking rather than single-pass making.
Iterative Analysis Component | Your IA Application |
|---|---|
Specification compliance matrix | Apply at each design iteration — documenting how well each version meets each specification criterion |
Annotated design evaluations | Annotate drawings and photographs of each design iteration with specific references to specification criteria and user needs |
User testing records | Document user testing of models and prototypes — observations, questionnaire results, think-aloud transcripts |
Version tracking | Clearly document what changed between iterations, what evidence prompted each change, and what improved as a result |
Refinement justification | Explicitly connect every design modification to a specific finding from specification comparison or user testing |
IA Criteria Connection
Criterion | Iterative Analysis Connection |
|---|---|
Criterion A — Analysis of a Problem | The design specification and user needs established in Criterion A become the two standards against which all iterative analysis is conducted — making Criterion A the foundation of the entire analytical process |
Criterion B — Conceptual Design | Iterative analysis of initial concepts against the specification and user needs drives the selection and development of the strongest design direction — demonstrating that concept choices are evidence-based |
Criterion C — Development of a Prototype | Iterative analysis is the primary mechanism of Criterion C — examiners assess whether the prototype evolved through documented cycles of comparison, learning, and refinement driven by both specification criteria and user feedback |
Criterion D — Testing and Evaluation | The patterns of performance identified through iterative analysis provide the context for final evaluation — demonstrating how the design progressed toward meeting its specification across iterations |
💡Student Tip
The most powerful evidence of design thinking in your IA is a clearly documented iterative process — showing not just what your design looked like at each stage, but what you compared it against, what you found, and what you changed as a result. Examiners are not looking for a perfect first design — they are looking for evidence that you can learn from comparison and use that learning to improve. Show every iteration, annotate every comparison, justify every refinement. A design that visibly evolved through rigorous iterative analysis tells a far more compelling story than a design that appeared fully formed — and earns significantly higher marks in Criterion C.
Sources
Cross, Nigel. Designerly Ways of Knowing. Springer, 2006.
International Baccalaureate Organization. Design Technology Guide. International Baccalaureate Organization, 2014.
Lawson, Bryan. How Designers Think: The Design Process Demystified. 4th ed., Architectural Press, 2006.
Norman, Donald A. The Design of Everyday Things. Rev. ed., Basic Books, 2013.
Ulrich, Karl T., and Steven D. Eppinger. Product Design and Development. 6th ed., McGraw-Hill Education, 2015.
Cross-reference: B2.1.9 specification as the evaluative benchmark; B2.1.12 for development actions arising from analysis; B2.1.13 for modelling outputs that are iteratively analysed.
Linking Questions
What ergonomic considerations are important to be able to engage successfully with the design process? (A1.1)
How do design technology students ensure they engage with user-centred research methods? (A2.1)
To what extent are the goals of the design process aligned with the goals of a user-centred design (UCD) process? (B1.1)
To what extent does the model, test, refine cycle require full engagement with modelling and prototyping at several levels of fidelity? (B2.2)
Which aspects of the design process require engagement with material selection? (B3.1)
How do the requirements of the design process ensure students are addressing the responsibility of the designer? (C1.1)
Why is product analysis and evaluation important in the design process? (C3.1)
To what extent does the design process require the exploration of design for manufacture strategies? (C4.1)