A Product Family Needs a Shared Logic
In series planning, if each product in the family still looks good alone, they rarely look like family when grouped, and no one knows how new members join.

In design reviews, if product form still starts as a beautiful rendering, the usual result is an attractive form that doesn't hold up on structure or cost and is then forced to change. A sounder approach is for form to answer all three questions from the outset, with a three-way comparison locking that choice in.

The first thing product form must stop is starting from a beautiful rendering. In design reviews, failing to stop leads straight to this: an attractive form that doesn't hold up on structure or cost, and then has to be reworked.
What carries on can be minimal. Keeping it minimal is what protects form answering all three questions from the outset.
Form answers all three questions from the outset. Until it does, product form is still stuck at a beautiful rendering.
Vagueness usually slips in through well-meant additions. To accommodate more scenarios, people write product form back into starting from a beautiful rendering.
Every time you add without looking back at the problem clearly, boundaries become harder to enforce. The problem is this: beautiful form doesn't hold up structurally or cost-wise, then gets forced to change.
A negative list beats adjectives. Write down when a product form cannot be used, and the team understands that form answers three things from the start—not as slogan, but as fact.
Keep the list short. Short enough that it survives a design review intact.
The three-part framework stops overreach; it doesn't collect inspiration. Overreach can exist, but it can't pose as product form.
It holds because design and engineering move together, and both can say no.
After overreach, don't just fix one output. Go back to the framework and patch the condition that got bypassed this time.
Then ask the same question again: when only appearance remains, do structure and cost still have answers?
From what cannot be traded away to tools usable on-site—each layer answers one question, so you don't rewrite product form as a pretty picture first.
This layer states what in product form is non-negotiable.
This layer compresses product form into checkable conditions.
This layer defines what product form can shift across different contexts.
This layer hands product form to those who use it, with exceptions noted.
Note: This diagram is a conceptual framework. It explains a way of thinking and is not statistical data. Source: Qingmei Future Insights.
In design review, mark where product form actually gets called—don't start by rewriting it as a pretty picture.
Use the three-part framework instead of longer descriptions. Keep only what supports the idea that form answers three things from the start.
In design review, ask one thing: when only appearance remains, do structure and cost still have answers? If not, it's not a decision yet.
Design and engineering together. Product form without a caretaker gets quietly changed in conflict.
In series planning, if each product in the family still looks good alone, they rarely look like family when grouped, and no one knows how new members join.
In material selection, if materials are chosen for trend or inventory alone, the material does the talking while the team can't say why.
When styling is completed before structural requirements are addressed, the structure often undoes the decorative work—or becomes burdened by it.