A short guide to onboarding flows

It comes up on almost every project, usually later than it should. Everything we would tell a client about onboarding flows in the time it takes to drink a coffee.

Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. If two people in the business would answer this differently, that gap is the actual problem.

Why it matters

Every extra step before value loses people. In practice this is a scheduling problem more than a technical one. It is worth deciding this deliberately rather than inheriting whatever the last person set up.

The practical version

Ask for information when you need it, not up front. The reasoning matters more than the rule, because the rule has exceptions. If two people in the business would answer this differently, that gap is the actual problem.

The mistakes we see most

Show progress so the end feels reachable. There is a version of this that is over-engineered, and it is worth avoiding. It rarely shows up as a line item, which is exactly why it slips.

In practice

Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. Three things worth confirming about onboarding flows before you move on:

• Someone can say what the current setup is without going to look
• Every extra step before value loses people — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Pick the one that would hurt most if it failed, and start there.