Day-based steps and why they beat triggers here

Keep the objective and the instructions apart

Of those five, one split is worth protecting. The objective is what the step is for, and it survives a change of tactic. The instructions are how it is done this quarter, with this messaging, for this segment.

Teams that write only instructions end up with plays nobody can revise, because a year later nobody can tell which part was the point and which was just how they were doing it in March. There is no branching to configure either; the timeline is deliberately linear.

Why time rather than triggers

Most automation tooling models a motion as a chain of triggers: if this happens, do that; if it does not, wait and do this instead. It is expressive, and it is close to unreadable once there are more than a handful of branches. To know what a trigger graph does you effectively have to run it in your head.

A timeline is legible in a way a trigger chain is not. You can read it top to bottom, in order, and see the entire motion, which is exactly what the Review step asks a human to do before the play goes live. That legibility is not an aesthetic preference; it is what makes review possible, and review is where the governance in this model actually lives.

Signals have not gone anywhere — they decide who enters the play, which is the next module. The division is clean: signals govern entry, time governs progress.

The gaps are part of the design

Because steps carry a position on the timeline, the interval between them is something you choose rather than something that falls out of a trigger firing. Choose it deliberately. Steps stacked too close together arrive in one person's queue on the same morning and get worked as a batch, which defeats the sequencing you just designed. Spread too far apart and each step arrives with no memory of the last, so the account experiences a series of unrelated approaches rather than a conversation.

A useful discipline when you are unsure: lay the steps out, then read the timeline as if you were the account receiving it. If the rhythm would strike you as inattentive or relentless, it will strike them the same way.

A worked example: post-pilot re-engagement

Take a motion most teams have some version of: a pilot finished, the outcome was decent, and the conversation went quiet. On a timeline that becomes four steps, and the day numbers are the design.

Day 0 is the trigger point, not a touch. The step assembles the pilot outcome, the stakeholder map and the original success criteria, and routes a briefing to the account owner. Nothing leaves the building. Day 2 is the first outreach, referencing the specific result the pilot produced, which is why it comes after the assembly step rather than alongside it. Day 9 is a second approach through a different stakeholder, because if the first landed you would not be here, and a second identical nudge to the same person is what makes buyers stop reading. Day 21 is the decision point: either the account is engaged and leaves the play, or it is not and the owner closes it out with a reason.

Notice what the intervals are doing. Two days is short enough that the briefing is still fresh in the owner's head. Seven days between the first and second approach is long enough not to nag and short enough that the pilot is still recent. Twelve days to the decision point stops the play from following accounts around indefinitely, which is the failure mode that quietly turns a re-engagement motion into a nuisance.

Three ways a timeline goes wrong

The last one is the quiet killer. A play with no end keeps accumulating accounts, and once the enrolled figure includes everything that ever entered, it stops telling you anything.

• Collapsing objective and instructions — a step whose objective reads "send email" tells a reviewer nothing about whether the instructions still serve it
• Stacking steps on adjacent days for the same owner, which turns a sequenced motion into one batch worked in a single sitting
• Building a timeline with no final step to resolve the account, engaged and out or closed with a reason