How often should I re-evaluate features with the Kano Model?

Regularly, as features decay over time; what was once an 'Attractive' delighter eventually becomes a 'One-Dimensional' performance feature and finally a 'Must-Be' expectation.

How does the Kano Model differ from RICE prioritization?

While RICE quantifies priority based on reach, impact, confidence, and effort, the Kano Model focuses qualitatively on the emotional relationship between feature presence and user satisfaction.

Can I use this skill for MVP planning?

Yes, it is ideal for MVPs. It suggests focusing on all 'Must-Be' features and at least one 'Attractive' feature to ensure the product is functional yet delightful.

What is the primary benefit of using the Kano Model?

It helps teams distinguish between basic requirements that users expect and innovative features that truly delight them, preventing wasted effort on features that don't drive satisfaction.

What are 'Indifferent' features in this model?

These are features that users don't care about whether they are present or absent. Identifying these helps teams avoid 'feature bloat' and save development resources.

Kano Model Prioritization

Name: Kano Model Prioritization
Author: lev-os

bylev-os

0•

Productivity & Workflow

Categorizes product features based on customer satisfaction and investment to drive strategic roadmap decisions.

The Kano Model skill provides a structured framework for evaluating how specific features impact user satisfaction versus implementation effort. By classifying features into categories like 'Must-Be,' 'One-Dimensional,' and 'Attractive,' it helps product teams and developers move beyond simple feature voting to make data-driven decisions. This skill is particularly useful when resources are constrained, allowing teams to balance 'table stakes' requirements with innovative 'delighters' that differentiate their product in the market while avoiding resource waste on indifferent features.

Key Features

01Provides a standardized functional/dysfunctional survey methodology for user research.

020 GitHub stars

03Categorizes features into five distinct satisfaction types: Must-Be, Performance, Attractive, Indifferent, and Reverse.

04Generates classification matrices to map customer expectations against development investment.

05Facilitates segment-specific analysis to understand how different user groups value specific capabilities.

06Identifies 'Indifferent' features to prevent feature bloat and unnecessary resource expenditure.

Use Cases

01Defining the scope of a Minimum Viable Product (MVP) to ensure it includes both essentials and one delighter.

02Conducting competitive analysis to identify where competitors are vulnerable in their basic feature sets.

03Prioritizing a product roadmap when engineering capacity is limited.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lev-os/agents kano-model

For use in Claude.ai and ChatGPT

Download Skill