Why usable products can still feel disposable — and what to do about it

Don Norman introduced emotional design as a three-level framework in his 2003 book Emotional Design. Each level operates differently — and calls for different design decisions.

Visceral is immediate and automatic. It's the first impression: how something looks, sounds, or feels before you've used it. Visceral responses are pre-rational. They happen before users consciously evaluate anything.

Behavioural is functional. It's the satisfaction of using something that works well — smooth feedback, clear affordances, controls that respond as expected. This is the layer most UX work happens at.

Reflective is meaning and identity. It's how using a product makes you feel about yourself. "I'm the kind of person who uses this." It's where genuine loyalty lives — and it's the layer least often designed for intentionally.

Products that operate only at the behavioural level — usable, efficient, clear — can still feel forgettable. Users complete tasks without friction but have no particular attachment to the product. Switching cost is low. When a competitor offers something comparable, there's nothing holding the user in place.

Norman's point wasn't that usability doesn't matter. It's that usability alone doesn't build the kind of relationship that sustains long-term retention. Affective response — how a product makes you feel — is a stronger predictor of continued use than ease-of-use scores alone.

A product can score well on a System Usability Scale evaluation and still churn at high rates. The functional score doesn't capture the emotional relationship.

This is where most teams underinvest. There's a persistent assumption in B2B product design that users care only about efficiency — that emotion belongs to consumer apps, not enterprise tools.

It's not accurate. B2B users bring their whole selves to work software. A product that makes them feel in control, competent, and informed creates a fundamentally different relationship than one that makes them feel confused or overwhelmed. The reflective layer still operates — "this is the tool that makes my job make sense" is an emotional response, not a functional one.

For teams working on Embedded Design or internal tooling, getting the emotional layer right is often the difference between adoption and avoidance. Internal tools that feel considered get used. Internal tools that feel designed for the system rather than the person get routed around.

The three levels call for different inputs:

Visceral:

• Visual craft — the product should look like it was made with care
• Motion and animation that feel considered, not tacked on
• Microinteractions that add texture without distraction

Behavioural:

• Tight feedback loops — every action should have a clear, immediate response
• Error States that respect the user's intelligence rather than making them feel at fault
• Flows organised around how people think, not how the underlying system is structured

Reflective:

• Tone of voice that treats users as capable professionals
• Personalisation that makes the product feel like it knows how you work
• Milestone moments — first task completed, a goal reached — that acknowledge progress in a way that means something

Emotional design gets misapplied when teams focus on the visceral layer while the behavioural layer is still broken. Delightful animations and playful copy on top of an experience that doesn't work isn't neutral — it's a gap between promise and reality that users feel immediately.

The failure pattern is familiar: high initial engagement, poor retention, reviews that say "looks great but frustrating to use." The appearance created expectations the product couldn't meet. That gap makes the functional problems feel worse than they would in a more honest interface.

The framework only works as a stack. Substance at the behavioural level comes first. The emotional layer built on top is what turns a product that works into one people don't want to stop using.