Using less material should serve use, not just look minimal
In structural lightweighting, if material is cut just to look like less, usability suffers and the reduction becomes a gesture.

In the form-giving process, structure is often still an afterthought: the ornament gets finished first and the structure is bent to fit. The usual result is that structure strips the ornament away, or the ornament weighs the structure down. A sounder approach is to make the structure work first, then decide where ornament is needed, and to lock that choice in through sequence.

If structure is only ever something bent to fit finished ornament, no system can be built. In the form-giving process it has to be broken apart. Otherwise no one can say where the problem lies: structure strips the ornament away, or the ornament weighs the structure down.
Breaking it apart isn't about adding complexity. It's so that “structure first, ornament second” can land in distinct layers.
Make the structure work first, then decide where ornament is needed. Until that happens, structure is still something bent to fit finished ornament.
The layers of a structure need interfaces between them. Only when the upper layer defines what's non-negotiable does the layer below know where it can flex.
Without interfaces, every context reinterprets the structure, and ornament-first thinking creeps back in through the gaps.
Rules can be executed; samples can only illustrate. If a team only collects finished pieces it likes, every new context brings back the old problem: structure strips the ornament away, or the ornament weighs the structure down.
That's why the sequence sets out conditions, not a single reference image.
The execution layer has to work for ordinary people, not just experts. In process reviews, check whether the sequence still points to structure first, ornament second.
Once the execution layer serves only the skilled few, structure again becomes something a handful of people bend to fit their finished ornament.
As the system evolves, update the rules while keeping the principles consistent. The design lead is responsible.
Every round ends with the same question: with the ornament removed, does the product still hold up? If the answer is yes, the system is still intact.
From what is non-negotiable to tools that work in the field, each layer answers just one question, so structure doesn't slide back into an afterthought bent to fit the ornament.
This layer states what in the structure is non-negotiable.
This layer distills the structure into conditions that can be checked.
This layer defines what the structure can flex across different contexts.
This layer hands the structure to the people who use it, with exceptions spelled out.
Note: This diagram is a conceptual framework. It explains a way of thinking and is not statistical data. Source: Qingmei Future Insights.
In the form-giving process, mark the moments when structure is actually called upon. Don't start by reworking ornament-first designs.
Use sequence over lengthy explanation—retain only what supports 'establish structure first, then decide where embellishment belongs.'
In process review, ask only: does the product hold without decoration? If you can't answer, it's not yet a decision.
Design ownership. Without a maintainer, structure gets quietly altered in conflict.
In structural lightweighting, if material is cut just to look like less, usability suffers and the reduction becomes a gesture.
In product definition, when the reuse path remains 'figure out what to do with it after the product ends,' the result is often that the destination is never designed and can only end up discarded.
In product value discussions, when durability remains 'articulating value as new features and appearance,' the result is often that products that don't last long invalidate all the promises that came before.