Prompt
Write a weekly update for my design work that a cross-functional team will actually read.
Context:
- Product/team: [describe]
- Audience: [PM/Eng/Leadership/Design]
- This week (what I did): [bullet list]
- Decisions made: [bullet list]
- Open questions / blockers: [bullet list]
- Metrics / signals (if any): [numbers, feedback, learnings]
- Next week priorities: [bullet list]
Output:
1) Slack version (8?12 lines, skimmable)
2) Notion/Email version (structured with headings)
3) ?Asks? section (what I need from PM/Eng/Leadership)
4) Risks + mitigations
Style constraints:
- Clear, concrete, non-hype
- Emphasize outcomes + decisions over activity
- If I didn?t ship a metric, say what signal we have (qual, research, stakeholder alignment)How to use
- 01
Fill in the context bullets with your real work from the past week (projects, decisions, blockers, outcomes).
- 02
If you have metrics: include them (conversion, activation, NPS, time-on-task, support ticket volume, etc.).
- 03
If you don?t have metrics: include qualitative signals (user quotes, research findings, stakeholder alignment, shipped learning).
- 04
Ask for two tones if needed: ?Direct? and ?More diplomatic.?
- 05
Paste the result into Slack/Notion and edit any sensitive details before posting.
Tips
- Lead with decisions and outcomes, most readers skim.
- Keep ?Asks? specific (who, what, by when).
- If something slipped, state the reason + next step (no excuses, just clarity).