Meeting Notes That Actually Get Used

Most meeting notes are never read again. They're written out of obligation, filed somewhere vague, and forgotten.

The problem isn't note-taking skill. It's note-taking purpose. Notes that capture everything capture nothing useful. Notes that capture decisions and actions get referenced.

What Meeting Notes Are For

Meeting notes serve future readers who weren't in the room (or were but forgot). They need to answer:

• What was decided?
• What actions were assigned and to whom?
• What context explains those decisions?
• What's still unresolved?

Everything else is optional. Extensive discussion transcription is usually worthless.

The Structure That Works

Every meeting note should have these sections:

# [Meeting Name] - [Date]

**Attendees:** [who was there]
**Purpose:** [why we met - one sentence]

## Decisions
- [Decision 1]
- [Decision 2]

## Action Items
- [ ] [Person]: [Task] by [Date]
- [ ] [Person]: [Task] by [Date]

## Discussion Summary
[Brief context for decisions - not a transcript]

## Open Questions
- [Unresolved issue 1]
- [Unresolved issue 2]

## Next Steps
[When/if we're meeting again, what happens next]

Decisions and action items at the top. Readers can stop there if that's all they need.

Capturing Decisions

A decision is not the same as a discussion point. Many meetings discuss topics without actually deciding anything.

When something is decided:

• State it clearly and specifically
• Note who had authority to decide (if relevant)
• Include brief rationale if non-obvious

Bad: "Discussed the launch timeline" Good: "Decision: Launch date moved to March 15 to accommodate QA testing"

If a topic was discussed without resolution, it goes in Open Questions, not Decisions.

Action Items That Get Done

Every action item needs:

• Who is responsible (one person, not "the team")
• What specifically they'll do
• When it's due

Bad: "Follow up on the vendor issue" Good: "Sarah: Get updated pricing from Acme Corp by Friday"

During the meeting, confirm action items verbally. "So Sarah, you'll get pricing by Friday?" This catches misunderstandings immediately.

Real-Time vs. Post-Meeting Notes

Real-time notes capture during the meeting. Benefits: nothing forgotten. Risks: too much detail, split attention.

Post-meeting notes written immediately after. Benefits: synthesized, focused. Risks: memory gaps, delay means forgetting.

Hybrid approach works best:

• During: Jot keywords, decisions, and action items only
• Immediately after: Expand into full notes while memory is fresh
• Same day: Share with attendees for corrections

Never delay notes until "later." Later becomes never.

When Someone Else Takes Notes

If you're not the note-taker, you can still contribute:

• Call out decisions explicitly: "So we're deciding X, correct?"
• Confirm action items: "To clarify, I'm doing Y by Z date?"
• Offer corrections during review

Taking turns as note-taker ensures everyone understands what good notes look like.

Notes for Recurring Meetings

Weekly standups, project check-ins, and regular 1:1s benefit from linked notes:

• Keep a running document or folder for the meeting series
• Start each entry with the same template
• Reference previous action items: what's done, what's carried over
• Track themes over time

For recurring meetings, consistency matters more than comprehensiveness.

What to Leave Out

Skip:

• Who said what (unless attribution matters for decisions)
• Tangential discussions that led nowhere
• Social chat and warmups
• Detailed arguments if the conclusion is what matters

Include:

• Minority opinions if they might become relevant later
• Context for controversial decisions
• Links to referenced documents
• Blockers or dependencies mentioned

Ask: "Would a reader six months from now need this?" If no, cut it.

Distributing Notes

Notes unread are notes wasted.

• Share within 24 hours (sooner is better)
• Use a consistent location (same Slack channel, same folder)
• Highlight action items for those assigned
• Give attendees a window to correct errors

If your organization has a notes graveyard (a folder where notes go to die), don't use it. Share in the channels people actually check.

Making Notes Findable

Future you will search for "that meeting where we decided X."

Help yourself:

• Clear, descriptive titles with dates
• Consistent tagging by project or topic
• Keywords in the body that you'd search for
• Links to related documents and previous meetings

Five seconds of metadata now saves five minutes of searching later.

The Note-Taker's Paradox

Taking notes during a meeting reduces your participation. You're transcribing, not contributing.

Solutions:

• Rotate note-taking duty
• Use a dedicated note-taker for important meetings
• Record meetings and take notes afterward
• Focus on decisions/actions during the meeting, write context after

Balance capture with contribution based on your role in each specific meeting.

Minimum Viable Meeting Notes

If nothing else, capture:

1. One decision that was made
2. One action item with owner and deadline
3. One open question that remains

That's three lines. Three lines is infinitely better than zero documentation.

Every meeting generates at least three lines of useful output—or the meeting shouldn't have happened.