Skip to content
Gallery
10 Feature Prioritization Methods
Share
Explore
Prioritization Tool Kit

icon picker
Method 6: Kano Model

Prioritize your features based on their
Modified from , by - Agile Coach at Agile by Design. And inspired by
Change: If customers had the feature? and If customers did not have the feature?
See results auto-ordered in: Kano Model Results
Set "If Customers Had"
How would customers respond if this feature was available in your product or service?
Set "If Customers Did Not Have"
How would customers respond if this feature was missing from your product or service?
Kano Metrics Table
Request Name
If customers had the feature?
If customers did not have the feature?
1
F1: New billing page
Like it
Like it
2
F2: Import functionality
Dislike it
Expect it
3
F3: Video calls
Expect it
Don't care
4
F4: Security upgrade
Like it
Dislike it
5
F5: Item comments
Don't care
Dislike it
6
BNS-684: Notification panel redesign
Don't care
Like it
7
F7: Localization of mobile app
Like it
Expect it
8
F8: Multi-location Management
Don't care
Don't care
There are no rows in this table

Kano Model Results
Category
Request Name
1. Must-be
1
F5: Item comments
2. Performance
1
F4: Security upgrade
3. Attractive
1
F7: Localization of mobile app
4. Indifferent
2
F3: Video calls
F8: Multi-location Management
5. Questionable
1
F1: New billing page
6. Reverse
2
F2: Import functionality
BNS-684: Notification panel redesign

Categories

Must-be: Expected features, avoid upsetting users

Your Must-be Features

F5: Item comments

About Must-Be

Must-be features need to be present in our product or service or users will complain and be frustrated. Continued investment in Must-Be features past the point of meeting user expectations does not provide additional returns.
Our goal with Must-be features is to invest just enough to keep users from being dissatisfied, and not more than that.
Examples:
You expect keyboards to register keys when you type. Investing in optical key switches is probably not going to delight you any more than a standard mechanical switch, but if your keys didn't register reliably you would notice and get frustrated

Performance: The more the better

Your Performance Features

F4: Security upgrade

About Performance

It's easy to think about Performance features as having a generally linear relationship between functionality and user satisfaction. The more of a Performance feature you have, the more satisfied users are, the less functionality you provide, the more frustrated users become.
While it's easy to think about Performance features linearly, realistically there will be minimum utility points on the low-end where a feature moves from usable to useless, and a maximum saturation point where any more improvements are overkill.
Examples:
Internet speed
Camera quality

Attractive: Non-critical, delightful features

Your Attractive Features

F7: Localization of mobile app

About Attractive

We don't need attractive features, but when we first notice them they make a big impact on us.
Examples:
Inertia/momentum scrolling on the iPhone
Funny "404 Page Not Found" error pages
Easter eggs like

Indifferent: Who cares

Your Indifferent Features

F3: Video calls
F8: Multi-location Management

About Indifferent

With Indifferent features both not having the feature, and investing heavily in it results in the same neural level of customer delight. Features in this category should avoided and not be worked on.

Questionable

Your Questionable Features

F1: New billing page

About Questionable

Lorem

Reverse

Your Reverse Features

F2: Import functionality
BNS-684: Notification panel redesign

About Questionable

Lorem
Todo: About Questionable and Reverse

Kano Model Links

Loading…
Kano Rules (Used for calculations)

Next up:

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.