Development teams routinely treat all customer requirements as equally critical. They invest heavily in premium materials and tighter tolerances, assuming a linear relationship between specification and satisfaction. This approach systematically misallocates engineering resources, funding features the customer ignores while underfunding the differentiators that win business.
Professor Noriaki Kano formalised this problem in 1984 by categorising product attributes based on how they actually affect customer satisfaction. The resulting Kano Model is a strategic framework for classifying requirements before committing development capital. It destroys the assumption that 'better' universally equals 'more satisfied'.
I apply the Kano Model early in the Advanced Product Quality Planning (APQP) process. It forces project teams to confront a hard truth: customers do not uniformly value our engineering effort. By separating features into distinct categories, we direct R&D spend toward specifications that move the market.
Three Categories of Customer Expectation
The Kano framework classifies requirements into three primary categories: Must-Be, One-Dimensional, and Attractive. Each category demands a fundamentally different engineering and financial approach. Treating them identically guarantees wasted effort and compromised quality.
Must-Be requirements are baseline hygiene factors. Their presence does not increase satisfaction, but their absence causes extreme dissatisfaction. In automotive manufacturing, functional brakes are a Must-Be. No customer buys a car because it stops, but a failure to stop destroys the brand. These requirements demand rigorous PFMEA focus, but zero investment in innovation.
One-Dimensional requirements follow a linear 'more is better' relationship. Higher fuel efficiency or faster processing speeds directly increase customer satisfaction. This is where direct market competition occurs. Companies must apply Design of Experiments (DOE) and continuous improvement capital here to outperform rivals on published metrics.
Attractive requirements generate disproportionate delight when present, but cause no dissatisfaction when absent. Customers cannot articulate these needs until they experience them. The first integration of gesture controls in vehicle interiors was an Attractive feature. It created immediate differentiation without penalising the product for lacking the feature in prior years.
The Kano Questionnaire Methodology
Classifying requirements requires structured customer data, not internal engineering assumptions. The Kano questionnaire presents each feature twice: a functional question (how do you feel if this is present?) and a dysfunctional question (how do you feel if this is absent?). Respondents choose from five standardised answers: I like it, I expect it, I am neutral, I can tolerate it, or I dislike it.
Cross-referencing the functional and dysfunctional answers yields a specific category for each requirement. A respondent who expects the feature when present but dislikes its absence yields a Must-Be classification. The mathematics is simple, but the sample size must be robust. I mandate a minimum of 100 respondent pairs to achieve statistical significance and filter out contradictory 'Questionable' responses.
Survey design must target a broad demographic. Sampling only current customers introduces severe survivor bias. You must gather data from lost customers, prospects evaluating competitor products, and end-users downstream of the OEM. If the sample is skewed, the resulting categorisation will validate existing biases rather than expose actual market dynamics.
| Customer Response (Functional) | Customer Response (Dysfunctional) | Resulting Kano Category |
|---|---|---|
| I like it | I dislike it | Attractive (or One-Dimensional) |
| I expect it | I dislike it | Must-Be |
| I am neutral | I am neutral | Indifferent |
| I dislike it | I like it | Reverse (Remove immediately) |
Reallocating Development Budgets
I recently audited a Tier 1 interior supplier losing market share despite high R&D expenditure. They spread their development budget evenly across 40+ customer specifications, striving for excellence in everything. The strategy failed because it ignored Kano dynamics entirely.
We ran a Kano analysis on their portfolio. The data showed they were dedicating 15% of their budget to recycled materials, a feature their OEM customer classified as Indifferent. Simultaneously, they spent only 5% on advanced acoustic dampening, an Attractive feature highly valued by the end-user. They were burning capital on unnoticed specifications while starving their differentiators.
We restructured the investment matrix. Must-Be requirements received strict, zero-defect quality control via enhanced Control Plans, but no additional R&D funding. One-Dimensional parameters absorbed the largest share of continuous improvement capital. Attractive features gained dedicated prototype budgets. Within twelve months, development costs dropped and market share recovered.
A common failure mode in engineering is treating legacy features as mandatory. During a sensor development project, an OEM specification sheet contained 47 requirements. Kano analysis revealed 16 were Indifferent holdovers from previous generations. We applied inherited designs to these lines, avoiding redundant engineering hours and saving significant project capital.
Integrating Kano with ISO 9001 and APQP
The Kano Model is not merely a marketing tool; it directly satisfies ISO 9001:2015 mandates. Clause 5.1.2 requires top management to demonstrate leadership and commitment concerning customer focus. Applying Kano analysis provides empirical evidence that leadership is actively determining and fulfilling customer requirements, rather than guessing.
Furthermore, Clause 8.2.2 requires organisations to determine requirements for products and services. Kano provides the exact classification framework needed to prioritise these requirements logically. When external auditors review the QMS, a documented Kano analysis proves that resource allocation decisions are driven by structured Voice of the Customer (VOC) data.
For automotive suppliers, Kano anchors the APQP process. During Phase 1, Kano categories define product priorities. In Phase 2, Attractive requirements drive innovative design solutions. By Phase 4, One-Dimensional requirements establish the exact target values for Production Part Approval Process (PPAP) validation, ensuring testing effort matches customer value.
I integrate these outputs directly into the DFMEA and PFMEA. Must-Be requirements dictate the severity ratings for potential failure modes. If a Must-Be fails, the severity is catastrophic. Indifferent features receive lower severity rankings, allowing engineering teams to focus their risk mitigation efforts precisely where the customer feels the impact.
The Decay of Attractive Features
Kano categories are not static. They decay over time. What delights customers today becomes a baseline expectation tomorrow. This dynamic shift is the most critical concept for long-term product strategy to grasp. Failing to map this decay guarantees a stagnant product roadmap.
Consider automotive air conditioning. In the 1980s, it was an Attractive feature that justified a premium price tag. By the 1990s, it shifted to One-Dimensional; customers wanted better, faster cooling. Today, air conditioning is firmly a Must-Be. A vehicle without it is unsellable in most markets. The feature lost its power to differentiate but retained its power to dissatisfy.
Investing heavily in features the customer considers standard is a guaranteed way to lose margin without gaining market share.
Because of this decay, a Kano analysis is obsolete within 24 months. Quality directors must institutionalise the survey into biannual management reviews. As outlined in Clause 9.3.2, management review inputs must include customer satisfaction data. Regular Kano tracking provides dynamic data that shows exactly how market expectations are shifting.
The Lifecycle of a Product Feature
- 01AttractiveThe feature creates delight. Heavy R&D investment in prototypes captures early adopter market share.
- 02One-DimensionalThe feature enters mainstream competition. Continuous improvement and DOE optimise performance metrics.
- 03Must-BeThe feature is expected. Focus shifts entirely to defect reduction, PFMEA, and cost minimisation via process control.
- 04DecayLegacy Indifferent features are identified during updates and stripped from the design to save manufacturing costs.
Common Implementation Failures
The most frequent implementation error is classifying too many requirements as Must-Be. Engineers default to this category because it protects the scope. If everything is Must-Be, prioritisation is impossible. A Must-Be classification must mean the product is literally unusable or illegal without it, not simply inferior.
Another structural failure is confusing internal pride with customer value. An engineering team might spend months perfecting a proprietary manufacturing process that yields a flawless surface finish. If the customer is Indifferent to that finish because it is hidden inside the assembly, the effort is pure waste. The Kano data must overrule engineering pride.
Finally, teams often treat the Kano Model as a standalone academic exercise, leaving the findings isolated in a PowerPoint deck. The output must be actively integrated into the NPI process, the Quality Management System, and risk management. If the Kano categories do not directly alter the Control Plan and the budget, the analysis was a waste of time.
Quality is defined by what the customer values, not by what the engineer finds interesting. The Kano Model translates Voice of the Customer data into actionable engineering boundaries. By funding differentiation, standardising the baseline, and cutting indifference, manufacturers build products that dominate the market at a lower development cost.