Most meeting notes are either a wall of text that nobody reads back, or so sparse they are useless a week later. The problem is usually not effort. It is purpose. People write notes as if they are documenting everything that happened, rather than capturing what matters going forward. The result is a record that serves as an archive but not as a tool.
Good meeting notes are not a transcript. They are a bridge to the next meeting, capturing the decisions made, the actions agreed, and enough context to make both meaningful when you return to them.
What meeting notes are actually for
Notes serve two moments: the one just after the meeting, when you need to confirm what was agreed and who is doing what, and the one just before the next meeting, when you need to know where things stand. Everything else is optional.
This is why the common approach of typing furiously during a meeting to capture every word usually fails. By the time you open that doc again, you cannot find what you need, and half of what you wrote is context that made sense in the moment but is cryptic a fortnight later. The better approach is to write for future-you: what do I need to know when I open this next?
- DecisionsWhat was agreed? This is the most important thing to capture. Decisions that live only in memory get disputed, forgotten, or silently reversed.
- ActionsWho is doing what, by when. Without an owner and a deadline, a task is just an intention. Name names and set dates.
- ContextEnough background so the decision makes sense later. Not the full debate, just why you landed where you did.
- Open questionsThings that were raised but not resolved. These are easy to lose in a long set of notes but important to bring back to the table.
- SentimentA brief note on how the meeting felt, whether energised, uncertain, or tense, can be useful context when you return to it, especially for 1-1s where mood and momentum matter.
What to write down (and what to skip)
The fastest way to improve your notes is to stop trying to record everything and start filtering for what matters. During the meeting, you should be listening and engaging, not typing a running commentary. Notes should be written in bursts at natural pauses, or straight after the meeting while things are fresh.
You do not need to capture who said what, how the conversation unfolded, or the tangents that did not go anywhere. You do not need meeting notes to double as minutes unless governance requires it. Write for usefulness, not completeness.
- Write downDecisions and the reasoning behind them. Actions with clear owners and due dates. Open questions to return to. Key context that would not be obvious later.
- SkipWord-for-word dialogue. Points raised and immediately dropped. Tangential discussions that concluded nothing. Background context everyone already knows.
- Write promptlyNotes written 48 hours after a meeting rely heavily on memory. Write them the same day, or at minimum jot the key points immediately after and expand them shortly after.
- Keep them shortA page of dense prose is harder to use than five bullet points. Brevity forces clarity. If a note takes more than a minute to scan, it is probably too long.
Making notes work before the next meeting
Most notes fail not because they are poorly written, but because they are never consulted again. The discipline of reviewing your notes before the following meeting, even for five minutes, transforms them from a passive archive into an active tool. You walk in knowing what was agreed, what is outstanding, and what has changed since.
The storage question also matters. Notes buried in email threads or personal docs are effectively lost to everyone but you. Notes stored somewhere accessible and searchable, linked to the meeting, the team, or the project, are actually findable when you need them. Sharing a brief summary with attendees immediately after also confirms alignment and gives everyone a shared reference point.
Manager Toolkit's meeting notes feature is built for exactly this: capture notes from a meeting, attach actions with owners and due dates, and then surface that context automatically before the next meeting with the same group. Tag notes with Key Themes to connect related discussions across meetings-so when the same topic surfaces again, the history is already there. Actions from meeting notes flow into your central action list, keeping everything in one place rather than scattered across docs.
Meeting notes that stick
Capture decisions and actions in seconds, linked back to every meeting.