2 min lesson
Designing a coherent sequence
Give a plain answer to "Why does the 'breakup' message at the end of a sequence often earn surprise replies?" Then ground it in one lesson detail.
Step 1 of 2
A sequence is a short story told across touches, not the same message sent five times until they break. Each step changes the angle so a non-reply on touch one doesn't doom touch three.
The take-home sometimes asks for the full sequence and graders look for an arc. The classic angles move from their problem, to proof it's solvable, to a peer who solved it, to a graceful exit.
Interactive diagram. Step through it with the Next and Previous controls below, or Tab to a region to read its detail.
A short story across touches, not the same message five times. The breakup is the gate that surfaces who's actually alive.
Learn more
Advanced table
Roughly two weeks, mixed channels, each touch a different angle
- Day
- Day 1
- Channel
- Angle
- Problem - personalized hook + soft CTA
- Day
- Day 2
- Channel
- Angle
- Connection request, relevance only
- Day
- Day 4
- Channel
- Call
- Angle
- Quick voicemail referencing the email
- Day
- Day 6
- Channel
- Angle
- Proof - one capability or result
- Day
- Day 9
- Channel
- Angle
- Peer - a comparable team's story
- Day
- Day 12
- Channel
- Angle
- Breakup - graceful exit
| Day | Channel | Angle |
|---|---|---|
| Day 1 | Problem - personalized hook + soft CTA | |
| Day 2 | Connection request, relevance only | |
| Day 4 | Call | Quick voicemail referencing the email |
| Day 6 | Proof - one capability or result | |
| Day 9 | Peer - a comparable team's story | |
| Day 12 | Breakup - graceful exit |
Roughly two weeks, mixed channels, each touch a different angle. Spacing is sensible, not daily.
The breakup message earns surprise replies because it removes pressure and triggers loss aversion. “Sounds like the timing's off - I'll close this out unless I'm wrong” often gets a “wait, actually…” It's also honest, which fits an engineer's expectations.