Kano Model
The existence of must-be quality does not increase customer satisfaction, but its absence causes extreme dissatisfaction. Attractive quality, by contrast, increases satisfaction if provided but does not decrease satisfaction if not provided.
The Kano Model is a structured methodology for classifying product and service features by how they affect customer satisfaction — separating basic expectations from performance differentiators and unexpected delighters. Developed by Professor Noriaki Kano in 1984, it uses standardized dual-question surveys and a classification matrix to produce quantitative feature priorities. Product managers, UX researchers, and founders use it to make evidence-based roadmap decisions instead of debating opinions.
“We're building a project management tool for freelancers. I have a backlog of about 12 features and my team is arguing about what to build next. Some…”
Find your delighters, protect your must-haves, and stop building features customers ignore
The Kano Model classifies every candidate feature into one of six categories by asking customers two standardized questions per feature: a 'functional' question (how they feel if the feature IS present) and a 'dysfunctional' question (how they feel if it is NOT present), each answered on a five-point scale. Paired responses are mapped through the Kano Evaluation Table to assign a category: Must-be (threshold basics whose absence causes dissatisfaction), One-dimensional (performance features with a linear satisfaction relationship), Attractive (unexpected delighters that create disproportionate satisfaction), Indifferent, Reverse, or Questionable. Aggregated across respondents, dominant categories emerge for each feature. A secondary metric — the Better-Worse coefficient (also called the Satisfaction/Dissatisfaction index) — quantifies how much adding or removing each feature moves the satisfaction needle. The full workflow runs: identify candidate features → draft functional/dysfunctional question pairs → administer survey → classify each response via the evaluation table → aggregate per-feature distributions → calculate Better-Worse coefficients → map features onto a priority quadrant → make roadmap decisions.
Product teams routinely build features customers are indifferent to while failing to protect the basic expectations that, when missing, cause immediate churn. Feature prioritization debates collapse into the loudest voice winning — or proxy metrics that don't capture the asymmetric, non-linear nature of customer satisfaction. The result: roadmaps full of 'nice-to-haves' that don't move the needle, and delighters left unbuilt because no one knew customers would love them.
Run a structured Kano survey, classify every feature as a Must-be, Performance driver, or Delighter, and calculate the exact Better-Worse coefficients that tell you which features to build first — converting a prioritization argument into a data-backed decision.
- A list of candidate features or product ideas you want to evaluate
- Optional: raw survey response data (functional/dysfunctional answer pairs) if you've already run a study
- Context about your product, market, and target customer segment
- Your current roadmap or prioritization dilemmas you want resolved
- A ready-to-distribute Kano survey instrument with correctly worded functional and dysfunctional question pairs for each feature
- A completed Kano Feature Classification Matrix mapping every feature to its dominant category (Must-be, One-dimensional, Attractive, Indifferent, Reverse, or Questionable)
- Better-Worse coefficient scores enabling numerical comparison of features across categories
- A Feature Priority Quadrant Map translating Kano results into actionable roadmap sequencing
Watch the methodology work.
Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.
“Your backlog has 47 items and your last sprint planning meeting turned into a 90-minute debate where the loudest voices won. Calendar sync got deprioritized because the founder doesn't personally care about it, and three engineers spent a month on custom themes — a feature 80% of your customers are completely indifferent to. Time tracking is half-built, invoice generation keeps getting pushed, and you have no idea whether the AI features you've been hyping will actually move the needle with customers.”
“After surveying 25 freelancers with your Kano instrument, invoice generation and mobile access both scored as Must-be — their absence was causing quiet churn you hadn't attributed to anything. AI task suggestions scored Attractive with a high Satisfaction coefficient, confirming it's worth the investment for differentiation. Dark mode and custom themes were solidly Indifferent — you removed them from the roadmap entirely, freeing up 6 weeks of engineering time. Your next three sprints are now sequenced by evidence, not debate.”
The same skill, where the work happens.
No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.
What it does, specifically.
Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.
Kano Survey Instrument Builder
Generates a complete, distributable survey instrument for your feature list, including correctly worded functional and dysfunctional question pairs and the standard five-point response scale. The output is ready to copy into any survey tool.
Functional/Dysfunctional Question Pair Generation
Transforms plain feature descriptions into properly scoped functional/dysfunctional question pairs, applying Kano's required question structure and phrasing to avoid leading language that biases responses.
Evaluation Table Classification
Takes any functional/dysfunctional answer pair and maps it through the Kano Evaluation Table to produce a feature category. Supports both individual responses and aggregate frequency distributions across multiple respondents.
Better-Worse Coefficient Calculation
Calculates the Satisfaction coefficient (how much satisfaction increases if a feature is added) and Dissatisfaction coefficient (how much satisfaction drops if a feature is removed) from your frequency distribution data, producing a numerical score for each feature.
Feature Priority Quadrant Mapping
Plots all evaluated features on a two-axis quadrant using their Better-Worse coefficients and dominant Kano category, producing a visual priority map that distinguishes must-protect basics, investment-worthy delighters, performance levers, and features to cut.
Roadmap Decision Translation
Converts the completed Kano classification matrix into plain-language roadmap guidance: what to build now, what to invest in for differentiation, what to maintain as hygiene, and what to cut from the backlog.
Graded before it shipped.
Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.
Kano Survey Instrument
A complete survey document with correctly worded functional and dysfunctional question pairs for every feature, plus the standard five-point response scale — ready to distribute to customers via any survey platform.
Kano Feature Classification Matrix
A structured table listing every evaluated feature alongside its dominant category (Must-be, One-dimensional, Attractive, Indifferent, Reverse, or Questionable), frequency distribution, and classification rationale.
Better-Worse Coefficient Scorecard
A numerical scorecard showing the Satisfaction (+) and Dissatisfaction (−) coefficients for each feature, enabling direct numerical comparison and rank-ordering across the full feature set.
Feature Priority Quadrant Map
A two-axis quadrant chart plotting all features by their Better-Worse coefficient scores, visually separating delighters, performance drivers, must-haves, and indifferent features into actionable priority zones.
Roadmap Prioritization Brief
A structured summary translating Kano results into roadmap decisions: features to build immediately, features to invest in for competitive differentiation, baseline requirements to protect, and backlog items to cut.
Grounded in the original work.
Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.
Noriaki Kano
Noriaki Kano is a Japanese quality management professor who developed the Kano Model while at Tokyo Rika University (now Tokyo University of Science) in the early 1980s. His 1984 paper 'Attractive Quality and Must-be Quality' introduced the multi-dimensional view of customer satisfaction that has become foundational to product management, UX research, and quality engineering worldwide. He is a recipient of the Deming Prize for his contributions to quality science.
Attractive Quality and Must-be Quality (Journal of the Japanese Society for Quality Control, 1984)
Professor of quality management, Tokyo University of Science; Deming Prize recipient; author of the 1984 framework adopted globally in product management and quality engineering.
Be first to run it.
Kano Model is being built right now. Leave your email and we’ll tell you the moment it goes live.