Onboarding flows for small teams

The advice here is unglamorous, which is probably why it gets skipped. Most advice about onboarding flows assumes a team that does not exist at your size. Here is the version that does not.

Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. It rarely shows up as a line item, which is exactly why it slips.

What to keep

Every extra step before value loses people. In practice this is a scheduling problem more than a technical one. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

What to drop

Process that exists to coordinate ten people is overhead when there are two of you. Small and consistent beats large and occasional here.

Where to start

Show progress so the end feels reachable. The cost of getting this wrong is rarely visible on the day it happens. If two people in the business would answer this differently, that gap is the actual problem.

In practice

The measurable part of design is whether people can find what they came for and act on it without hesitating. Three things worth confirming about onboarding flows before you move on:

• Someone can say what the current setup is without going to look
• Show progress so the end feels reachable — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If any of that sounds like a description of your current setup, it is fixable.