What is Mottainai?
Mottainai expresses regret over waste — of materials, time, energy, and human effort — before it ever occurs. As articulated by Wangari Maathai, it is not just about reuse or recycling, but about designing systems that honor resources from the beginning, so loss is never normalized.
The word "waste" comes from Latin vastare (lay waste, empty, desolate), originally meaning used up or bare. "Garbage" comes from Anglo-French garber (to refine, make neat) — not the excess, but the process of making neat. Our language shapes our systems.
Learn more: UNEP youth declaration on zero waste →
Waste is Designed In at the Start
Most waste is not the result of individual behavior, but of decisions made long before a product reaches a person. Materials are extracted, processed, and assembled in ways that assume disposability. By the time something reaches the curb, the waste has already been locked in.
"Waste" meant used up, bare, open (think wasteland). "Garbage" was about making neat, not the excess created. Our language shapes our systems.
Waste is born at the factory, not the curb. Design choices upstream determine what becomes waste downstream.
When systems ignore the full lifecycle, inefficiencies and losses become invisible until it's too late.
Three Principles
Engineer products and systems by accounting for where materials come from, how they are used, and how they return without becoming waste.
By generating continuous, real-world data, we make invisible losses visible, enabling better decisions before inefficiencies harden into waste.
We align technology with natural processes, favoring regeneration, adaptation, and resilience over extraction and replacement.
Our Solution (in progress)
We are building practices and tools that catch waste at the sketch stage. Every experiment here is aimed at making reuse the default and disposal the rare exception.
Trace inputs, score their circularity, and swap in regenerative options before procurement locks in.
Architect products for repair, upgrade, and remanufacture. Components live multiple lives across programs.
Build take-back and refurbishment into the business model so users never face waste decisions alone.