How to Write Meeting Notes That People Actually Read
Meeting notes get read when decisions and action items come first, each action has an owner and deadline, items nobody claimed are flagged as unassigned, the whole thing reads in about three minutes, and casual meetings get a short message instead of formal notes.
- Lead with decisions and action items.
- Give every action an owner and a date.
- Flag unassigned items separately.
- Keep it to about a three-minute read.
- Skip formal notes when a short message will do.
Meeting notes that people read put the outcomes first: a short list of decisions, then action items with owners and deadlines, then any unassigned items, with discussion summarized briefly afterward. Keeping notes short matters; adults read English non-fiction at about 238 words per minute on average, according to a 2019 meta-analysis by Marc Brysbaert, so a three-minute read is roughly 700 words. Chronological write-ups make readers do the extraction themselves.
You spent twenty minutes writing up the meeting. Fifteen people got it; three opened it. Next week someone asks a question answered on page two. The problem is usually structure, not effort.
Who are meeting notes for?
Meeting notes have at least two audiences with different needs: the people who were in the meeting (who need a record of what got decided) and the people who weren't (who need to know what affects them). These two audiences read notes differently. The in-meeting reader scans for confirmation that their understanding matches the record. The absent reader scans for action items, decisions that affect their work, and anything they'll need to respond to. Notes that try to serve both audiences with the same chronological narrative serve neither well. The fix is to lead with what both audiences want — decisions and action items — and let the discussion summary follow as supporting detail. The opening of any meeting note should be readable on a phone screen and contain everything an absent reader needs.
"DECISIONS • Move launch to Oct 15 (Sarah) • Cut feature B from MVP (Tom) ACTION ITEMS • Sarah → revised timeline doc by Friday • UNASSIGNED → investigate vendor pricing — needs an owner DISCUSSION SUMMARY [everything else]"
This structure does most of the work of making meeting notes readable. Decisions and action items at the top, scannable in fifteen seconds. UNASSIGNED items pulled out so they can't be missed. The discussion summary follows as supporting context. Readers who only need to know what got decided can stop after the first two sections. Readers who need depth can keep reading. Both audiences are served by the same document, which is what notes are supposed to do.
What should go first in meeting notes?
The standard chronological structure ('first we discussed X, then we moved on to Y') is a common reason meeting notes get skimmed and abandoned. Replace it with two sections at the top: 'Decisions' and 'Action Items.' Decisions are short, declarative, and dated ('Decided to move launch to Oct 15. Owner: Sarah.'). Action items have an owner, a deadline, and a one-sentence description of what done looks like. Both sections are scannable in under thirty seconds. Everything else — the discussion summary, the deferred questions, the context for each decision — comes after, as material the reader can dive into if needed but doesn't have to. This is the structural move that does most of the work of making notes readable. Even imperfect notes with this structure are often more useful than polished notes with a chronological one.
How do you handle action items nobody claimed?
Meetings often produce action items that nobody explicitly took ownership of. Someone said 'we should look into that,' the room nodded, and the action item entered an ambiguous state where everyone assumed someone else would handle it. These are the action items that disappear by the next meeting. Surfacing them in writing is one of the most valuable things meeting notes can do. The technique is to call them out explicitly: 'UNASSIGNED — investigate vendor pricing options. Needs an owner.' The flag forces the next conversation: someone either claims the action item or it gets dropped on purpose, both of which are improvements over the silent fade. Don't bury unassigned items in the action-items list; pull them into their own visually distinct subsection so the omission can't be missed. The notes are doing project management work that the meeting itself often skipped, and that's where much of their value lives.
How long should meeting notes be?
Short enough to read in about three minutes. Long notes tend to get scanned rather than read, in the order the document is structured, which is why structure matters more than completeness. At the average adult silent reading speed of roughly 240 words per minute for non-fiction, three minutes is about 700 words. Treat the discussion summary as compression, not transcription: one sentence per topic where possible, three at most. If a topic needs more, link to a separate document. The notes are an interface, not an archive, and they have to work in the first scan of someone's inbox.
Do all meetings need written notes?
Some meetings don't actually need formal notes. Quick stand-ups, brainstorm sessions where the output is the brainstorm document itself, 1:1s where the action items live in private channels — for these, formal meeting notes can be more friction than they save. The signal you've reached this category: are you writing notes mostly because notes are what one writes after meetings, rather than because someone will use these specifically? If yes, the right artifact may be a three-line Slack message ('In our standup today: A is unblocked, B is at risk on the data dependency, C will own the customer follow-up'), or a single calendar entry update, or just an in-person hallway recap. The discipline is to choose the artifact that serves the actual outcome, not the one the situation conventionally calls for. Three-line Slack messages get read; formal notes for casual meetings often don't.
Get the structure done for you in seconds
The Debrief takes a meeting transcript — Zoom captions, Teams, Otter.ai, Google Meet, or typed notes — and produces the structured output: decisions (with who drove each), action items with owners and deadlines, UNASSIGNED items flagged, tensions detected, open questions, and a meeting health score. The notes you'd spend twenty minutes writing arrive in seconds.
Found this useful? Link to it.
https://deftbrain.com/guides/meetings/how-to-write-meeting-notes-that-people-actually-read
Free to read, no account, no paywall — link away.