The Delight Model
A 4-step process to find the highest-ROI delight opportunities instead of shipping low-value confetti
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 95%
A repeatable four-step model for systematically building delight into products without changing your existing ways of working. It moves teams from vaguely 'wanting to delight users' to concretely identifying which features blend functional and emotional value. Each step feeds the next: motivators become opportunities, opportunities become categorized solutions, and solutions get validated against a checklist.
Origin
Developed by Nesrine Changuel from her time as a dedicated 'delight PM' at Google (Chrome, Google Meet) and prior roles at Spotify and Skype, and published in her book 'Product Delight.' The theoretical basis (delight = joy + surprise) she credits to psychologist Robert Plutchik's Wheel of Emotions.
Core principles
- 01Delight serves both a functional need and an emotional need at once, not joy sprinkled on top of utility
- 02Delight is a differentiator and growth strategy in crowded markets, not a luxury or 'cherry on top'
- 03You don't have to do all three delight levers at once; every feature should consider at least one
- 04Emotion must sit at the heart of the experience and be tied to a concrete business value
How to run it
- 1
Identify user motivators (functional and emotional)
Add a third segmentation axis beyond demographic and behavioral: motivational segmentation, i.e. WHY people use the product. List both functional motivators (find a specific track, get inspired) and emotional motivators (feel less lonely, change my mood, feel secure). Split emotional motivators further into personal (how the user wants to feel) and social (how they want others to perceive them).
Pro tip When users struggle to name what makes them happy, ask instead what frustrates or stresses them and identify emotional DEMOTIVATORS; it is often easier to surface. Use Plutchik's Wheel of Emotions as a menu, but only pick emotions specific to your product.
Watch out Do not skip the emotional motivators; they are used in later steps and most teams stop at functional jobs-to-be-done.
- 2
Convert motivators into product opportunities
Turn each motivator into a product opportunity to be solved, shifting the framing from 'problem space' to 'opportunity space' because solutions can honor needs, not just fix problems. Put these opportunities into the strategy. Any ideation tool (e.g. 'How Might We') works.
Pro tip Don't be religious about which ideation framework you use here; the value is in starting from the motivators, not the tool.
- 3
Identify solutions and place them on the Delight Grid
Build a matrix (the Delight Grid) with functional motivators on one axis and emotional motivators on the other. Place each candidate solution based on which motivator(s) it serves, sorting features into three types: Surface Delight (emotional only, e.g. Spotify Wrapped, Apple Watch birthday balloons), Low Delight (functional only), and Deep Delight (both at once, e.g. Discover Weekly, Chrome inactive tabs).
Pro tip Deep Delight is the most powerful category: take a feature you'd build for pure function and build it slightly differently so users also feel valued, seen, or understood.
- 4
Validate with the Delight Checklist
Run each candidate feature through a checklist before building to ensure it delivers real user and business impact, not just aesthetics. Key checks include: user impact, business impact/KPI alignment, feasibility, familiarity, a plan to sustain the delight over time, and above all inclusion.
Pro tip Add a 'maintenance plan' check: because surprise wears off (the habituation effect), require a roadmap to renew the delight over time, the way Google Meet evolved backgrounds from blur to static image to video to immersive to AI-generated.
Watch out Skipping the inclusion check is dangerous: a delight feature that assumes everyone shares the same happy context can backfire badly (see the Mother's Day fake-missed-call example).
In the wild
Tasked with tab management on Chrome iOS, Changuel's team interviewed users and discovered a genuine emotional relationship with open tabs, some users kept them as reminders and felt shame or refused to let Chrome close them. Rather than just compress thumbnails for performance, they built 'inactive tabs,' which auto-moves tabs untouched for 21+ days into a folder.
→ A cleaner tab grid that reduced stress while preserving trust, because tabs were never deleted, just grouped, an example of deep delight solving function and emotion together.
Discover Weekly was designed to be 100% new music. After launch, engineers found a bug injecting some already-liked songs into the playlist. When they fixed the bug to make it fully new, all the success metrics dropped, revealing users loved the injected familiarity.
→ They effectively kept the 'buggy' familiar-plus-new version, which is why familiarity became a permanent item on the Delight Checklist.
Common mistakes
Stopping at functional motivators
Most teams segment by demographics and behavior and identify only functional jobs. Without the emotional motivators, step 3 has nothing to place on the emotional axis and you can only build low delight.
Confusing confetti for delight
Shake-the-phone snowflakes or gratuitous animation with no value is the 'confetti effect.' Confetti is fine only when it carries real meaning (e.g. Airbnb celebrating a renewed Superhost badge).
Is it for you?
Best for
Product managers and teams in crowded, competitive markets who keep being told to 'delight users' but have no repeatable method to decide what is actually worth building.
Not ideal for
Green-field products solving a hair-on-fire pain with no competition, where simply making the core function work is enough to win (at least until competitors arrive).
From the transcript
“It happens in four steps.”
“the very first step is about identifying users motivators”
“the second step is to convert those motivators”
“There's the surface delight when a feature is only solving for an emotional motivator”
“The second type of delight is what I call low delight”
“the third type which is the most powerful for me is the deep delight”
“The the fourth step which is the last step of the model is validating”
“I created something that I call the delight checklist”
“So inactive tabs is that ability where you can actually this this happened automatically where all tabs um longer than 21 day”
“So they fixed the bug and now with discover weekly that you're enjoying is a buggy version if we can say”
From the episode
A 4-step framework for building delightful products
Nesrine Changuel (Spotify, Google, Skype)