Kano Model

Framework categorizing features by their relationship to customer satisfaction, distinguishing must-have requirements, proportional performance features, and excitement differentiators.

Process

Key Fields

Question it answers	What features are table-stakes vs. differentiators? What creates competitive advantage? Where is the market heading?
Participants & timing	100-300 respondents · 3-5 min per response · 1-2 weeks analysis
AI compatibility	AI scores responses against the Kano model, categorizes features, creates Kano diagrams, and projects feature evolution over time.
Output	Kano categorization matrix, 2D Kano diagram (satisfaction vs. effort), feature prioritization roadmap, market evolution outlook

Use when

Feature roadmap prioritization considers both satisfaction and differentiation
Understanding which features create competitive advantage is needed
Market is mature with predictable feature evolution

Skip when

Product or category is entirely new (no established baseline features)
Feature set is very small (under 8 items)

Common Mistakes

Assuming excitement features stay exciting

Excitement features eventually become expected table-stakes. Regularly re-run the Kano model and update categories as the market evolves.

Over-investing in excitement when must-haves are broken

Adding excitement features while basic tasks remain incomplete alienates users. Fix must-haves first; excitement features can wait.

Not accounting for customer segment differences

What is must-have for enterprise (SSO, audit logs) may be an excitement feature for SMB. Run separate Kano models by segment and road-map accordingly.