Designing for the second glance

The first time someone uses your product, they're not really using it. They're deciding whether to use it. Their attention is wide and shallow. They see your hero, they see your CTA, they see whether things look broken. The first glance is mostly defense — they're looking for reasons to leave.

The second glance is different.

The second glance happens after a user decides to stay. Their attention narrows. They notice the things you didn't think they'd notice — the empty state in a corner of the dashboard, the way a tooltip animates, whether the keyboard shortcut you mentioned in the docs actually works.

What survives the second glance

I keep a list. It started as a way to talk to my team about the difference between "looks good in Figma" and "feels good after a week."

• The empty state is written like a person wrote it
• Loading is fast enough that the spinner is a backup, not a feature
• The error message says what to do next, not just what went wrong
• The button you'll press most often is the easiest button to press
• The setting you toggle once a year is in the right place — but not in the way

None of this shows up in a screenshot. None of this is in the brand guidelines. None of this gets reviewed in a design crit.

The second-glance test

When I'm reviewing a feature, I try to ask: what will the tenth user notice? Not the tenth visitor — the tenth use. What's the thing that will start to grate, or start to delight, the more often they touch this?

That's the question. The answer is usually small. The answer is almost always worth doing.