How to Take Notes in Meetings (Without Becoming a Stenographer)

Most meeting notes are unreadable a week later. The reason is not that the note-taker was lazy. The reason is that they were trying to do the wrong job. They were trying to transcribe.

Transcription is what a recording is for. If you want a transcript, hit record. The point of taking notes by hand, in a meeting where you are also expected to participate, is to produce a different artifact entirely: a short list of the things in the room that you will need to come back to. Not what was said. What was claimed.

The distinction matters. Most of what gets said in a meeting is connective tissue. "As I was mentioning earlier," "to your point," "the way we're thinking about it." None of this is worth writing down. It is the meeting clearing its throat. What is worth writing down is much narrower: the numbers, the definitions, the commitments, and the questions that didn't get a clean answer.

Write down four things

The discipline that works is to keep your notes to four columns, mentally if not literally:

Numbers. Anything stated as a quantity. Revenue, headcount, conversion rate, runway, burn, margin. Write the number, write who said it, write the timestamp. Don't editorialize. You are creating a record you can compare against later.

Definitions. When someone uses a term that has more than one common meaning — ARR, retention, active user, qualified pipeline — write down what they meant by it. The same word means different things in different rooms, and the gap between two definitions is where most meeting confusion lives.

Commitments. "I'll send that over by Friday." "We'll have a draft by end of next week." Names, dates, deliverables. This is the only part of the standard meeting-notes template that is actually load-bearing.

Dodges. This is the column nobody trains for, and it's the one that pays. When a question gets asked and the answer is not the question, write down the original question. Not the answer. The question.

What to leave out

Almost everything else. Don't write down conclusions. Don't write down your impressions of how someone seemed. Don't write down the agenda — you have the agenda. Don't write down the meeting's summary at the end, because the summary is almost always wrong about what actually mattered.

The bias to fight is the bias toward completeness. Notes that try to be complete end up being a worse, slower version of the recording. Notes that are deliberately incomplete — that capture only the four things above — end up being the most useful artifact from any meeting.

The review pass

The notes are not the deliverable. The deliverable is what you do with them, an hour later, when the room is no longer in your head.

Read down the numbers column. Anything look round in a way that's suspicious? Anything contradict a number from a previous meeting? Read down the definitions column. Did anyone use a term in a way that, on reflection, doesn't match how the rest of the team uses it? Read down the commitments column. Are the names and dates specific enough that you'll be able to follow up? Read down the dodges column. For each one, decide whether it matters enough to re-ask.

The output of this fifteen-minute pass is a much shorter document than your raw notes. It is the document worth keeping. The raw notes can be thrown away. They were scaffolding.

Why most note-taking advice is wrong

The advice industry treats note-taking as a memory aid. It is not. Your memory of a meeting, twenty-four hours later, is more than adequate for almost everything that was discussed. What your memory cannot do is hold a number stated in slide four against a number stated in slide eleven, twelve minutes apart. That is a comparison job. That is what notes are for.

Once you accept that, the four-column discipline becomes obvious. You are not trying to remember the meeting. You are trying to make the comparisons the room couldn't make in real time.

Most operators learn this the hard way, after a few quarters of decisions that turned out to be based on numbers nobody had bothered to check. The good ones learn to take notes that are almost embarrassingly sparse, and almost always more useful than anyone else's.