Every product team has a set of patterns they reach for when designing onboarding. Most of them assume the new user is paying close attention.

They aren't.

The reality of a first session

A new user drops into your product after clicking a link. They have one tab in a stack of fifteen. They've heard about you for six seconds. They will give you about ninety more before deciding whether to stay.

That's the entire window. Tooltips, video walkthroughs, multi-step setup wizards. All of these assume more attention than you have.

Three patterns we use instead

Show the win in the first screen. The first screen after sign-up should contain the thing the user came to do — already half-done, with their name on it. We pre-create their first project. We pre-fill it with a working example. The first interaction is editing, not setting up.

Defer everything you can. Settings, integrations, team invites, billing setup — none of these belong in the first session. They belong on the third visit, when the user has already decided you're worth coming back to.

Treat the empty state as the homepage. New users see the empty state more than any other screen. Most teams design empty states last, as an afterthought. We design them first.

What this looks like in practice

The new user lands on a working preview with sample content, edits something, sees the change reflected immediately. That's the entire onboarding. They've done the thing the product does. Everything else is permission to keep going.