Product Analysis
Learn from existing products by examining what succeeds, what fails and what evidence suggests should change.
By the end of class, you should be able to…
Explain purpose
Describe why product analysis is used in design development.
Identify stakeholders
Recognize how users, manufacturers and engineers contribute evidence.
Analyse key features
Use function, performance, usability, features and materials as lenses.
Generate opportunities
Use testing / reverse engineering evidence to identify improvements.
Product analysis is structured learning from what already exists.
The purpose is not to copy a product. It is to understand strengths, weaknesses and opportunities for future development.
What works well?
Identify successful features worth preserving or learning from.
What limits the product?
Find failures, friction, poor performance or unmet needs.
What could improve?
Translate evidence into focused redesign directions.
Different stakeholders see different problems.
Experience + usability
Can reveal needs, errors, satisfaction and real task performance.
Construction + production
Can identify assembly, repeatability and production constraints.
Technical performance
Can assess function, mechanisms, safety or performance evidence.
Do not analyse “everything.” Use clear lenses.
Function
What is the product intended to do?
Performance
How well does it achieve the function under relevant conditions?
Usability
How effectively can intended users interact with it?
Features + materials
Which design details and material choices contribute to strengths or weaknesses?
Testing reveals performance instead of relying on impressions.
Performance data
Time, force, capacity, accuracy, leakage, stability or another relevant metric.
User interaction
Errors, pauses, workarounds and satisfaction.
Alternatives
Test similar products under the same conditions to reveal meaningful differences.
Reverse engineering examines the product by working backwards from the existing design.
Disassembly or detailed inspection can reveal components, construction, interfaces, materials and how features contribute to function.
What is analysis—not description?
A student writes about a travel mug: “It is black, 20 cm tall and made of stainless steel.”
Which next statement is strongest?
Compare competing and similar products to reveal weaknesses, trade-offs and opportunities.
| Lens | Product A | Product B | Design insight |
|---|---|---|---|
| Opening | Twist lid; high grip effort | Flip lid; accidental release risk | Trade-off between security and ease of access |
| Cleaning | 3 removable parts | 6 removable parts | More components may increase cleaning complexity |
| Leak test | No leakage | Minor leakage after inversion | Seal design deserves deeper analysis |
Constructive discontent turns dissatisfaction into a design opportunity.
The goal is not to complain about a product. It is to identify where the product is not meeting user needs, support that judgement with evidence, and ask how it could improve.
“This lid is terrible.”
No user need, no evidence and no direction for development.
“3/5 users cannot open the smooth lid with wet hands.”
The evidence identifies an unmet need and creates a focused opportunity to improve grip while retaining seal performance.
Analysis should end with “so what?”
Feature
Smooth cylindrical lid.
Evidence
3/5 intended users fail to open it with wet hands on first attempt.
Weakness
Insufficient grip under a realistic condition.
Opportunity
Improve lid interaction for low-friction / wet-hand use while maintaining seal performance.
Your IA must analyse successes and weaknesses of key features.
What succeeds?
How do form and features support the task?
What causes limits?
What design choices contribute to performance or failure?
What affects users?
Where do interaction, comfort or risk reveal opportunities?
Analyse one everyday object.
Choose a stapler, reusable bottle, phone stand, pencil case, desk lamp or similar product.
Product-analysis vocabulary
Retrieve first. Then check.
Can you retrieve it without looking back?
Before you leave…
Usability Objectives & SWOT
Keep the evidence chain moving: user → research → decision → test.
C3.1.1–3.1.7 Product analysis and evaluation · stakeholders · SWOT · testing / reverse engineering · comparing competing and similar products · constructive discontent; IA Criterion A existing-product analysis.