Why journeys beat blasts

The one-off campaign is the default unit of marketing work, and it is easy to see why: you write it once, you send it once, and the report arrives the next morning. The trouble is that it is scheduled around your week rather than the customer’s. Someone who signed up an hour ago and someone who has been quiet for eleven months receive the same message on the same Tuesday, and neither of them was waiting for it.

What the blast actually optimises for

A blast optimises for the sender. It fits neatly into a content calendar, it produces a single number to report, and it feels productive. What it cannot do is respond to anything. If a contact opens the first message and ignores the second, the third one lands anyway. If they buy on Wednesday, the Thursday send still promises the thing they already own.

Relevance is mostly a timing problem wearing a content problem’s clothes.

What a journey changes

A journey inverts the schedule. Instead of a date, the first step has a trigger — a signup, a purchase, a form submission, a segment a contact drifted into. Everything after it is described relative to that moment: wait two days, check whether they came back, branch, send the version that matches what they actually did.

• The trigger decides when each contact starts, so nobody is early or late.
• Waits are relative, so a two-day follow-up is two days for everyone.
• Branches let one journey serve people who behaved differently, without a second campaign.
• It keeps running after you stop thinking about it, which is the whole point.

Start with the one you already send by hand

The best first journey is almost never a clever one. It is the message you already send manually and inconsistently — the welcome note, the nudge after an abandoned signup, the check-in a fortnight after the first purchase. Automate that one first. It is the message with the clearest trigger, and it is the one whose absence you can already feel.

Campaigns keep their place. Announcements, launches and seasonal sends really are calendar events, and they should stay that way. But the work that compounds is the work that runs whether or not you opened the app this week.