Day 217 of the Daily · Product Management

The Kano Model

5 min read · 4 principles · apply it by lunch

Some features earn you no credit at all. Some earn it in proportion. One gets you remembered.

The question

The last five things your team shipped: which kind was each one — the sort nobody thanks you for but people leave over, the sort where more is straightforwardly better, or the sort nobody asked for and everybody mentioned afterwards — and could you say which was which without checking?

The idea

In 1984 Noriaki Kano, a professor of quality management at the Tokyo University of Science, published a paper with Nobuhiko Seraku, Fumio Takahashi and Shin-ichi Tsuji in the Journal of the Japanese Society for Quality Control. It was called ‘Attractive Quality and Must-Be Quality’, and its argument was that satisfaction isn’t a single dial. Drawing on Frederick Herzberg’s work on what satisfies and dissatisfies people at work, Kano showed that product attributes fall into distinct kinds, each paying out on a different curve. Must-be quality is invisible when it’s there and fatal when it isn’t — nobody praises a hotel for hot water, everybody leaves over the lack of it. One-dimensional quality is the honest trade: more is better, less is worse, and customers will tell you exactly where they’d like more. Attractive quality produces delight, and no survey hands it to you, because people don’t request what they haven’t imagined. Then comes the part that costs money. Kano observed that attractive attributes don’t stay attractive: today’s delight becomes tomorrow’s expectation and eventually becomes the thing you get complaints about. Free returns made that journey; so did the camera on a phone. The trap is one priority number laid across all three — three payoff curves scored on a single scale, which is how a hard quarter of shipping ends with satisfaction exactly where it started.

In the Daily · 4 principles and a template

The Kano Model is Day 217 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Product Management

The next four in the course.

All 22 Product Management frameworks
Day 227 · Product Management

Versioning

Look at the cheapest thing you sell and the dearest one, then say what actually differs between them — not the price, the product itself: is that difference a dimension your best customers would genuinely pay to escape, or a handful of things somebody switched off on a Thursday so the tiers wouldn’t look identical?

See the framework →
Day 236 · Product Management

The Opportunity Solution Tree

Pick any item on the roadmap you’re working to right now and say out loud which outcome it’s meant to move and which customer need it addresses — then work down the list item by item, and how far do you get before the honest answer becomes ‘because it was already on the roadmap’?

See the framework →
Day 245 · Product Management

The House of Quality

Your customers keep asking for the same vague thing — that it feel faster, or simpler, or more solid — and delivering it means moving one measurable characteristic inside the product: can you say which one, and in what unit? Most teams can’t. So the unit gets chosen by whoever writes the code, at the moment they write it.

See the framework →
Day 255 · Product Management

RICE

When your team last settled what to build next, could anyone in that room have said out loud how sure they were — not whether the idea was good, but how much of the case rested on a figure somebody had actually gone and looked up? I’ll give you the answer: nobody was asked, because nothing on the list carried a number anyone could argue with.

See the framework →