Product development teams at all levels are commonly vexed by the question "which new features should we prioritize?" In the absence of an empirically sound prioritization method, product teams are often prone to internal forces carrying an outsized influence over their product roadmaps - including the infamous HiPPO effect.
The Kano survey method offers a novel approach to product feature prioritization by considering not only the functional requirements of a product feature, but also the emotional needs and expectations of users. While a Kano survey doesn't make the prioritization decisions for you, it provides a user-centric, quantitative way of revealing the features that really matter to people.
In this session...
We'll get grounded in the theory behind the Kano model
We'll share practical tips for how your team can run its own Kano study
We'll acknowledge some of the practical limitations of the Kano model, and how you can overcome them
Matt Schraan leads Product Management at Livefront. At Livefront, Matt loves outsourcing product feature prioritization to the people.
Does this session sound interesting? You may also like these:
This will add your name to the list of interested participants. It will help us gauge interest for scheduling purposes.