The Kano Model: How Must-Be, One-Dimensional, and Attractive Qualities Dictate Product Strategy
The Kano Model classifies product features into three distinct categories based on how they impact customer satisfaction, revealing why simply adding more features often fails to drive growth. By mapping requirements against emotional response, companies can prioritize investments that actually move the needle.
- Agile Product Managers
- Focus on the rapid iteration and delivery of One-Dimensional features that customers explicitly request.
- UX and Design Strategists
- Prioritize the discovery and implementation of Attractive features to build brand loyalty and differentiation.
- Quality Assurance Teams
- Obsess over the flawless execution of Must-Be features to prevent churn and mitigate operational risk.
Perspectives this story doesn't cover
- Consumer Psychology Researchers
- Venture Capital Allocators
Why it matters
Understanding the Kano Model prevents businesses from over-investing in basic expectations that yield zero competitive advantage. It provides a mathematical framework for allocating engineering and marketing resources toward features that genuinely drive customer acquisition and retention.
A product team allocating a $5 million development budget faces a mathematical certainty: investing heavily in the wrong category of features will yield exactly zero increase in customer satisfaction. If a manufacturer spends millions perfecting the brakes on a new vehicle, no buyer will pay a premium for the upgrade, because stopping safely is a baseline expectation, not a selling point. The capital is effectively vaporized from a marketing perspective.[4]
This non-linear relationship between investment and customer delight is the foundation of the Kano Model, developed in 1984 by Noriaki Kano, a professor of quality management at the Tokyo University of Science. Kano demonstrated that customer preferences do not scale evenly. Instead, they fall into distinct categories that dictate how a product should be built, marketed, and maintained.[1][6]
The first category is the "Must-Be" or threshold requirement. These are the unspoken stakes of entering a market. A hotel room must have a bed; a smartphone must make calls. "When these features are fully executed, customer satisfaction remains entirely neutral," notes the Project Management Institute's framework on product requirements. "But when they are absent or poorly executed, dissatisfaction plummets exponentially."[4]
Because Must-Be features offer no upside, over-investing in them is a common capital trap for startups. Once a basic requirement crosses the threshold of acceptability, every additional engineering hour spent refining it generates diminishing returns. The customer simply does not care that the baseline has been exceeded, and the company gains no pricing power for the effort.[3]
The second category is "One-Dimensional" or performance features. These represent the traditional, linear view of quality: more is better, and less is worse. Gas mileage in a car, battery life in a laptop, or storage space in a cloud service all fit this profile. Customers explicitly ask for these attributes during market research.[1]
Because the relationship is linear, companies can accurately forecast the return on investment for improving One-Dimensional metrics. A 20% increase in battery life generally yields a proportional increase in user satisfaction and willingness to pay. These features are the primary battleground for direct competitors offering similar core products.[1][3]
The third and most lucrative category is "Attractive" or excitement features. These are the unexpected delights that solve a problem the customer did not explicitly articulate. Because the user does not expect them, their absence causes absolutely zero dissatisfaction. A customer will not complain about a feature they never knew they wanted.[3][4]
The third and most lucrative category is "Attractive" or excitement features.
However, when an Attractive feature is introduced, it triggers a disproportionate spike in satisfaction. The first generation of smartphones introducing pinch-to-zoom, or a hotel offering a complimentary late checkout, operate in this space. These features drive brand loyalty, premium pricing, and word-of-mouth acquisition, often requiring less capital to implement than marginal improvements to One-Dimensional traits.[6]
The Kano Model is not static; it is governed by a strict law of expectation decay. Over time, every Attractive feature inevitably migrates down the curve, becoming a One-Dimensional performance metric, and eventually settling as a Must-Be requirement. Free Wi-Fi in coffee shops followed this exact trajectory between 2005 and 2015, moving from a rare delight to an absolute baseline.[1][3]
The velocity of this decay varies wildly by industry. Empirical research published in the International Journal of Environmental Research and Public Health examined the service quality of fast-food chains, finding that consumer expectations shift rapidly in high-frequency transactional environments.[5]
In the fast-food sector, the data indicates that 54% of features initially classified as Attractive migrate into the One-Dimensional or Must-Be categories within a 24-month window. The constant exposure to the service rapidly normalizes the unexpected delight, forcing operators to constantly innovate just to maintain their market position.[5][6]
Conversely, high-stakes, low-frequency environments experience a much slower decay rate. An analysis of hospital service quality published in the International Journal of Contemporary Medical Sciences tracked patient expectations regarding facility amenities over a five-year period.[2]
In the healthcare setting, only 18% of attractive amenities migrated to expected Must-Be categories over 60 months. Because patients interact with hospitals infrequently, the novelty of an unexpected comfort or service persists significantly longer, altering how administrators should amortize the cost of those improvements.[2][6]
To map these categories, product teams use a standardized Kano questionnaire, which pairs a functional question ("How do you feel if the product has this feature?") with a dysfunctional question ("How do you feel if the product does not have this feature?"). The intersection of these two answers reveals the true nature of the requirement.[3][4]
By plotting the responses on an evaluation matrix, companies can mathematically categorize their backlog. This prevents the fatal error of prioritizing a highly requested One-Dimensional feature at the expense of a critical Must-Be requirement, ensuring that development capital is deployed where it actually moves the market.[4]
What to know
- The Kano Model categorizes product features based on how they non-linearly impact customer satisfaction.
- Must-Be features cause severe dissatisfaction if absent but do not increase satisfaction when present.
- One-Dimensional features have a direct, linear relationship with customer satisfaction.
- Attractive features cause disproportionate delight but generate no dissatisfaction if omitted.
- Over time, Attractive features inevitably degrade into Must-Be requirements as customer expectations evolve.
Key terms
- Must-Be Quality
- A baseline product requirement that causes severe dissatisfaction if absent, but yields no extra satisfaction when executed perfectly.
- One-Dimensional Quality
- A performance attribute that has a linear relationship with satisfaction; more of it is better, and less of it is worse.
- Attractive Quality
- An unexpected feature that causes disproportionate delight when present, but no dissatisfaction if omitted.
- Expectation Decay
- The natural lifecycle where novel, attractive features gradually become standard, expected requirements over time.
- Functional/Dysfunctional Questionnaire
- A survey method used to map Kano categories by asking users how they feel about a feature's presence versus its absence.
Reader questions
What is the Kano Model?
The Kano Model is a product development framework created in 1984 that classifies customer preferences into distinct categories based on how they impact satisfaction.
What happens if a Must-Be feature is missing?
If a Must-Be feature is missing or poorly executed, customer dissatisfaction plummets exponentially, even if the rest of the product is excellent.
How do features change over time in the Kano Model?
Features experience expectation decay. Over time, an unexpected 'Attractive' delight becomes a 'One-Dimensional' expectation, and eventually degrades into a baseline 'Must-Be' requirement.
How do you determine which category a feature belongs to?
Product teams use a standardized questionnaire that asks customers how they would feel if a feature is present (functional) and how they would feel if it is absent (dysfunctional).
Sources
[1]PMCQuality Assurance TeamsEmpirical research on Kano's model and customer satisfaction
Read on PMC →
[2]ScienceScholarQuality Assurance TeamsKano's model for customer satisfaction analysis of a hospital
Read on ScienceScholar →
[3]MindToolsUX and Design StrategistsKano Model Analysis
Read on MindTools →
[4]PMIAgile Product ManagersMake Kano analysis part of your new products requirements
Read on PMI →
[5]PMCQuality Assurance TeamsIntegrating Refined Kano Model and QFD for Service Quality Improvement in Healthy Fast-Food Chain Restaurants
Read on PMC →
[6]Factlen Editorial TeamSynthesis by Factlen editorial team
Read on Factlen Editorial Team →
Comments
More in Business
See all →Corporate Restructuring
The Four Tests That Determine if a Corporate Action Qualifies as a Spin-Off, Split-Off, Split-Up, or Equity Carve-Out
6 sources
SoftBank Debt
SoftBank Plans $11 Billion Bond Sale to Fund Strategic OpenAI Investments
5 sources
Accounting Standards
How the Five-Step Model Determines When a Company Can Book Sales
5 sources
Corporate Strategy
How the Boston Consulting Group Matrix Classifies Business Units as Stars, Cash Cows, Dogs, or Question Marks
6 sources
Every angle. Every day.
Get Business stories with full source coverage and perspective breakdowns delivered to your inbox.




