The Kano model is a framework for classifying product features and quality characteristics by how strongly they influence customer satisfaction, so teams can decide which to prioritize. Developed by Professor Noriaki Kano in the 1980s, it sorts every feature into one of five categories: must-be (basic), one-dimensional (performance), attractive (delight), indifferent, and reverse. The core insight is that not all features affect satisfaction equally: some are expected and only cause anger when missing, while others delight customers precisely because nobody demanded them.
Kano's method plots customer satisfaction against how fully a feature is implemented. Each category behaves differently on that curve:
A crucial Kano principle is that categories are not fixed. Today's delighter becomes tomorrow's expectation. A rear-view camera in a vehicle was an attractive feature a decade ago; now buyers treat it as a must-be. This drift means a Kano study is a snapshot, not a permanent classification. Manufacturers should re-run the survey periodically, especially in fast-moving categories, so the roadmap keeps pace with rising customer expectations.
Kano data comes from a structured pair of questions asked about each feature. For every characteristic, respondents answer:
Each question offers five answers ranging from "I like it" to "I dislike it." The pair of responses is mapped against a Kano evaluation table that assigns a category. Tallying responses across many customers reveals which category dominates for each feature. This is a rigorous, structured form of voice-of-customer capture, and it converts vague requests into a ranked priority list.
Manufacturers use the Kano model to prioritize which quality characteristics to control tightly and which product features to fund. It sits naturally at the front of an improvement effort. In a DMAIC project, Kano results feed the Define and Measure phases by turning customer needs into ranked critical-to-quality characteristics. Those ranked characteristics then flow into a control plan, which specifies how each one is measured, monitored, and reacted to on the shop floor.
Kano also complements risk analysis. Once you know a characteristic is a must-be, its failure modes deserve serious attention in an FMEA, because a must-be failure produces sharp customer dissatisfaction. Performance characteristics, meanwhile, are strong candidates for statistical process control, since satisfaction tracks continuously with how consistently you hit the target.
Suppose a pump manufacturer surveys 200 customers about five candidate features. Using the functional and dysfunctional question pairs, responses are tallied and the most frequent category wins for each feature. The results come back as follows:
The priority logic falls out cleanly. The leak-free seal is non-negotiable: an 84 percent must-be verdict means any seal defect triggers strong dissatisfaction, so it belongs in the control plan with tight tolerances and a low scrap rate target. Energy efficiency is a performance lever worth continuous investment because satisfaction scales with it. The vibration sensor is the standout delighter: at 59 percent attractive, it is the feature most likely to differentiate the product, so it earns roadmap funding. Casing color is a 76 percent indifferent result, meaning color options should be cheap or dropped. The voice panel is a reverse feature for nearly half the sample, so it should be optional at most, never standard.
To sharpen prioritization, teams often compute two satisfaction coefficients. The satisfaction potential for the vibration sensor equals (attractive plus one-dimensional responses) divided by (attractive plus one-dimensional plus must-be plus indifferent). If 118 are attractive, 40 one-dimensional, 22 must-be, and 20 indifferent, that is (118 plus 40) divided by 200, which equals 0.79. A coefficient near 0.79 confirms the feature has high upside, justifying its place at the top of the delight backlog.
A Kano classification is only valuable if the factory can actually hold the characteristics it deems critical. That is where production data becomes the foundation. Once you decide the leak-free seal is a must-be, you need continuous evidence that seal quality stays in spec, and you need to catch the equipment problems that cause defects before they reach the customer. Fabrico is a real-time OEE and production-monitoring platform that supplies exactly this data foundation: live quality, availability, and performance figures tied to each machine and run.
Fabrico does not run the Kano survey for you, and it is not a customer-research tool. What it does is make your must-be and performance characteristics measurable and defensible in production. Its computer-vision monitoring works even on machines without a PLC, so quality and stoppage data can be captured from older lines that would otherwise stay dark. When a must-be characteristic slips, the same platform's CMMS work-order and preventive-scheduling tools route the fix, closing the loop between what customers demand and what the shop floor delivers. Understanding your overall equipment effectiveness shows whether the process is even capable of protecting the characteristics Kano flagged as essential.
A plain ranking treats features as more or less important on a single scale. The Kano model recognizes that features affect satisfaction in fundamentally different shapes: must-be features only hurt when missing, performance features scale linearly, and delighters add satisfaction without any downside when absent. This lets you avoid over-investing in basics and instead fund the differentiators that actually win customers.
Yes. Treat the "customer" as whoever receives the output, including the next process step. A downstream station may consider a clean, burr-free part a must-be and a pre-sorted batch a delighter. Applying Kano thinking internally helps prioritize which process characteristics to lock into a control plan and monitor with production data.
No. Fabrico is a real-time OEE, production-monitoring, and CMMS platform, not a customer-research tool. Kano surveys are done through voice-of-customer questionnaires. Fabrico's role begins after classification: it provides the live quality, downtime, and equipment data needed to hold the must-be and performance characteristics that a Kano study identifies as critical.
Ready to turn your prioritized quality characteristics into live, defensible production data? Book a Fabrico demo and see how real-time OEE and CMMS monitoring keeps your must-be and performance features under control on every machine.
Login
Blog