What is it?
Feature-Satisfaction Analysis (classically known as the Kano Model) is an empirical product prioritization framework developed in 1984 by Professor Noriaki Kano at the Tokyo University of Science. It directly challenges the linear assumption that customer satisfaction scales monotonically with product feature volume. By modeling the non-linear relationship between feature fulfillment and emotional perception, it guides engineering teams toward asymmetric value creation.
The Analytical Mechanism
The methodology interrogates feature perception utilizing paired questions (Functional: "How do you feel if this feature is present?" vs. Dysfunctional: "How do you feel if this feature is absent?"), categorizing features into five distinct archetypes:
1. Must-Be Attributes (Basic Expectations): Non-negotiable baseline hygiene factors. Their presence creates neutrality; their absence triggers catastrophic churn (e.g., dial-tone on a phone).
2. Performance Attributes (One-Dimensional): Linear satisfaction drivers. Increased execution speed, battery longevity, or storage directly elevates customer sentiment.
3. Attractive Attributes (Delighters): Unanticipated innovations. Absence causes no distress, but presence generates disproportionate advocacy and pricing power.
4. Indifferent Attributes: Features that buyers simply do not value, representing pure operational waste.
5. Reverse Attributes: Complex or invasive capabilities that actively degrade user satisfaction.
The Algorithmic Reactor Advantage
Product backlogs frequently succumb to bloat, as teams conflate internal development effort with market impact. The Brainstorm Reactor framework imposes rigorous filtering:
- Elimination of Indifferent Work: Flags and deprioritizes low-impact feature proposals before sprint allocation.
- Hygiene Architecture Validation: Verifies foundational reliability prerequisites prior to authorizing speculative delighters.
- Temporal Erosion Modeling: Automatically alerts teams to the inevitable decay of past delighters into contemporary baseline expectations.
Boundary Limits & Trade-offs
The Kano methodology captures customer sentiment at a specific point in time. It requires disciplined segmentation; mixing enterprise buyers with end-users corrupts classification datasets.
Strategic Application Fields
Essential for SaaS roadmap grooming, minimum viable product (MVP) scoping, legacy software rationalization, and enterprise packaging tier definitions.