One of the challenges product teams encounter, is how to decide which features should be included in their products. Identifying the user needs, helps teams to focus on what a product should deliver to address a certain type of user. In time, teams develop many ideas on how to address these needs. The Kano model (proposed in the 80s by Noriaki Kano) offers a way to differentiate these features by focusing on customer satisfaction.
This article provides an alternative approach using the Kano model to answer the question: “Which features should be included in the Minimum Viable Product (MVP)?”
English