A useful alternative way of thinking about requirements prioritization. I’ve worked on projects where users’ basic expectation will not be met at launch because of technical limitations and timelines. I knew at the time that the frustrations created from not meeting basic expectations would likely override any delighters that the final product would provide. The Kano model is a good way of phrasing this type of argument to stakeholders and project members.
