In Part 1, we introduced the idea that meaningful product design isn't about adding more — it's about knowing what to remove. Now let's examine this principle through a specific lens: meditation and mindfulness products.
The Paradox of "More Mindfulness"
Walk through any app store's health & wellness category and you'll find a strange contradiction: apps that promise to reduce your mental clutter by adding more things to your daily routine.
- Daily meditation streaks
- Guided breathing exercises (14 varieties)
- Sleep stories narrated by celebrities
- Mood tracking with 47 emotion labels
- Community challenges, leaderboards, badges
- AI-generated personalized recommendations
The message is clear: "To feel less overwhelmed, here are 12 more things to do every day."
This isn't just ironic — it's counterproductive. The cognitive load of managing a wellness routine can itself become a source of stress.
The Feature Ceiling
I've been studying meditation products for the past few months, and a pattern emerges across the market:
| Product | Core Feature | Total Features After 2 Years |
|---|---|---|
| Calm | Guided meditation | ~40+ (stories, music, masterclasses) |
| Headspace | Guided meditation | ~35+ (focus music, move, sleep casts) |
| Balance | Personalized meditation | ~15 (singles, plans, skills) |
The most interesting case is Balance, which has fewer features but higher per-session engagement. Users spend more time meditating, not more time navigating.
This isn't accidental. There's a cognitive principle at work: decision fatigue applies to self-care too. Every additional feature is another decision the user has to make before they can simply be still.
What OneZen Gets Right
OneZen takes the subtraction principle to its logical endpoint. Instead of asking "What can we add?" the product asks "What can we remove while still delivering value?"
The result is a meditation tool that doesn't feel like a tool at all. It feels like breathing room.
Three design choices worth studying:
1. No onboarding questionnaire.
Most apps ask: "What brings you here? Anxiety? Sleep? Focus?" — creating a taxonomy of your problems before you've even started. OneZen skips this entirely. You open the app, you breathe. The diagnosis can come later, if at all.
2. No content library.
The paradox of choice is well-documented. When you have 500 guided meditations, choosing becomes its own mental exercise. OneZen offers a deliberately minimal set — enough for variety without the overwhelm.
3. No streaks or gamification.
This is the most radical choice. Streaks work — they're psychologically proven to build habits. But they also transform an intrinsically motivated activity (wanting to feel calm) into an extrinsically motivated one (not wanting to break a streak). When the streak breaks, so does the habit. OneZen trusts that the practice itself is rewarding enough.
The Evidence for Subtraction
This isn't just philosophy. There's a growing body of research supporting minimalist design in wellness products:
- A 2024 study in the Journal of Medical Internet Research found that meditation app users who engaged with fewer features reported higher satisfaction and longer retention.
- The "paradox of choice" (Schwartz, 2004) has been replicated in digital wellness contexts: more options consistently lead to lower usage, not higher.
- Headspace's own data showed that users who only used the "Today's Meditation" feature (ignoring the rest) had 3x better retention than power users.
What This Means for Builders
If you're building a product in the wellness space — or any space where the core value is reducing cognitive load — here's what the subtraction principle looks like in practice:
Ship the minimum viable calm. Not the minimum viable product. The minimum viable calm. What's the smallest thing you can build that still creates a genuine moment of peace?
Measure removal, not addition. Track "features removed this quarter" alongside "features added." If the ratio is below 1:2, question it.
Default to no. Every feature request should start with "why shouldn't we build this?" not "why should we?"
The best feature is the one users don't notice. If someone describes your product as "simple" or "clean," you've succeeded at subtraction. If they describe it as "powerful," you might be adding too much.
The Hardest Part
The reason most products don't follow the subtraction principle isn't that builders disagree with it. It's that subtraction is organizationally harder.
- Adding a feature makes someone on your team happy (the PM who suggested it, the engineer who built it, the user who requested it).
- Removing a feature makes someone unhappy.
- Not adding features makes investors nervous ("What's the roadmap?")
The subtraction principle requires discipline that goes against every organizational incentive. But the products that achieve it — from the original iPod scroll wheel to OneZen's deliberately sparse interface — are the ones we remember.
This is Part 2 of a series on product subtraction. Part 1 covered the general principle; this part applies it to mindfulness products. Coming next: Part 3 on how Web3 projects can (and should) apply subtraction to token design and community mechanics.
Top comments (0)