Repair and Disassembly Are Design Decisions
When repair is left until after launch rather than addressed in product definition, products that cannot be disassembled pass every post-use problem on to someone else.
Article Industrial Design Education
Prototypes Must Test Constraints, Not Just Appearance
In prototyping plans, when a prototype is still built just to see whether it looks right, the lookalike sample often fails to answer whether it can be made and used. The safer approach: state the constraints each prototype must test, and lock that choice in with a prototype brief.
Key points
- In prototyping plans, prototypes should no longer exist just to see whether they look right.
- Left unchecked, the same thing happens again and again: a lookalike sample never answers whether it can be made and used.
- Start instead from this: state the constraints each prototype must test.
- Write the choice into the prototype brief, owned jointly by design and engineering.
- From then on, sign off against a single question: if this sample only looks good, has it failed its task?
01What to Decide First About Prototyping
When handling prototyping, the first thing not to do is polish prototypes built just to see whether they look right. In prototyping plans, sequence matters more than wording in determining whether this happens: a lookalike sample that never answers whether it can be made and used.
Start by rewording sentences, and the team will assume prototyping has been updated—while the lookalike sample still hasn’t answered whether it can be made and used.
State the constraints each prototype must test. Until that holds, prototyping is still stuck at checking whether things look right.
02Which Prototyping Decisions Must Come Later
Some decisions must come later. Discussing channels, visuals, or messaging before stating the constraints each prototype must test only preserves prototyping-for-looks under a different name.
Later decisions aren't less important—they're meant to serve earlier choices. Otherwise, the team just keeps treating symptoms: a sample that looks right hasn't answered whether it can be made and used.
03The Order of Prototyping Is Itself Design
The sequence breaks into three steps: first, each prototype documents the constraints to verify; second, that forms the prototype brief; only then do external narratives shift.
When you reverse this order, prototyping looks busy, but it's still just being pulled along by how things look.
04Use Tools to Fix the Prototyping Sequence
A prototype brief must show precedence. Anyone reading it should know what's locked and what still moves.
Before prototyping, use the brief to check whether the sequence has been scrambled by campaign pressure.
05When to Review Prototypes
Design and engineering together. Once the sequence breaks under exceptions, go back to the brief to reset the rules—don't patch it in a chat.
Review asks only: if this sample were just beautiful, would it count as incomplete? If you can answer that, the sequence is working.
Framework
The four-layer structure of prototyping
From what cannot be traded away to tools ready for the field, each layer answers one question only—and keeps prototyping from becoming just about how it looks.
L1Constraints to verify
This layer names what cannot be compromised in the prototype.
L2Appearance is only one item
This layer collects the prototype into checkable conditions.
L3Reject
This layer sets what the prototype can vary across different contexts.
L4Next round
This layer hands the prototype to its users and notes exceptions.
Note: This diagram is a conceptual framework. It explains a way of thinking and is not statistical data. Source: Qingmei Future Insights.
Recommended actions
Action 01
Start from the site
Mark where the prototype is actually called in the roadmap—don't start by rewriting it for appearance.
Action 02
Keep it to one page
Replace longer explanations with the prototype brief; keep only what supports 'each prototype documents the constraints to verify.'
Action 03
Judge it by one question
Before prototyping, ask only: if this sample were just beautiful, would it count as incomplete? If you can't answer, it's not yet a decision.
Action 04
Name the owner
Design and engineering together. A prototype without a keeper gets quietly rewritten in conflicts.
Related
All insightsRelated insights
Feeling Safe Is Part of the Experience
When experience reviews treat safety only as a testing requirement, a product may pass every test while still leaving people feeling unsafe—or unnecessarily alarmed.
Touch-point details shape perceived quality
At sample sign-off, if budget and attention still go to the form seen from a distance, the gaps and feel in the hand often overturn that first impression.