Designing an onboarding journey around one first action

The standard onboarding programme is a five-email tour of the product. Email one welcomes, emails two to four each explain a feature, email five asks for a review. It is easy to build, easy to approve, and it rarely changes retention.

The problem is the premise. New customers are not short of information about your product, they are short of a reason to come back tomorrow. A tour answers a question they have not asked yet.

We build onboarding journeys backwards from a single behaviour: the first action that reliably predicts whether someone is still here in ninety days. Everything in the programme either moves a person towards that action or gets cut.

Find the activation moment in your own data

Every product has a threshold behaviour. Completing a profile, making a second purchase, inviting a colleague, listening to three episodes, adding a payment method. Your version is in your data already.

Find it this way. Take everyone who signed up between six and twelve months ago, split them into retained and churned, and compare what each group did in their first fourteen days. Look for the behaviour where the gap between the two groups is widest.

Then check that the relationship holds when you control for obvious confounders such as acquisition channel and plan tier. Plenty of correlations are just a proxy for high-intent traffic, and building a programme around one of those wastes a quarter.

Write the result as a single sentence with a number and a window. Customers who complete two bookings within fourteen days retain at roughly three times the rate of those who complete one. That sentence is the brief for the whole journey.

Map the first thirty days backwards from that action

Start at the activation moment and work backwards through every step a person must take to reach it. Account created, verified, preference set, first item added, first order placed, first order received.

For each step, write down the obstacle rather than the feature. People do not fail to set a delivery preference because they never heard of delivery preferences. They fail because they were on a phone, mid-commute, and the form asked for a postcode they could not remember.

Then decide which obstacle a message can genuinely remove. Some cannot be solved by CRM at all, and naming those honestly is useful, because it sends the problem to the product team where it belongs.

The remaining obstacles become your message set. In most programmes that is four to seven messages across thirty days, not the fifteen that a feature tour produces.

Build the triggers on behaviour, not on elapsed time

A time-based drip sends message three on day five whether or not the person has already done what message three asks for. That is how customers end up being told to complete a step they finished on day one.

Use your segmentation layers here. State decides whether someone is in the onboarding programme at all, behaviour decides which message fires next, and attributes decide the content inside it. The three-layer framework keeps this manageable once the journey has branches.

Practical rules we hold to:

• Every message has an entry condition and an exit condition, both written before the copy.
• A person exits the step the moment they complete its action, even if the message is queued.
• Time-based sends exist only as a fallback when no behavioural signal is available.
• Maximum one onboarding message per person per day across all channels, enforced centrally.
• The whole programme has a hard exit at thirty days, after which people move into business as usual.

That last rule matters. Without a hard exit, people accumulate in onboarding for months and receive a strange mix of beginner guidance and promotional campaigns.

Write to the obstacle and measure the action

Onboarding copy should be short, specific and single-purpose. One message, one action, one link. The subject line names the obstacle, the body removes it, and nothing else competes for attention.

Measure each message on completion of its step, not on opens or clicks. A message with a modest open rate that moves sixty per cent of recipients through a step is doing its job better than a widely opened message that moves nobody.

Report the programme on one number: the share of new customers who reach the activation moment within the window. Track it weekly by signup cohort, since a monthly average hides the effect of every change you make.

Test one variable at a time, and give each test a full cohort before reading it. Onboarding volumes are usually smaller than broadcast volumes, so patience is the difference between a result and a coincidence. The build and iteration side of this sits in our execution work.

What to do this week

• Pull the first fourteen days of behaviour for retained and churned cohorts, and identify the action with the widest gap between them.
• Write the steps to that action in order, with the real obstacle named under each one, and mark which obstacles a message can remove.
• Add an explicit exit condition to every message in your current onboarding programme, plus a hard exit at thirty days.