Kano Customer Requirement Mapping

Run a Kano model user feedback analysis to categorize customer requests into essential features, performance drivers, and potential delighters.

5 time blocks, 60 minutes in total.

Time blocks

Feedback Ingestion and Pair Clean: 10 min
Format functional and dysfunctional response pairs into clean rows
Kano Evaluation Matrix Mapping: 15 min
Match response pairs against the matrix to classify each feature tag
Category Frequency Calculation: 15 min
Tally Must-Be, Performance, Attractive, and Indifferent percentages
Satisfaction Coefficient Scoring: 10 min
Compute Better and Worse scores to measure satisfaction impact
Roadmap Synthesis and Action: 10 min
Group features into roadmap tiers based on final category scores

About this routine

Noriaki Kano created the Kano model in 1984 to help product teams understand how customer satisfaction shifts as features are added or modified. Instead of treating every piece of customer feedback equally, this approach evaluates feature requests on two dimensions: how the user feels if a feature is present, and how they feel if it is absent.

Using a Kano model user feedback analysis prevents teams from spending development effort on features that customers find indifferent or reverse. By sorting responses into Must-Be, Performance, Attractive, Indifferent, and Reverse categories, product managers gain a clear view of baseline expectations versus true differentiators.

Why this routine works

Separates baseline expectations from innovative delighters
Prevents overinvestment in features customers do not value
Provides quantitative satisfaction scores for backlog prioritization

FAQ

What is Kano customer requirement mapping?

It is a framework developed by Noriaki Kano that categorizes customer feedback into five requirement types based on how feature presence or absence affects satisfaction.

How long does a Kano analysis session take?

A standard Kano analysis session takes 60 minutes once survey responses are collected.

Sources

Attractive Quality and Must-Be Quality by Noriaki Kano et al., Journal of the Japanese Society for Quality Control, 1984