Prioritize MVP Features Using the Kano Model
Prioritizing features at an early stage of the product is a bummer — the Kano model helps us understand in which features to invest, how much, and what is our Wow feature.
Published in
9 min readAug 14, 2020
tl;dr (or when to use the Kano model)
Like all product teams and freelance designers, we are limited by time and resources. The Kano model helps us identify:
👍 What are the minimum features the user expects to have.
✌️ What features will enhance the user’s experience.
👌 What feature has the potential to be a Wow feature.
Planning the work in stages allow us to:
💁♀️ Validate our assumptions by listening to user’s feedback.
🙋♂️ Spread out Excitement generators, maintaining a high level of interest.
🏃♂️ Manage costs and workload to shorter sprints.
As a freelance product designer, I usually come across entrepreneurs and CEO’s with an idea for a product, with a varying degree of a plan and list of business goals. It could be a simple and straightforward idea:
