Laws of PM Strategy Kano Model

Kano Model

Delight vs. Must-Haves

Features fall into three types — basics, performance, and delighters — and each type pays back differently.

Why PMs should care

Spending too much on basics is wasted effort — nobody writes a review about how smoothly the login worked. Spending too little on basics kills you — one broken password reset can drag your App Store rating down for months.

Performance features reward extra investment in a straight line: faster loading, more chart indicators, more detailed reports. Delighters are where the surprising wins come from, but they don't stay delighters for long. What felt magical in 2015 is expected in 2025 — think fingerprint login, face unlock, real-time fraud alerts.

Your job is to keep these three types in the right balance, and to remember that their definitions shift every 2–3 years. A feature that's a delighter today will quietly become a basic by the time you've caught your breath.

Example in product work

For a banking app, fraud alerts are a basic — their absence causes outrage, their presence generates zero emotion. Clear spending categorisation is a performance feature: the more accurate and granular it gets, the happier the user. An AI-drafted dispute letter that writes itself when a user contests a transaction is a delighter today.

But if two competitors ship it in the next 18 months, it will be a basic by 2027 — and the team that only shipped a delighter, without hardening the basics underneath, will have spent budget on a feature that now feels mandatory.

What to do when you see it

Sources & further reading

Back to all 59 laws