I cannot see Kano as a standalone prioritisation method. Yes the three categories make sense and cover most of the groundwork, however you're going to need internal ranking for the Satisfiers and the Delighters (you cannot build everything). MoSCoW creeps in inadvertently. You also don't mention the RICE method, (maybe Weighted Ranking ticks this off).
Well articulated and very easy to follow. As the Agile space is maturing and is being accepted by the sponsors, the next item I am seeing with my clients is more engaged discussions on feature / capability prioritization. The market needs easy steps for busy enterprise leaders to understand the processes of prioritization - And this presentation gives that frame work that Product teams can use to collaborate with sponsors and stake holders
