What to capture, and what to ignore
The instinct is to write down what people say. That produces a long document that nobody opens again, and it means the note-taker is transcribing rather than listening for the thing that actually matters.
Four things are worth capturing. Everything else is not.
Decisions. What was agreed. Stated as a conclusion, not as a discussion summary.
Rejected options, with the reason. This is the most undervalued line in any set of notes. Six weeks later somebody proposes the thing you already considered, and the one-line reason saves the whole conversation happening again.
Actions. Person, verb, date.
What was deliberately left open. Distinguishing "we decided not to decide yet" from "we never got to it" prevents an open question from silently becoming a forgotten one.
The filter
If a line in your notes does not record a decision, a rejection, an action, or an open question, it probably does not need to be there.
A format that takes two minutes to write
Meeting: Q3 pricing
Date: 24 August
Decided
- Moving to three tiers, not four
- Launch date is 1 October
Rejected
- Usage-based pricing. Too hard to forecast for customers at this size
Actions
- Danish drafts the tier descriptions by Wed 27 Aug
- Priya checks migration impact for existing accounts by Fri 29 Aug
Open
- Whether existing customers are grandfathered. Decide next week with finance
That is the whole thing. It takes two minutes, it can be read in twenty seconds, and every line is doing work. A page of prose covering the same meeting would take fifteen minutes to write and would not be read at all.
The readback, which does most of the work
Two minutes before the end, read the decisions and actions aloud.
This one habit is worth more than everything else in this article, because it is where you discover that two people left the room with different understandings. That discovery is free now and expensive in a fortnight, when a deadline is missed and neither person thought it was theirs.
It also forces vagueness to the surface. Reading out "someone will look into the pricing question" and hearing the silence that follows is what turns it into "Priya checks it by Friday". Actions that survive contact with a readback are actions with an owner.
Where transcripts and AI notes fit
Automatic transcription and AI summaries handle the part that was always tedious, and they handle it well. What they do not do is judgement.
An AI summary will accurately report that the team discussed three pricing models and leaned towards tiered. It will not reliably distinguish between the room genuinely committing to that and one senior person saying it while two others privately disagreed. It also cannot tell that the important thing in a forty minute meeting was one sentence near the end.
The practical division: let the tooling capture the record, and keep a human responsible for confirming the decisions and the owners. In practice this means reading the generated summary within the hour, correcting the decisions, and sending it on. That takes about three minutes and produces something considerably more reliable than either the raw summary or hand-written notes alone.
If you record, tell people you are recording and check the consent rules where your attendees are, since these differ by country.
Making the actions survive the week
Notes that stay in a document are notes that get read once.
Move actions into wherever work actually lives
The same day. Whatever your team uses for tasks, the actions belong there, not in a meeting note that nobody opens on Tuesday.
An action item in a document is a record that something was agreed. An action item in the task system is something that will actually be looked at.
Same dayStart the next meeting with the last one's actions
Sixty seconds, at the top. Done, not done, or no longer relevant.
This is the entire accountability mechanism. Without it, actions are aspirational, and people quickly work out that nothing follows from committing to one.
60 seconds at the topKill actions that keep rolling over
If something has appeared unfinished three times, it is not a task, it is a decision nobody wants to make. Either give it real time or drop it explicitly.
Perpetually rolling actions make the whole list feel optional, which undermines the ones that matter.
Three strikes
The test for whether any of this is working is simple. Pick a meeting from three weeks ago and ask what came out of it. If nobody can answer without opening a document, the notes were a record rather than a mechanism, and the fix is the readback and the sixty seconds at the top of the next meeting.
Frequently asked questions
- Who should take notes in a meeting?
- Not the person facilitating, if you can avoid it. Facilitating and note-taking compete for attention, and the notes usually lose. Rotate the note-taker so it does not always fall to the same person, which in many teams means the most junior or the only woman in the room.
- Should I write down everything that was said?
- No. A transcript of discussion is close to useless later, because nobody re-reads it. Capture what was decided, what was rejected and why, who owns what, and what was deliberately left open. Everything else is recoverable from the people who were there.
- What makes a good action item?
- A named person, a specific verb, and a date. "Sam sends the revised quote to Acme by Thursday" is actionable. "Follow up with Acme" is a reminder that something exists, which is not the same thing.
- Do AI meeting notes replace taking notes?
- They replace the transcription, not the judgement. An automatic summary captures what was discussed accurately but cannot reliably tell which of five options the room actually committed to. Someone still has to confirm the decisions.
- When should notes be sent?
- The same day, ideally within an hour. The value is that anyone who understood something differently can correct it while the meeting is fresh. Notes sent three days later are a record, not a mechanism.
