Lesson 04 of 8
Five-message journey architecture
Give each message a distinct job, set pacing by reader effort, and add only branches that change the experience.
By the end of this lesson
- Use the five-message decision path as an architecture, not a rigid cadence.
- Choose timing based on the resource and decision effort.
- Document branch fallbacks when tracking is unavailable.
3.1 Use a five-message decision path
The default architecture is a five-message sequence. Adjust timing to the context, but preserve the job of each message.
| Message | Job | Subscriber question |
|---|---|---|
| Welcome and deliver | Fulfill the signup promise and set expectations | Did I get what I asked for? |
| Diagnose the situation | Help the reader recognize the real problem | Why does my current approach feel difficult? |
| Teach the mechanism | Explain a useful method they can apply | What should I do differently? |
| Make the offer legible | Show fit, contents, boundaries, and tradeoffs | Is this the right next step for me? |
| Support the decision | Resolve remaining uncertainty without pressure | What do I need to decide responsibly? |
3.2 Pace by reader effort
Timing is a design choice, not a universal formula. Consider:
- How quickly the free resource can be used.
- Whether the topic is urgent or reflective.
- The length and complexity of each message.
- Existing newsletter frequency.
- Time zones and local sending rules.
- Whether a purchase should exit the subscriber from sales messages.
A reasonable starting pattern for a non-urgent educational product is immediate delivery, then spacing messages across several days. Treat this as a hypothesis and review actual behavior.
3.3 Design branches sparingly
Start with one clear path. Add a branch only when it changes what the subscriber should receive.
Useful branches:
- Customer versus non-customer.
- Chosen topic or declared goal.
- Product-specific eligibility.
- Meaningful engagement with a decision resource.
Weak branches:
- One open that may be unreliable.
- Tiny timing differences with no content consequence.
- Complex scoring that nobody reviews.
Document fallback behavior when tracking is unavailable.
Working session
Apply it now
Draft the five rows of your flow map. For every message, name the reader question, communication job, primary action, and exit condition.
Lesson resources
Download a working copy, complete it locally, and return to the lesson when you need the decision logic.
Local progress only
Finish the lesson
This open preview has no account. Completion is stored only in this browser and can be reset at any time.