Delight has a budget

Move the slider from "every keystroke" to "rare milestone" and try each example. Notice how much each moment is allowed to do:

Typing gets nothing. A button gets a tiny dip. Finishing onboarding gets confetti. Swap any two and it feels wrong: confetti on every save would be unbearable by Wednesday.

The delight-impact curve

This is Benji Taylor's rule, and it is the most useful single question in this course: how often will someone see this?

Delight, the small flourishes that make a product feel alive, wears out with repetition. Something you see once a year stays fresh; something you see a hundred times a day becomes friction by lunchtime.

So when someone says "let's make this more fun", ask how often people see it. For anything frequent, the right answer is usually less visible, not more.

Marketing UI is not product UI

The same rule explains a mistake you will see everywhere: building the inside of an app like a landing page, or the reverse.

A marketing page is visited once or twice. Its job is to impress and explain. A product screen is used hundreds of times. Its job is to get out of the way.

Before reviewing any screen, ask which one it is. The same animation can be right on the landing page and wrong in the app.

Feeling right

A screen can be correct, accessible, fast and consistent, and still feel cheap. What is left after every box is ticked is whether it feels right, and it is the part an agent is weakest at. Benji Taylor put it plainly after building morphing icons with Claude: the agent got them technically correct but could not tell when something looked wrong. That judgement is yours.

Feeling right is not the same as fancy. A still screen with clear hierarchy and good type feels more right than a busy one with five animations. Restraint reads as confidence; over-design reads as anxiety.

You cannot test feel with an automated check, but you can test it:

1. The next-day review

   Build it, sleep, look again. If you still like it tomorrow, ship it. (Emil Kowalski's habit.)

2. The slow-motion replay

   Record the interaction and play it at a quarter speed. Almost every motion bug shows up frame by frame.

3. The cold-eyes test

   Show it to someone who has never seen it. Their first reaction is the truth.

4. The phone-call demo

   Demo it to a friend over a call. If they say "wait, what?", the timing is off.

Do this last, after correctness and accessibility. When something "works but feels off", the fix is rarely one property; it is usually rhythm and timing across several elements.

For every animation on this screen, tell me how often a user will see it (every keystroke, every action, daily, weekly, rare) and whether this is marketing or product UI. Remove or shrink anything that performs more than its frequency allows, and list what you changed.