Skip to content
Prioritization Toolkit
Feature Prioritization Toolkit
Eisenhower Matrix
Value vs Effort
Kano Model
Cost of Delay
More
Share
Explore
Kano Model

icon picker
Kano Model Results

Category
Problem to Solve
Questionable
if the CCID isn't unique to each choice, we won't be able to link the finalized item setup attributes for those styles to the correct choice rows in a MAP Buy
when current retail value is null in MDM, we pull original retail, which impacts our POs
I have more than 12 programs in my assortment
Would like to see a sum of the number of choices that are listed in the buy plan portion of MAP in the aggregations summary vs having to manually count and see if I have enough or have over-choiced.
I get an error when I try to add a choice and the vendor field is populated.
I use the group choices by function in every single buy plan, but it goes away when you get to the weekly receipts. Can we have it show up there + on the buy plan when you export into Excel?
Product attribute values don't tell me enough (dept, class, selling channel)
When a KP2 is not attached to a program, the calculation comparing KP2 to my buysheet is wrong
IMU subtotal calc is incorrect
Better attached KP2 indicator
Really annoying to have to open vary dates but scroll for days to try and manipulate the dates by cluster. Would rather open vary dates and have the column open as wide as it can.
As Read Only viewer, we cannot see the entire style name for the style. Hovering over doesn't show the style name and also cannot click on the style. We have to export to see what the style name is.
⁠

Categories

Must-be: Expected features, avoid upsetting users

Your Must-be Features

⁠

⁠
⁠

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

⁠

⁠
⁠

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

⁠

⁠
⁠

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

⁠

⁠
⁠

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

⁠
Loading…
⁠
⁠
Kano Rules (Used for calculations)
0
⁠
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.