The decision filter
The internal questions every feature, product, and piece of content must answer before it ships under the Kumbatio name.
Before publishing content, adding a feature, or shipping a product under the Kumbatio name, we ask six questions.
If the answer to most of them is no, it's not a Kumbatio product or piece of content - no matter how interesting it is to build.
The questions
-
Does this reduce cognitive load or add to it? Every feature carries a processing cost. If the value doesn't clearly outweigh the added load, it doesn't ship.
-
Does this improve the user's agency or apply pressure? Tools should expand what people can choose to do, not push them toward what the tool wants. Nudges that guilt, deadlines that shame, and defaults that trap all fail this test.
-
Does this help someone at low energy, not just at peak? It's easy to build features that shine when the user is at
100. The harder and more important question is what the feature does for someone at25. -
Does this assume one default brain, or design for variability? If a feature only works for users with stable attention and predictable schedules, it recreates the problem Kumbatio exists to solve.
-
Is this honest about what it does and doesn't do? No vague promises, no clinical overreach, no capability we can't actually deliver. If we can't describe it plainly, we don't ship it.
-
Would this feel supportive to someone having a genuinely difficult day? The final gut check. Not "is this useful in the abstract" - would it feel like an embrace or like another demand?
Why a filter instead of a roadmap
The Kumbatio products are deliberately different from each other - different metaphors, different UI patterns, different user moments. That flexibility is a feature, not a weakness.
What holds the umbrella together isn't uniformity. It's shared intent:
- Human-first over productivity theater
- Clarity over complexity
- Adaptation over rigid workflows
- Supportive language over shame-based language
- Practical usefulness over trend features
The filter is how that intent gets applied to concrete decisions. A product can look nothing like its siblings and still be unmistakably Kumbatio - because it passed the same questions.
What the filter has ruled out
The filter isn't decorative. It's why Kumbatio products have no streaks that punish breaks, no engagement-maximizing notifications, no productivity scores, and no gamification designed around loss aversion. Each of those is standard in the category. Each fails at least three of the six questions.