A 4-step framework for building delightful products

Delight is the simultaneous experience of joy and surprise.

Professor Pratchik’s Wheel of Emotion defines delight as a combination of joy and surprise; when users feel both at once they are truly delighted.

Why: Emotions drive retention and word-of-mouth; products that spark joy + surprise create deeper user connection than pure utility.

"delight is an emotion... these two emotions are joy and surprise"

Surface confetti without value is not delight; delight must serve functional and emotional needs.

Features like shaking a phone to make snowflakes fall are superficial unless tied to real user value; avoid decorative “confetti effects.”

Why: Users quickly see through empty delight; only value-anchored experiences earn trust and repeat usage.

"that's not the light I talk about... it has to come with the value"

Remove friction, anticipate need, and exceed expectations.

Every product interaction should (1) eliminate pain points, (2) give users what they need before they ask, and (3) deliver more than expected.

Why: These three actions reliably generate the joy + surprise cocktail that defines delight.

"we need to satisfy three main pillars... removing friction... anticipating need... exceeding expectation"

All products are B2H (business-to-human); emotion matters in every domain.

Even enterprise tools like GitHub, Snowflake and Dropbox use principles like “Cupcake” or “Superhero” to honor user emotion.

Why: Human users bring emotional expectations everywhere; ignoring emotion cedes advantage to competitors who embrace it.

"as long as there are human using the product... then they need their emotion to be honored"

Ask: “If my product were a human, how would the experience improve?”

Google Meet compared itself to an in-person conversation, not to Zoom; Dyson compares vacuums to hiring a real cleaner.

Why: Human metaphors raise the bar beyond feature parity and surface unmet emotional needs.

"it's about reminding users that there are a real human behind the product"

Segment users by why they use the product, not just who they are or what they do.

Spotify users might functionally “search for a track” but emotionally “want to feel less lonely”; map both sets of motivators.

Why: Emotional motivators reveal product opportunities that demographic or behavioral segmentation miss.

"the third type of segmentation... is the motivational segmentation... why do they use the products"

Plot solutions on a 2×2 of functional vs emotional motivators to classify Surface, Low, or Deep Delight.

Surface = emotion-only (e.g., Spotify Wrapped), Low = function-only, Deep = both (e.g., Discover Weekly).

Why: Explicitly balancing the matrix prevents over-investing in decorative features and under-investing in high-impact deep delight.

"deep delight... happens when you have a feature where you are at the same time solving for a functional need and also solving for an emotional need"

Allocate 50 % function-only, 40 % deep delight, 10 % surface delight.

Ensures the product works first, then systematically layers in emotion without abandoning core utility.

Why: Provides a concrete prioritization guardrail so teams don’t swing too far toward either pure utility or pure delight.

"50 % of your features should be for low delight... 40 % for deep delight... 10 % for surface delight"