Serious.Games
AgileFree

Kano Model

Prioritise features based on their impact on user satisfaction.

Duration · 90 min
Participants · 4–15
Level · Intermediate

The Kano Model allows for the classification of product features according to their impact on user satisfaction. This game helps teams make informed decisions about the roadmap based on perceived value rather than the complexity of features. By identifying essential, linear, and exciting features, teams can better align their development with user expectations.

Walkthrough

  1. 1

    Introduction to the Kano Model

    10 min

    The facilitator presents the Kano Model by explaining the three categories of features: essential, linear, and exciting. They discuss the importance of these categories for user satisfaction and how they influence feature prioritisation. Participants are invited to ask questions to clarify their understanding.

    TipUse concrete examples to illustrate each category, such as the car example, to make the theory more tangible.

  2. 2

    Identifying Features

    20 min

    Participants are divided into small groups and receive cards of potential features for their product. Each group must discuss and decide which category each feature belongs to according to the Kano Model. The facilitator moves from group to group to answer questions and guide discussions.

    TipEncourage participants to base their classifications on user data or customer feedback.

  3. 3

    Sharing Results

    15 min

    Each group presents their categorisation choices for the features and explains the reasoning behind their decisions. Other groups can ask questions to better understand the choices. This step allows for confronting perspectives and ensuring a common understanding.

    TipUse a whiteboard or a visual collaboration tool to note each group's choices and facilitate discussions.

  4. 4

    Discussion on Prioritisation

    15 min

    The facilitator leads a discussion on how features should be prioritised based on their category. Essential features should be developed first, followed by linear and then exciting features. The focus is on creating a balanced release plan.

    TipRemind participants that prioritisation can evolve over time and that today's exciting features may become essential tomorrow.

  5. 5

    Summary and Next Steps

    10 min

    The facilitator summarises the main conclusions of the workshop and discusses the next steps for integrating these priorities into the product roadmap. Participants are encouraged to think about how they can use the Kano Model in their daily work.

    TipSuggest regularly reviewing the categorisation of features to adapt to market changes and user expectations.

Variants

  • Use real features from your current product for a more concrete approach.
  • Add a step where participants must predict how features might evolve over time.
  • Integrate a brainstorming session to identify new exciting features.

Debrief guide

  • How has the Kano Model changed your perception of feature prioritisation?
  • What difficulties did you encounter when categorising features?
  • How could you integrate this model into your current development process?
  • What advantages do you see in using the Kano Model compared to other prioritisation methods?
  • How do you think users would react to prioritisation based on the Kano Model?
  • What adjustments could you make to this workshop to adapt it to your specific context?
  • What is the next step to apply what you learned today?