How to Take Meeting Notes People Actually Read

Your notes have one reader: the person who wasn't there

Start by being honest about who meeting notes are for. The average knowledge worker spends around 11 hours a week in meetings — roughly 392 hours a year, nearly ten full workweeks, per Flowtrace's analysis of millions of meetings. Microsoft's Work Trend Index puts the number of meetings at roughly triple what it was in February 2020, and finds 57% of the average employee's work time now goes to communicating instead of creating.

That's a staggering volume of discussion whose only surviving record is a document somebody typed up — and attendees themselves rate 35–45% of meetings as unproductive. Your notes compete with that skepticism every time someone decides whether to open them. So write for the reader who wasn't in the room: a person with two minutes and one question — what happened, and what happens next?

Stop transcribing. Start deciding what survives.

The single most common note-taking failure is trying to write down everything. The moment you fall behind, you're recording too much. Ask one filtering question as you write: would someone need this sentence to understand what was decided? If not, it doesn't go in.

Decision and discussion must live in separate places. Meetings are full of tradeoffs and exploration before arriving at a conclusion, and when the decision stays buried in a long paragraph, nobody can find what changed. Write each decision as a clear standalone statement, with the reason attached if you have it. "Launch moved from March to May because the auth rewrite needs two more sprints" survives. A paragraph about the fifteen minutes of debate that produced it does not.

There's one hard rule for the decisions section: only record what was actually agreed. A decision is something the group settled, not something one person suggested. If you're not sure it was agreed, say so — literally ask, "for the notes, the decision is X — is that correct?" Five seconds of awkwardness beats a week of people acting on different understandings. Anything uncertain goes under open questions instead of being laundered into a decision.

The four-part recap that fits every meeting

You don't need an elaborate template. A usable meeting recap has four parts, and it takes a few minutes to write:

TL;DR. Two or three sentences: what the meeting was about and what changed. If nothing changed, say that. This is the part most people will read, so write it last and keep it plain.
Decisions. One line each, with the reason if you captured it. Settled only — no ideas that merely got discussed.
Action items. A simple table or list: task, owner, due date. One clear next step per row. "Ravi to update the API docs by Thursday" is an action item; "we should update the docs" is a wish.
Open questions. What was raised but not resolved — and who has to answer it. Mark anything you don't know as TBD instead of guessing.

Two details make this work. First, every action item needs a named owner and a deadline, confirmed in the room before the conversation moves on. "Owners are implied" is how follow-ups die; when three people agree "we should do X," zero of them believe they're the one. Second, send the recap the same day, within 24 hours at the latest. One page for a 30-minute meeting, two for an hour. If you're past three pages, you're transcribing.

Do half the work before the meeting starts

Good notes begin before anyone talks. Pull up the agenda and pre-populate your document with it as section headers — you spend less time deciding where to write and more time listening, and you can't accidentally skip an agenda item. If there's no agenda, that's your first data point about the meeting.

Also decide who takes the notes, ideally ahead of time, and rotate the role. It shouldn't be the person running the meeting — facilitating and capturing at the same time is how both get done badly — and it shouldn't always be the same team member, because note-taking shouldn't be one person's permanent job.

There's also a quieter reason to take notes during the meeting itself. Harvard Business Review's management research describes "margin notes": in the main body, write down only what the other person is saying, and park your own reactions in the margin. Forcing yourself to separate their points from your judgments keeps you listening instead of rehearsing your rebuttal — which is what most people are doing when the camera is on and the pen is down.

Pen, keyboard, or AI — pick the tool for the job, not the habit

The honest version: handwritten notes make you remember more; typed notes make your team remember more. A 2014 Psychological Science study by Mueller and Oppenheimer found that students writing longhand had to process and summarize instead of transcribing, and understood the material better than laptop typists who wrote down more. So for 1-on-1s and strategy sessions, where your own retention matters most, handwriting wins. For team meetings, where the notes are a shared artifact, type.

AI meeting assistants have changed the division of labor, not the goal. Let the tool capture the transcript; your job shifts from transcribing to synthesizing. The right setup is two artifacts: the AI transcript as your archive, and a short human extract as your record. The machine captures what was said and you capture what it meant — including the decision that was really about headcount and the question nobody wanted to put in writing.

One caution: don't ship the raw AI summary as your meeting notes. AI summaries capture what was said, not what was agreed — which is exactly the distinction the decisions section exists to make. (And to be fair: board meetings and regulatory sessions legally require full minutes. This system is for the other 95% of meetings, where the point is action, not the archive.)

If you can't fill the recap, you don't have a notes problem

Here's the diagnostic power of the four-part format: when you sit down to write the recap and find there were no decisions and the only action item is "same time next week," your notes have just told you something about the meeting. A recurring meeting with a consistently empty decisions section is a candidate for deletion, not better notes. The notes didn't fail. They did their job, which is to produce the evidence.

What to actually do this week

Pick one recurring meeting and try this. Before it starts, pre-fill the agenda as headers and volunteer to take the notes. During it, capture only decisions (with the one-line reason), action items (task, owner, due date — confirmed out loud), and open questions (with who must answer). After it, spend ten minutes cleaning up and send the recap the same day: a two-sentence TL;DR on top, the three sections below.

Then watch what happens to the "what did we decide?" questions. Most meetings don't need better attention. They need one person writing down the answer.