2. Designing is mostly about solving problems
• Especially in mature products
• The YOLO approach
Designing = problem solving
Especially in mature products
The Kano model is a technique for classifying customer needs into different categories, basing on how they impact users satisfaction when being met. It helps to determine appropriate levels of innovation for products and services and is often used in agile methodologies to prioritise requirements.
stay aware of different customer requirements categories,
focus on meeting basic users expectations before investing in excitement generators (which won’t increase satisfaction until basic expectations are met),
stop investing in improving must-be requirements that are already at satisfactory level
realize that users expectations change over time, so you constantly need to look for opportunities to bring innovation,
avoid the experience rot