From Product Onboarding Steps to a 7-Day Teach Reel Sequence
Map activation checklist items into a day 1–7 teach series: one intent per Reel, what to skip, and why not one mega-tour video.
From Product Onboarding Steps to a 7-Day Teach Reel Sequence
Map activation and onboarding steps into a short teach series. One checklist item becomes one Reel—not a single guided tour that nobody finishes.
PLG marketers and customer education leads already have onboarding checklists. The failure mode is narrating the whole product in one video. CRM funnel cadence is a different calendar (CRM stages → weekly teach cadence); this piece is the first-week activation map for vertical teaches.
Day 1–7 intent map
Start from the checklist users must complete to reach the activation event. Example pattern (adapt to your product—do not invent benchmarks):
| Day | Viewer intent | Source checklist item | Skip if |
|---|---|---|---|
| 1 | Orient: what “done” looks like | Welcome / outcome promise | Pure brand film with no teach |
| 2 | Create the first object | Empty-state action | Advanced settings |
| 3 | Invite or share safely | Seat / permission step | Billing deep-dives |
| 4 | Core loop once | Primary workflow | Edge-case power features |
| 5 | Fix the common stall | Top Day-3 drop-off error | Rare enterprise paths |
| 6 | Read a signal | Dashboard / insight | Full reporting suite |
| 7 | Habit cue | Recurring action / digest | Upsell pitches |
One intent per Reel. If a day has two intents, split into two Reels or defer one—do not merge.
Related finishing patterns: onboarding videos users finish and first-week onboarding checklist.
What to skip in week one
- Admin-only configuration
- Competitive positioning
- Pricing and plan comparisons
- Full keyboard shortcut tours
- Every integration
- Brand history
Those belong in later series or help docs. Week-one Reels protect time-to-value.
Anti-pattern: the mega-tour
One 4-minute “complete walkthrough” fails because:
- Mute-first viewers cannot skim
- Drop-off hides which step failed
- Updates require full re-renders
- New users need day-shaped spacing, not a firehose
Prefer seven micro-boards approved before batch render. Ship daily or every other day; keep order stable even if publish timing flexes.
Board pack before batch
For each day:
- Micro-intent line
- Hook using user language
- 2–4 teach beats max
- One stall tip (especially Day 5)
- Soft next → tomorrow’s intent (series nav end cards once live)
- UI crops annotated for accuracy
Batch with one style lock (week of explainers from one style lock).
Measuring the sequence
Use activation checklist completion and day-N retention you already track—not vanity views alone (measure beyond views). If Day 3 Reels get saves but invite completion stays flat, the Reel may teach the wrong stall—or product friction needs a fix beyond content.
Building the intent map from a real checklist
Export the in-product checklist or empty-state tasks. For each item ask:
- Is this required for activation?
- Can a stranger learn it in ≤60s mute-first?
- Does it need UI demonstration?
- Is it day-shaped (early) or power-user (later)?
Items failing (1) drop from week one. Items failing (2) become docs. Items failing (3) may be tip-grids. Items failing (4) move to week two+.
Sample beat budgets per day
- Days 1–2: more orientation + first action; shorter method
- Days 3–4: denser method steps; introduce one constraint
- Day 5: troubleshooting grammar (error → cause → fix)
- Days 6–7: interpretation + habit; lighter UI, clearer framework stills
Align holds with readable pacing (pacing templates). Do not accelerate VO to cram a tour into day 4.
Cross-linking the sequence
Each Reel’s end card should point to the next day’s intent once published. Until day 7 exists, point to the relevant public doc. After the week ships, add a playlist or series hub in bio/docs—not seven competing CTAs on every episode.
Team roles
- PMM: intent map + claims
- Education: accuracy of steps
- Production: boards/stills/render
- Support: Day 5 stall validation
- Comms: publish schedule
A 7-day sequence is an ops object. Assign owners or the series stalls on day 3.
Example day cards (workspace product)
- Day 1: “Done means one shared workspace live”
- Day 2: “Create your first project board”
- Day 3: “Invite without duplicate seats”
- Day 4: “Complete the core loop once”
- Day 5: “Stuck on invite loop? Fix it”
- Day 6: “Read your first activity signal”
- Day 7: “Set the weekly digest habit”
Swap nouns for your product; keep one job per day.
Soft production tip
Approve seven micro-boards before batch render. Tools like Scro fit the pattern: lock each day’s beat map, generate stills, then render—so launch week does not invent prompts under pressure.
Checklist
- Activation event defined
- Seven intents mapped from real checklist
- Mega-tour rejected
- Skips listed explicitly
- Boards approved before render
- Series navigation planned for days 2–7
- UI labels match production
Onboarding teach sequences work when each day answers one job the new user must finish—nothing more.