Make Them Feel It, Then Make Them Act: Emotional Design Against Norman's Three Levels

Most teams treat emotional design as decoration. They pick a warmer blue, round a few corners, add a bouncy animation, and call the product friendly. Then retention stays flat and nobody can say why. The problem is that feeling and behavior got decoupled. A user can enjoy your screen and still leave. The fix is to tie every emotional choice to an action you want, and to check that your color, type, and small moments all pull the same way.

The deep cut

• Feeling must cash out as behavior. Ivacan ties emotional design to Norman's three levels precisely to move what users do, not just how they feel.
• Decoration without direction loses users. Adam Fard's retention killers, clunky UI and slow loads, undo any warmth your visuals add.
• Make color and type agree before you animate. Jakub Wojciechowski warns that mixed signals cancel the feeling you intended.

Start with the behavior, not the mood

The trap is designing for a vibe. You want the app to feel calm, or bold, or playful, so you chase that feeling and stop there. A feeling with no job attached is just paint. Before you touch a single color, name the action you want. Sign up. Finish onboarding. Come back tomorrow. Then ask what feeling pushes someone toward that action.

Ivacan frames this through Don Norman's three levels: the gut reaction to how something looks, the feeling of using it, and the story a user tells about themselves after. Each level is a lever on behavior. When you map a feeling to an action, you stop arguing about taste and start arguing about outcomes.

The three levels are three jobs, not three moods

Norman's levels sound academic until you turn them into work. The first level is the snap judgment people make in a second. That is color, shape, first impression. The second is how the thing feels to use, the flow and friction. The third is the meaning that sticks, the reason someone recommends you or renews.

Treat each as a separate job with its own test. Does the first screen read as trustworthy in a glance? Does the core task feel smooth or do people stall? Does finishing leave someone proud or relieved? If you can only point to the pretty first layer, you have decorated the lobby and left the stairs broken.

Microinteractions earn their keep when they confirm progress

Small animations get oversold. A confetti burst that fires on every tap turns into noise fast. Jakub Wojciechowski ties microinteractions to connection, and the useful read is this: a small moment earns its place when it tells the user something true. A save confirmed. A step done. A loading state that shows the system is alive.

Use them to reduce doubt at the exact point a user might quit. The checkout button that reacts. The form field that confirms before you move on. Those moments change behavior because they answer a real question: did that work? Delight that does not answer a question is just friction with a smile.

A pretty flat product still bleeds users

Here is the humbling part. You can get the feeling right and still lose people to boring mechanics. Adam Fard lists the plain retention killers: too many ads, slow load times, bad reviews, clunky UI. No palette survives a three-second load. Emotional design sits on top of competence, not instead of it.

So audit the basics before you polish the mood. Time the load. Count the taps to the core action. Read your worst reviews out loud. The strongest emotional lever you have is often just making the thing fast and clear, which is its own kind of warmth. Fix the leaks, then make it feel like something.

Write the insight down so the feeling survives handoff

Emotional intent dies in translation. The designer feels it, the engineer ships what is specced, and the feeling never makes the trip. Guard against that by writing the insight plainly, the way Rick Swette collects real anecdotes instead of textbook rules. His examples, like why the first song's quality drives whether a Spotify playlist catches on, show what a sharp insight sounds like.

Write yours the same way. Not "users like delight" but "users abandon at the second form field because they doubt the save worked." A specific insight tells the whole team which feeling to protect and which action it serves. Vague ones get sanded off in the build.

Three questions for your team

• What single action are we trying to move, and which feeling pushes someone toward it? Tie every color, type, and animation choice to that answer.
• Are our color and type pulling in the same direction, or canceling each other out before we even add motion?
• Which retention killer hits us hardest right now, and have we fixed it before spending a sprint on polish?