Start with the job the notes must do
Good meeting notes are not a compressed transcript. They are a retrieval tool for the future reader: what changed, why it changed, what remains unresolved, and what happens next.
Before the meeting, decide what you will need later. For a design review that may be trade-offs and architectural decisions. For a client call it may be requirements, objections, dates, and commitments.
Capture five things, not everything
- Decisions: the choice that was actually made.
- Rationale: the important reason, constraint, or trade-off behind the choice.
- Open questions: anything still unresolved or blocking progress.
- Commitments: who agreed to do what, and any date that was explicitly agreed.
- Evidence: the transcript moment, screenshot, diagram, number, or quote you may need to verify later.
Do not duplicate what the transcript already preserves
If the meeting is transcribed, there is little value in manually reproducing chronology. Use your attention for interpretation: mark the moment where the conversation changed direction, a disagreement was resolved, or a decision became firm.
Keep the transcript as the evidence layer and the notes or summary as the retrieval layer.
Write action items as deliverables
“Follow up on design” is weak. “Design lead shares updated onboarding wireframes with the team by Thursday” is useful. A good action contains a deliverable, an owner, and only the deadline that was actually agreed.
Review for ambiguity before you close the meeting
- Can you tell which statements are decisions versus proposals?
- Does every action have an owner?
- Are unresolved questions clearly visible?
- Are important numbers or contractual statements linked back to evidence?
- Would somebody who missed the meeting understand what changed?