Meetings & notes21 categories
Summarise a week of standups
Turning daily noise into something a stakeholder can read on Friday.
Summarise the standup notes below into a short picture of the week. 1. **Shipped**: what actually completed, not what was worked on. 2. **In progress**, with an honest read of whether each is moving. If something has appeared every day with no visible change, say so. 3. **Blocked**: what, who is blocked, on whom, and for how long. 4. **Emerging risk**: anything mentioned in passing more than once. These are usually mentioned three times before they become a problem. 5. **Changes to the plan** made during the week. Keep it under 200 words. Do not list every person's every task. Do not soften a slipping item into "progressing well". Standup notes:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Updates and follow-ups. The message after the meeting: status for a manager, a team update, and chasing what stalled.
Related prompts
Chase actions nobody clearly ownsA week after a meeting, when half the actions have quietly not happened.Compress an update into a chat messageWhen the status belongs in Slack, not in a document nobody opens.Write a weekly update for my managerFriday afternoon, summarising a week you can barely remember.Turn this into a team updateNotes that need to become a message people will actually read.One-line statusA stakeholder asks how it is going and wants the honest one-liner.Write the follow-up messageThe message you send an hour after the meeting to make it stick.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free