You spent twenty minutes writing a meeting recap. You hit send. You feel productive.
Then the responses come. Three people ask questions that were answered in the recap. Two people reply with "thanks." One person says they didn't see the recap and asks for a verbal summary in the next meeting.
The meeting recap nobody read. A universal experience.
Why Recaps Fail
They're too long.
The recap covers everything that was said, not what was decided. It's a transcript, not a summary. Nobody has time for a transcript.
They're not actionable.
If the recap doesn't tell people what to do next, it's not doing its job. A recap that says "discussed Q3 planning" without naming the decision or the owner is useless.
They're not delivered in context.
The recap lands in an inbox with fifty other messages. Without a clear subject or a nudge, it disappears.
What a Recap Actually Needs
Three things:
Decision: "We decided to move forward with Option A. Option B was rejected because [reason]."
Owner: "[Name] is responsible for executing the migration by [date]."
Next step: "We'll revisit this in the June 15 sync to check progress."
That's it. If your recap doesn't have those three elements, it doesn't matter if people read it.
How to Get People to Actually Read It
Send it immediately after the meeting. Not an hour later. While the decisions are fresh.
Subject line that says the decision: "Decision: Q3 roadmap will use Option A" — not "Meeting Notes 04/24."
Follow up in the next meeting: "Did everyone see the recap? Any questions?"
If the recap needs a follow-up to be understood, fix the recap.
Top comments (0)