Build a stakeholder update cadence with tiered depth

Stakeholder Updates: Write Once, Reuse Three Times

Writing the same update three times — Slack, weekly email, quarterly memo — costs hours per PM per week with no compounding. Basecamp's Getting Real and First Round Review's communication research both document the tiered update pattern: Tier 1 Slack for tactical awareness, Tier 2 biweekly email for cross-functional stakeholders, Tier 3 quarterly memo for leadership. The compounding rule — T1 feeds T2 feeds T3 — is what reduces total write time while preserving content quality.

How the Build a stakeholder update cadence with tiered depth Prompt Works

The prompt establishes three tiers with strict word caps and forces compounding reuse so T1 feeds T2 feeds T3. The "one recurring section I'd cut across all tiers" output is the honesty check — most updates contain one ritual section nobody reads.

When to Use It

• You're spending >2 hours/week writing similar updates in different formats.
• Updates are inconsistent and stakeholders are asking for standardization.
• A new PM is establishing communication rituals.
• A leadership team is asking for a reliable update cadence.
• A cross-functional initiative needs multi-audience updates.

Common Pitfalls

• Writing each tier from scratch. You'll burn hours weekly. Compound from Slack to email to memo.
• No word caps. Updates inflate without limits. Caps force selection.
• Same content at every tier. Executives don't need the Slack detail; the team doesn't need quarterly summary. Tier-appropriate.

Sources

• Getting Real — Basecamp
• First Round Review — First Round
• The Product Manager — Silicon Valley Product Group
• Google re:Work — Google