Fill in these first
- Product or team: [e.g. the payments team of a lending app]
- Readers: [e.g. founders, sales leads, support head]
- Rough notes, tickets closed and releases: [paste]
- Metrics with last week and this week: [paste, e.g. checkout success 91% to 93%]
- Blockers and who can unblock them: [paste]
- Decisions needed and by when: [paste, or none]
Task
Write an update a busy reader can skim and act on, without any engineering jargon.
Output format
- Subject line under 60 characters with the week's date range.
- Summary: three lines, the most important change first.
- Shipped: each item as what changed for customers, in one line, with who should know about it, such as support or sales.
- Learned: one to three findings from data, research or support, each with its source.
- Metrics: | Metric | Last week | This week | Note |
- Blocked: each blocker with the owner who can clear it.
- Decisions needed: the question, the options and the date.
- Next week: up to five items.
Rules
- Under 350 words in total.
- No ticket numbers or internal code names; describe the change.
- Bad news is stated plainly in the summary, not hidden at the bottom.
- Figures come only from the inputs.






