| name | status-updates |
| description | Writing effective status updates for different audiences and cadences. Use when: writing a weekly status update, preparing a monthly summary, drafting a quarterly review, sending updates to leadership, sharing progress with stakeholders, or improving the clarity and impact of team communications. Covers weekly, monthly, and quarterly formats tailored for upward, lateral, and downward communication. |
| tags | ["manager","communication","executive"] |
Status Updates
When to Use
- Writing a weekly status update for your manager or skip-level
- Preparing a monthly team summary for stakeholders
- Drafting a quarterly review for leadership
- Sharing progress with peer teams
- Communicating project health to non-technical stakeholders
- Creating a standard update format for your team
Core Principles
- Lead with outcomes, not activities — "Reduced onboarding time by 40%" beats "Worked on onboarding improvements"
- Audience-appropriate detail — Executives want headlines and risks. Peers want context. Your team wants specifics.
- Signal risks early — An update that hides problems is worse than no update at all
- Consistent cadence — Same day, same format, every cycle. Predictability builds trust.
- Concise — If your status update takes more than 5 minutes to read, it's too long
Weekly Status Update
Audience: Your manager, skip-level, peer leads
Cadence: Every Friday (or Monday morning)
Length: 10–15 lines max
Template
## Weekly Update — [Team Name] — Week of [Date]
### Highlights
- [Outcome or milestone achieved]
- [Outcome or milestone achieved]
### In Progress
- [Initiative] — [brief status, % complete or sprint target]
- [Initiative] — [brief status]
### Risks / Blockers
- [Risk] — [impact and mitigation plan]
- [Blocker] — [who/what is needed to unblock]
### Asks
- [Specific request with context — decision needed, resource needed, escalation]
### Next Week
- [What the team will focus on]
Guidelines
- Highlights: Max 3 items. These should be things your manager can pass upward.
- Risks: Never zero. If you can't think of any, you're not looking hard enough. "No risks" signals a lack of awareness, not a perfect sprint.
- Asks: Be specific. "Need a decision on X by Wednesday" is actionable. "Need help" is not.
Monthly Summary
Audience: Director/VP level, cross-functional stakeholders
Cadence: End of each month
Length: 1 page
Template
## Monthly Summary — [Team Name] — [Month YYYY]
### Key Outcomes
1. [Measurable outcome with business impact]
2. [Measurable outcome with business impact]
3. [Measurable outcome with business impact]
### OKR Progress
| Objective | KR | Current | Target | Status |
|-----------|-----|---------|--------|--------|
| ... | ... | ... | ... | 🟢 On Track / 🟡 At Risk / 🔴 Off Track |
### Metrics
| Metric | Last Month | This Month | Trend |
|--------|-----------|------------|-------|
| Sprint velocity | ... | ... | ↑/↓/→ |
| Escaped defects | ... | ... | |
| PR cycle time | ... | ... | |
### Risks and Mitigations
| Risk | Status | Mitigation |
|------|--------|-----------|
| ... | New / Active / Resolved | ... |
### Team Health
Brief note on team morale, capacity changes, hiring status.
### Next Month Focus
Top 2–3 priorities for the upcoming month.
Quarterly Review
Audience: VP/C-level, org leadership
Cadence: End of each quarter
Length: 2–3 pages or a short deck (5–8 slides)
Template
## Q[N] Review — [Team Name]
### TL;DR
3-sentence executive summary: what we achieved, what we missed, what's next.
### Scorecard
| Objective | Score | Highlights |
|-----------|-------|-----------|
| ... | 0.X | ... |
Overall: X.XX / 1.0
### Key Wins
- [Win with quantified impact]
- [Win with quantified impact]
### Key Misses
- [Miss with root cause and lesson learned]
### Delivery Metrics
| Metric | Q[N-1] | Q[N] | Trend |
|--------|--------|------|-------|
| Features shipped | ... | ... | |
| Incidents (P1/P2) | ... | ... | |
| Velocity (avg) | ... | ... | |
### Risks and Outlook
Active risks heading into next quarter.
### Next Quarter Preview
Top 3 themes or initiatives for Q[N+1].
Communicating to Different Audiences
Upward (Your Manager, VP, Exec)
- Lead with impact: Business outcomes, metrics, customer impact
- Be concise: 5 bullets, not 5 paragraphs
- Surface risks: They want to know what might break, not just what's going well
- Make asks explicit: Don't hint — state what you need clearly
- Use their language: Revenue, retention, velocity-to-market — not story points or tech jargon
Lateral (Peer leads, PMs, adjacent teams)
- Focus on dependencies: What you need from them, what they need from you
- Share context: They don't have your team's full picture
- Flag shared risks: Especially cross-team blockers
- Be transparent about capacity: If you can't take on their request, say so clearly
Downward (Your Team)
- Be transparent: Share company context, org decisions, reasons behind priorities
- Celebrate wins: Public recognition in team channels
- Be honest about challenges: Don't sugarcoat — the team knows when things are hard
- Show how their work connects: "This feature directly supports the company OKR on retention"
Delivery Channel
| Update Type | Channel | Format |
|---|
| Weekly | Team chat (channel + manager DM) or email | Text with clear sections |
| Monthly | Email + shared wiki page | Longer-form with tables |
| Quarterly | Wiki doc + presentation | Document + slides for review meeting |
| Ad hoc (incident, launch) | Chat + email | Brief, factual, with next steps |
Anti-Patterns
| Anti-Pattern | Problem | Better Approach |
|---|
| Activity log | "Worked on X" tells nothing about progress | State outcomes: "Shipped X, reducing Y by Z%" |
| No risks section | Signals unawareness or avoidance | Always include at least one risk or watch item |
| Buried asks | Buries what you need in a wall of text | Surface asks in their own section at the top |
| One-size-fits-all | Same update sent to execs and the team | Tailor format and depth by audience |
| Inconsistent cadence | Updates come randomly, not on schedule | Pick a day, stick to it every week |
