Build a stakeholder update cadence with tiered depth
Storytelling
0 uses
Updated 4/17/2026
Description
You're writing the same update three times — short for Slack, medium for the weekly, long for the quarterly — and it's eating your Fridays. This builds a tiered cadence with templates at each depth so each write compounds and you stop re-editing.
Example Usage
You are designing a stakeholder update cadence for {{team_name}}. Stakeholder tiers: {{tiers}}.
## Three tiers
### Tier 1 — Weekly Slack (3-5 sentences)
- Shipped this week: 1-2 bullets
- Shipping next week: 1-2 bullets
- Risks/asks: 1 sentence
### Tier 2 — Biweekly email (400 words max)
- Headline: 1 sentence on progress vs. goal
- Shipped (2 weeks): detail on impact
- Currently building: what, why, when
- Risks and decisions needed
- Metric highlights
### Tier 3 — Quarterly memo (2 pages max)
- Quarter highlights
- Metrics vs. goals
- Key decisions made and why
- What we learned
- Next quarter focus
- Asks
## Compounding rule
Each tier reuses language from the previous:
- Slack → email: copy the previous 4 Slacks, expand with context
- Email → memo: copy the previous 6 emails, synthesize
## Ownership
- PM writes T1 + T2
- PM + EM co-author T3
- Approval: none for T1, lead review for T2, leadership review for T3
## Output
1. Templates for each tier
2. The compounding workflow (Slack → email → memo)
3. The one recurring section I'd cut across all tiers
4. The first T2 email based on last 2 weeksCustomize This Prompt
Customize Variables0/2
Was this helpful?
Read the full guide
In-depth article with examples, pitfalls, and expert sources