• [What changed and why — 1 sentence each]

• [Anything trending in the wrong direction]

• ✅ [What went live] — [1-line impact or observation]

• 🔄 [Feature/initiative] — [% complete or current status]

• ⚠️ [What didn't happen] — Reason: [brief] — Action: [who's unblocking it]

• [Item + why it's carrying over]

• "[Quote or paraphrase]" — Source: [user/channel] — Theme: [tag]

• [Top ticket category this week + volume]
• [Anything that signals a product gap]

• [Any discovery from user interviews, analytics, or experiments]

• [Any decision that's blocking progress — who needs to make it]

• [What you need from engineering / design / data / leadership]

What's one thing from this week I'd do differently? [Your honest answer — 1–2 sentences]

What's the biggest unknown I'm carrying into next week? [Name the uncertainty explicitly]

• Product area or team you own
• Key metrics this week (with values and prior week comparison)
• What shipped, slipped, or is blocked
• Top 3 priorities for next week
• Any customer insights or signals (optional)

• Metrics include period-over-period comparison (not just raw numbers)
• Every blocked item has an owner and a specific unblocking action
• Next week's priorities have a "why this week" rationale
• Total length is under 400 words (skimmable in 3 minutes)
• Reflection section is honest, not aspirational

• Keep the whole document under 400 words — if stakeholders won't read it, it doesn't exist
• The reflection section is for you, not your stakeholders — keep it honest
• Always name a clear owner for every blocked item — "the team will figure it out" is a blocker in disguise
• Recommend sending this by end of Friday — Monday morning is too late to course-correct
• If three weeks of weekly reviews show the same blocked item, escalate immediately