You're in a meeting. Decisions get made. You send a summary email to the team.
Three people reply-all with questions. Two people respond with "thanks." One person asks why they weren't invited. Another person points out that the decision you thought was made wasn't actually agreed to.
Sound familiar?
The problem isn't the update. The problem is what you left out.
What the Update Misses
A meeting summary captures the surface. What it misses:
- The trade-offs that were discussed but not resolved
- The person who pushed back but was overruled
- The constraints that weren't fully articulated
- The questions that were asked but not answered
None of this fits in a summary email. And all of it matters for the people who need to act on the decision.
What to Do Instead
Send the decisions. Explain the context.
Don't just say "we decided X." Say "we decided X because Y. Here's what we considered and what we ruled out."
This takes more time to write. It also means people don't have to ask follow-up questions to understand what happened.
Identify who's responsible for what.
The decision isn't enough. Every decision has an owner. Make sure that owner is clear — and that they know they're accountable for the outcome.
Say what happens next.
For each decision, capture: what's being done, who's doing it, by when. If you don't know, say that too.
Why This Matters
When people receive a meeting update, they're trying to understand two things:
- What changed?
- What does that mean for me?
A summary that only answers question one will get constant follow-up. A summary that answers both will save you hours of reply-all threads.
The next time you send a meeting update, double-check: does this tell people what they need to know, or just what happened?
Top comments (0)