PM Executive Updates Guide
(2026 Edition)
6-section structure, 6 principles for great updates, before/after examples, and 5 rules for timing and cadence.
Build PM Writing Skills Daily — Free →6-Section Structure
1. Status tag (green/yellow/red)
Takes 2 seconds to read. Visual signal of health.
2. One-sentence headline
The most important thing this week. If they read only this, what matters most?
3. 3 bullets: wins
What shipped, what moved, what we learned. Specific, with numbers.
4. 1 bullet: risks
What's at risk. Surface early, not when it becomes crisis.
5. 1 bullet: asks
What you need from leadership this week. If nothing, say nothing.
6. 1 bullet: next week
The ONE outcome you're driving toward next week.
6 Principles
Lead with status, not narrative — executives skim
Numbers beat adjectives — 'retention at 22%' beats 'retention is improving'
Surface bad news early, specifically — 'we're at risk of missing X by 15%' beats 'things are challenging'
Send on a predictable cadence — trust comes from consistency
Keep under 300 words — longer signals you're hiding in words
Ask explicitly for help — don't expect executives to infer what you need
Before & After
❌ Before
“We've been working hard on the onboarding flow this week and have made significant progress, though there have been some challenges with engineering capacity that we're working through.”
✅ After
“🟡 ONBOARDING: Redesigned flow shipped to 10%. Activation up from 40% to 52% (target 55%). At risk: 1-week delay on full rollout due to tests failing on Android 8.”
💡 Why: Status tag, specific metric, clear risk, no fluff
❌ Before
“Great week overall! Lots of exciting progress across multiple initiatives. Looking forward to next week!”
✅ After
“🟢 Wins: Shipped checkout v2 (conversion +4pp). Completed user research with 8 Tier-3 users. Risks: Payment gateway partner has 2-day delay in KYC. Ask: Need legal review by Fri on refund policy.”
💡 Why: Concrete wins, specific risk, explicit ask
5 Rules for Timing & Cadence
Weekly on Friday — freshest memory, sets up weekend reflection for leaders
Send same time each week — consistency > perfect timing
Monthly longer updates complement weekly short ones
Don't send during weekends — respects boundaries + gets better attention Monday
Post in a persistent channel (shared doc or email) — not just Slack where it gets lost
FAQ
How often should PMs send exec updates?
Weekly cadence is standard — any less and you surprise leadership with bad news; any more and you create noise. If your team is running hot (launch week, crisis), bump to mid-week shorter updates. The cadence itself builds trust: predictability signals reliability.
What's the biggest mistake PMs make in exec updates?
Over-writing. Many PMs submit 800-word updates thinking more detail = more effort. Executives read maybe 50 of those words. Under 300 words, with the most important thing at the top, earns more trust than long, narrative updates. The discipline of brevity signals confidence and clarity.
Practice Concise PM Writing Daily
Daily scenarios that force the discipline of brevity and specificity.
Start Free Trial →