Feature Prioritization Toolkit

Explore

Kano Model

Kano Model Results

Categories

Must-be: Expected features, avoid upsetting users

Your Must-be Features

⁠

Easy team metrics

⁠

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

⁠

Stand-up check in

⁠

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

⁠

Digital kanban simulation Project brief

⁠

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

Google Chrome's dinosaur game⁠

⁠

Indifferent: Who cares

Your Indifferent Features

⁠

Guide to asyncronous work

⁠

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.

Todo: Questionable and Reverse

⁠

Next: Try the

SAFe "Arnold Mod" WSJF⁠

method

⁠

Kano Model Links

⁠

Kano Rules (Used for calculations)

Kano Rules (Used for calculations)

⁠

Gallery

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.