Degrowth as design

The most common design brief in software is simple: increase usage. More minutes, more sessions, more retention. Our dashboards assume that if the person keeps coming back, the product is working.

Degrowth as design flips that premise.

It says: a product is working when the human needs it less.
The win condition is graduation.

That one reversal changes everything: what you measure, what you build, and what kinds of business models are even ethical or viable.

What we’re truly trying to say

Degrowth isn’t an aesthetic of “less.” It’s a commitment to a different definition of value.

Most products treat the user’s ongoing dependence as proof of success. Degrowth treats reduced dependence as proof of success. It asks designers to stop confusing “ongoing engagement” with “ongoing benefit.”

That’s the core claim:

If a product’s success metric is graduation, it cannot be extractive by design. It must contain an off-ramp, and celebrate it.

This is not minimalism, and it’s not anti-product

Degrowth as design is often misheard as minimalism (“remove features”) or as a kind of moral stance against products (“people should be offline”). That’s not what this is.

Degrowth is an architectural and organizational stance:

• The system must include an explicit off-ramp.
• The off-ramp can’t be punitive, hidden, or emotionally manipulative.
• The product must help the person take what they earned and carry it forward without you.

In other words: the product isn’t trying to become smaller; it’s trying to make the user bigger.

Where it came from (Inyeon + training wheels)

This design stance emerged in the work around Inyeon, where the North Star isn’t “daily journaling forever.” It’s compassion that comes more naturally as you grow.

That’s why OFNR (Observation, Feeling, Need, Request) is treated as training wheels: a scaffold, not a permanent ontology. The point isn’t to keep someone in the framework; the point is to help someone outgrow it.

The decision was named explicitly: OFNR is training wheels, not a permanent framework.

Once you have that framing, “degrowth” stops being metaphor and becomes operational: you can design for transcendence signals (moments where a person no longer needs the structure) and treat them as a success state rather than churn.

Inyeon as the survival test

The origin story matters, but the harder claim is this: Inyeon is where degrowth has to hold.

Keiko and I want Inyeon to succeed. If people actually journal more compassionately, the product builds a compassionate threshold inside the person: a felt sense of what compassion means to them. That is not a vibe outcome. It is a specific class of data the product captures: ground truth on the user’s own compassion, authored by the user.

An affirmation app was originally proposed. We stepped back because there is no ground truth in affirmations: they are inputs without a felt referent. Compassion journaling has the opposite shape: the journal is the referent. The data only exists if the person did the work.

Call it a ground truth economy: a class of products whose data is impossible to fake, impossible to surveil into existence, and impossible to extract without consent. The data is only valuable because it was authored, not harvested.

A product optimized for extraction cannot generate that data. A product optimized for graduation can, as a byproduct.

This is the part where degrowth stops being a stance and starts being a moat.

The moment this became a public differentiator

A subtle thing happens when the broader ecosystem moves in the opposite direction: toward ads, surveillance, and extraction.

When ChatGPT’s ads platform got logged, it wasn’t just a product note. It was a forcing function: if the world is normalizing engagement-maximizing ad models, then a graduation-based product has a clear stance.

Degrowth becomes legible as sovereignty.

What degrowth changes (three concrete shifts)

Once “graduation” is the win, three layers of the stack have to change.

1) The metric inverts

In a degrowth-oriented product, a decline in usage frequency can be a feature, not a bug.

This is not naïve. It doesn’t mean you ignore retention. It means your retention curve is no longer your moral compass.

The question becomes:

• Is the person returning because the product is valuable?
• Or returning because the product is addictive, anxiety-inducing, or structurally sticky?

A graduation metric forces you to disentangle dependency from benefit. It pushes you to measure outcomes instead of loops.

2) The business model has to follow

If your product is working when the user needs it less, you can’t price on retention. You can’t build a business that requires an indefinite relationship while claiming your product’s purpose is transformation.

This is the design-to-economics bridge that the companion piece explores: Degrowth economics: graduated users cost less.

The core tension is simple:

• Retention pricing assumes ongoing dependence.
• Graduation assumes a completed transformation.

So degrowth requires business models aligned to outcomes, cohorts, and transition moments, not indefinite extraction.

3) The privacy posture follows “for free”

A product designed to be needed less has less incentive to extract, hoard, and pool data.

When the win condition is graduation:

• You don’t need shadow profiles.
• You don’t need cross-context identity graphs.
• You don’t need to keep the person in your orbit.

The architecture stays cleaner because the metric stays cleaner.

This is why degrowth belongs inside the sovereignty argument: if you can’t let someone leave with their data, in a format they can use, with no friction and no residual identity tracking, then your “degrowth” is just marketing copy.

The funny tension: “less” is hard to believe

Degrowth is conceptually simple, but psychologically disruptive.

We’ve been trained, as builders and as users, to equate “more” with value:

• more features
• more time
• more touchpoints
• more personalization
• more “engagement”

Degrowth asks a different question: what is the smallest artifact that proves the transformation occurred?

It also exposes a pattern many organizations fall into: degrowth in the copy, retention in the dashboard.

The compromise is always the same:

• You tell a story about empowering users.
• Then you measure success by how long they stay dependent.

Degrowth as design refuses that split.

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.

This is the stack claim:

• Degrowth is not merely a value statement.
• It is a testable architecture decision.
• It’s the mechanism that makes sovereignty real.

How we got here: manifestation as database building

Keiko brings GTM and an unusual gift for making people trust her with something real. I bring product and architecture. We started by asking a question that sounds soft until you take it seriously: what could we offer people that is actually good for them?

Planning for degrowth was how we answered. It let us imagine a future we wanted to be part of providing (non-extractive, graduation-shaped, sovereign) and then work backwards into schemas, surfaces, and stack decisions that could hold that future.

Turns out manifestation is a form of database building. You declare the future you want. You encode the constraints that make it possible. Then the architecture starts refusing the shortcuts that would betray it.

The real test: can a user leave cleanly?

If you want to know whether you built a degrowth product, don’t look at your homepage.

Look at your off-ramp.

Ask:

• Can a user export their data in a usable format, without hoops?
• Can they understand what will happen to their account and history?
• Can they leave without being punished with dark patterns?
• Is the product still “successful” when they do?

If not, degrowth isn’t implemented. It’s aspirational.

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?