Most meeting notes are written for an audience of zero. They're a transcript nobody asked for, filed somewhere nobody looks, capturing a discussion everyone present already heard. Good meeting notes are a different genre entirely: they're written for the people who weren't there and for everyone's memory three weeks later — and they're short.
Capture decisions and actions, not conversation
The discussion is the process; the notes are the output. Ruthlessly, notes need only three sections:
- Decisions — what was settled, and the one-line reason. "Going with vendor B (better SLA, price within 5%)."
- Actions — who does what by when. Every action has exactly one owner. "Sam: draft contract by Fri 6/27."
- Open questions — what wasn't resolved, and how it will be. "Pricing tier — needs finance input, on agenda next week."
If a point produced no decision, action, or open question, it usually doesn't need to be in the notes.
Write them during, publish within the hour
Notes written from memory the next day are fiction. Take rough notes live — bullet fragments are fine — and spend five minutes right after the meeting turning them into the three sections above. Speed matters more than polish: notes published within the hour get read while the meeting is still mentally warm; notes published Thursday get archived unread. A quick cleanup pass with a rewriting tool like Wrivio can turn live-typed fragments into readable sentences in a minute without changing what was said — useful when the notes go to executives or clients and "rough" isn't an option.
Actions belong in the task system, not just the notes
The most common failure: actions are faithfully recorded in the notes and then never looked at again. Notes are a record; they are not a tracking system. Every action item should be copied into whatever board or checklist the team actually works from — a shared tool like MyTeamTask is a natural landing spot — with the note serving as the context link. The test of good meeting hygiene isn't whether actions were written down; it's whether anyone would notice if one silently disappeared.
Structure recurring meetings identically
For standing meetings, use the same notes template every time, in the same document or thread, newest entry on top. Predictable structure means a reader can find "what did we decide about X" in seconds, and it exposes drift — the open question that has appeared in four consecutive weeks' notes is trying to tell you something.
The distribution line matters
End the notes with explicit routing: "Action needed: Sam, Priya (see actions). FYI only: everyone else." Readers triage instantly, and owners can't claim they didn't know. For meetings with external parties, send the notes to them too — "here's what we understood and agreed" — because an unshared understanding isn't an agreement, it's an assumption with a delay on it.
Keep a decision log for the big ones
Some decisions outlive the meeting notes that recorded them. Anything with long-term consequences — architecture choices, pricing changes, policy — deserves a second home in a standing decision log: date, decision, reason, who was in the room. It's ten seconds of copying that saves the organization from its favorite pastime: re-arguing settled questions with worse attendance.
