The drip is a guess that never updates
Most onboarding flows are a drip: five emails, fixed days apart, sent to everyone who signs up. Day 0 welcome, day 2 feature tour, day 5 case study, and so on. It feels organized. It is mostly a guess — one made on the day you built it, frozen forever, indifferent to what the person in front of you actually did.
The problem isn’t the timing. The problem is that a drip treats a brand-new stranger, a returning customer, and someone who quietly went cold as the same person. They are not. They sit at different points in their relationship with you, and a sequence that ignores that will, at best, be ignored right back.
A branch map starts from a different question. Not what do I want to say next, but what state is this person in, and what’s the one move that gets them to the next state.
Optimize for the ambitious behavior, not the easy click
Every onboarding needs a main goal and a few intermediate ones. The mistake is picking goals that are easy to hit instead of goals that matter. An email open is easy. A click is easy. Neither tells you the product earned a place in someone’s week.
The goal worth chasing is the ambitious downstream behavior — a habit, a real second visit, the first action that actually delivers the value you promised. For a tool, that might be the second project created, not the first login. For a marketplace, the second order, not the first browse. Build the whole map backward from that, and the intermediate goals stop being vanity steps and start being rungs on a ladder.
When you measure the right thing, the timed-email instinct quietly dies. You stop asking which email goes on day three and start asking what has to be true by day three.
Stop asking which email goes on day three. Start asking what has to be true by day three.
Branches are where the relationship actually lives
Here’s where the map earns its name. A genuinely new user gets the full introduction. But an existing user who re-registers is a different person entirely. Don’t welcome them like a stranger; recognize them, skip the basics, and route them to whatever they came back for. Welcoming a loyal user with a beginner’s tour is a small insult that quietly costs you.
Reactivation after a long absence is its own branch: not a feature tour, but a reason to return — what changed, what they’re missing, one concrete pull. Then the triggers. A day-three branch for still no first meaningful action — not another scheduled email, but a fork that fires only because the action didn’t happen, and tries a different door. Finally, a pre-churn reconnection: one honest reach-out before you stop spending on this person. Not desperate. Just a last, specific reason to come back.
The drip sends the same thing into all of these states and hopes. The branch map looks at where someone actually is and sends the one thing that fits. That’s the whole difference — between a sequence that runs and a system that responds.