persuasion
Delighters
What are delighters in UX?
Delighters are the small, unexpected, pleasurable touches that exceed expectations and make a product feel cared-for - a witty empty state, a satisfying animation, a thoughtful surprise at just the right moment. In the Kano model they're the features nobody asks for and whose absence is never missed, but whose presence delights and builds affection.
Also known as: delighters, delight, kano delighters
Prefer to watch?
Watch the recap 1:06
The demo
You just finished a task. Here's the “done” moment, two ways - one purely functional, one with a small surprise. Trigger each and notice the difference a tiny delight makes. (The basics work in both.)
What this demo shows (text version)
The same "task complete" moment is shown two ways. The plain version is a flat, functional confirmation - it works, but it's forgettable. The delightful version is the same confirmation plus a small, well-timed surprise: a brief celebratory touch and a bit of warm, on-brand copy. Both get the job done; the delightful one also makes you smile, for very little extra cost.
That little extra is a delighter - in the Kano model, an unexpected pleasure that wins affection but isn't missed when absent. The key caveat is order: delight only lands because the basics work. Get the must-haves solid first, then add subtle, well-timed delight where it genuinely enhances - it's the icing, never the cake.
Delighters are bonus touches that lift an experience from acceptable to loved - but only once the basics work. Kano's model distinguishes must-haves (whose absence frustrates), performance features (more is better), and delighters (unexpected pleasures that win affection but aren't missed if absent). The trap is reaching for delight to paper over broken fundamentals: confetti on a checkout that loses your order is worse than no confetti. Get the must-haves rock solid first, then add small, well-timed, on-brand delight - a surprising thank-you, a playful detail, a satisfying micro-interaction - where it genuinely enhances rather than distracts. Delight is the icing, never the cake.
The plain version did the job; the delightful one did the job and made you smile - a small surprise that cost little and bought real warmth. That's a delighter. Just remember the order of operations: the delight only landed because the basics worked. Sprinkle these touches on a solid experience and people fall for it; sprinkle them on a broken one and they just feel mocked.
In the Kano model, satisfaction comes from three feature types. Must-be qualities are expected - their absence causes frustration but their presence is taken for granted. Performance qualities scale with satisfaction - the better they are, the happier people get. Delighters (attractive/exciter qualities) are unexpected: nobody requests them and their absence isn't noticed, but their presence produces disproportionate delight and emotional attachment.
Delighters are how good products become loved rather than merely tolerated: a charming empty state, a perfectly-timed animation, a surprise thank-you, an Easter egg, copy with personality, a micro-interaction that feels satisfying. They differentiate, create memorable peaks (which the peak-end rule says people remember), and signal craft and care that build affection and word of mouth.
The crucial caveat is sequence and restraint. Delight cannot substitute for working fundamentals - polish on top of a broken core reads as tone-deaf. Add delighters only once the must-haves and performance features are solid, keep them subtle, on-brand and well-timed (especially at peaks and endings), and make sure they never get in the way of the task or wear thin through repetition. Delight is a multiplier on a good experience, not a rescue for a bad one.