I’ve written about the lifecycle of successful product features before (and the opportunities it harbours).
But that’s not the only lifecycle pattern found by researchers. Noriaki Kano suggested there was another type, one that other researchers have dubbed the “flavour-of-the month”-lifecycle (Löfgren et al, 2011).
If you’re doing regular Kano studies on the same features, and you see a feature rising from Indifferent to One-Dimensional in a flash (or the other way around), chances are you’ve got yourself a flavour-of-the-month feature.
“For quality attributes [aka features] that follow this life cycle, the change from indifferent to one-dimensional happens quickly; the quality attribute becomes the selling point of the product soon after market introduction.” (Löfgren et al, 2011, my emphasis)
It sounds great, and up until a certain time it is, but this is a dangerous life cycle.
The feature that rises from Indifference to Perform can be mesmerizing. Its instant success makes you believe it has some kind of magical property. And when its success starts waning, you believe that users should just rediscover your magical property and all will be fine again. Everyone knows stories about product teams that clung to obsolete product features while everyone else knew these features were no longer relevant.
These types of features are particularly dangerous because they usually are a defining feature of the product. When such a feature moves back into oblivion, it can easily take the whole product with it.
Armed only with a Kano analysis, the best way to recognize flavour-of-the-month features is by their very definition and observed movement:
They are a defining feature of your product, its selling point;
Over the course of time, they move from Indifferent to One-Dimensional or back.
Everyone recognizes a flavour-of-the-month feature when they see it, except when it’s their own. So whenever you suspect you might have a flavour-of-the-month feature on your hands, go out and talk to your customers.
How to handle a flavour-of-the-month feature
When you have established that a feature is a flavour-of-the-month feature, make sure you’re not putting all of your eggs in that one basket. Open up efforts to develop new features that can bring more sustainable success to your product. Revisit the original latent requirement and find other solutions.
Let the flavour-of-the-month feature follow its prescribed path. Invest in it as long as you see results. When it starts crawling back to the Indifference category, let it go. Be ready to accept that its success is not repeatable.
Actions to undertake for a feature that goes through a flavour of the month life cycle:
Feature Category Competitive Advantage Actions to undertake
Indifferent Unknown Promote usage
🠗
Perform Feature performance Measure satisfaction of
(better, more, …) incremental changes and
🠗 stop investing when return
on satisfaction is too low
Indifferent None Remove feature
Personal note: As you see, this newsletter isn’t dead. I’m as enamoured with the Kano model as ever, but life and work have a tendency to keep interfering. Luckily, work includes doing Kano studies, so I’ll keep posting here, albeit very irregularly.