Degrowth as Design
A design practice where success is users needing the product less. Usage decline as the product working.
The premise
Most products are designed to maximize engagement. Time-on-app, daily active users, retention curves: every metric assumes the win is the user keeps coming back. Degrowth as design inverts the metric. The product is working when the human graduates.
This is not minimalism. It is not anti-product. It is a specific architectural commitment: the system must contain its own off-ramp, and the off-ramp must be celebrated rather than mourned.
Where it came from
Inyeon's North Star is degrowth: compassion journaling that gets quieter as you grow. OFNR (Observation, Feeling, Need, Request) is taught as training wheels, not a permanent ontology. The system tracks transcendence signals, the moments where a user no longer needs the structure, and treats them as wins, not churn.
The decision was named explicitly: OFNR is training wheels, user-paced graduation. Both staying and graduating are success.
What it changes
Three concrete shifts:
- The success metric inverts. Decline in usage frequency is a feature, not a bug. The dashboard celebrates exits.
- The business model has to follow. If users graduate, you cannot price on retention. You price on the transformation, or you price the next graduating cohort.
- The privacy posture follows for free. A product designed to be needed less has no incentive to extract, hoard, or pool. The architecture stays clean because the metric does.
The honest tension
Degrowth as design is hard to sell to investors who model on retention curves. It is also hard to sell to product teams whose performance is measured against engagement KPIs. The compromise most companies make is degrowth in the marketing copy, retention in the dashboard. That compromise produces a worse version of every other product, not a degrowth product.
The real test is whether you write the off-ramp into the contract. If a user can leave with their data, in a format they can use, with no friction and no shadow profile, the product was built for them. If not, degrowth was a story you told yourself.
Where it sits in the stack
Degrowth is the design layer of a longer sovereignty argument. Without graduation, sovereignty is rhetorical. Without sovereignty, graduation is just churn with better PR.
Open questions
- How do you price a product whose success metric is its own redundancy?
- What is the smallest possible artifact a graduated user takes with them?
- Where does degrowth break down? At what scale does the off-ramp become the product?