Product teams often jump straight to recycled material percentages, circularity claims, or packaging changes. Those things matter, but they come later. The first test is legitimacy: does the product solve a real human problem, with defensible impact, in a way the team can actually build and support?
If you need the more tactical version of that question, read How to validate a product idea before you build it. This article goes deeper on customer evidence, buyer clarity, and the signs an idea still needs more proof.
Why “should this exist?” is the right starting point
A weak product can still be profitable. A fashionable concept can still be environmentally poor. A clever technical solution can still add noise rather than value. Sustainable design begins by refusing to separate product success from product justification.
Sustainability is strongest when it acts as a filter on what deserves to be built, not just as a decoration added after the business case is approved.
The four-part test
| Dimension | What strong looks like | Warning sign |
|---|---|---|
| Human value | Clear problem solved, frequent use, meaningful benefit | Novelty or convenience without lasting value |
| Planetary impact | Impact is proportionate to benefit and can be reduced over time | High material or energy burden disguised by shallow green claims |
| Economic viability | The concept can survive without distorting the original purpose | Margin depends on overselling, overproducing, or planned replacement |
| Technical feasibility | The team can build, verify, and support it reliably | Technical complexity is being mistaken for innovation |
Worked example: two products with very different legitimacy
A diagnostic medical device and a novelty desk gadget might both be manufacturable and commercially attractive. The difference appears when the value question is made explicit. One product can justify material, energy, and support burden because the utility is high and sustained. The other may only survive if the team ignores that its value evaporates quickly.
Questions worth asking in the concept review meeting
- What real human problem does this solve, and for whom?
- What energy, material, and service burden does the product create over time?
- Would the business model still work if we made the product last longer and need replacing less often?
- Can the team reliably build, support, repair, and improve it?
How to improve a weak concept before it becomes an expensive one
Turn the review into next-step decisions
The Product Purpose Framework helps teams judge whether a concept deserves momentum. Once a concept clears that test, use the Carbon Footprint Estimator and Product Lifecycle Explorer to inspect how the design could become less burdensome over time.