Part of guide The Definitive Guide to Startups and Venture Capital
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.
Share this story
In short
- 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.
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.
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][5]
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."
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]
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.[5]
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.[4]
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.[4][5]
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][5]
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]
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.
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).
Where opinion splits
Agile Product Managers
Focus on the rapid iteration and delivery of One-Dimensional features that customers explicitly request.
For teams operating in highly competitive, commoditized markets, the Kano Model serves as a roadmap for incremental gains. Agile product managers often prioritize One-Dimensional features because they offer a predictable return on investment. If a competitor increases their cloud storage offering by 50%, matching or exceeding that metric is a defensive necessity. These teams use the Kano framework to ensure they are not over-investing in Must-Be features when those engineering hours could be spent winning the linear performance battle.
UX and Design Strategists
Prioritize the discovery and implementation of Attractive features to build brand loyalty and differentiation.
Design purists view the Kano Model through the lens of emotional resonance. They argue that competing solely on One-Dimensional metrics leads to a race to the bottom on price and specifications. Instead, UX strategists advocate for allocating risk capital toward Attractive features—the unexpected delights that create evangelists out of users. By focusing on the top curve of the Kano graph, these teams aim to build a moat of brand loyalty that insulates the product from competitors who only compete on raw performance.
Quality Assurance Teams
Obsess over the flawless execution of Must-Be features to prevent churn and mitigate operational risk.
From an operations and quality assurance perspective, the Kano Model is a stark warning about the asymmetric risks of product development. QA teams focus heavily on the Must-Be category because a failure here is catastrophic. A banking app with a beautiful, Attractive user interface will still lose customers immediately if the Must-Be feature of secure login fails. For these teams, the Kano Model justifies rigorous testing budgets for baseline features, ensuring the foundation is flawless before any capital is spent on excitement.
- 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
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]PMCQuality Assurance TeamsIntegrating Refined Kano Model and QFD for Service Quality Improvement in Healthy Fast-Food Chain Restaurants
Read on PMC →
[5]Factlen Editorial TeamSynthesis by Factlen editorial team
Read on Factlen Editorial Team →
More in Business
See all →SaaS Metrics
Gross Revenue Retention Exposes Underlying Subscription Churn That Net Expansion Metrics Routinely Conceal
3 sources
AI Funding
Manus Raises Over $500 Million in Fresh Funding After China Blocks $2 Billion Meta Acquisition
10 sources
Equity Compensation
How Double-Trigger Acceleration Safeguards Startup Equity and Preserves Buyer Retention
5 sources
Venture Capital Contracting
Drag-Along Clauses Prevent Minority Shareholder Holdouts During Corporate Acquisitions, Paired with Tag-Along Rights Securing Equal Exit Terms
2 sources
Comments
Every angle. Every day.
Get Business stories with full source coverage and perspective breakdowns, free every day.




