Why good minutes matter
The meeting is the cheap part. The expensive part is everything that happens — or doesn’t — after it. Minutes are the handoff from a live discussion to the work that follows it.
Good minutes are short. They say what was decided, who owns what, and when the next checkpoint is — so anyone who missed the meeting can act without asking a follow-up question.
What good minutes contain
- Decisions — what was agreed, in one line each.
- Action items — owner, deadline, and deliverable.
- Next steps — what happens before the next meeting.
- Context — a short note on why — so future you remembers.
How audien·to structures yours
What lands in the doc
- Decisionsone line per agreement. Stated outcome, not the discussion that led there.
- Action itemsowner · deliverable · deadline — never “the team,” always a name.
- Next stepswhat unblocks the next meeting. Distinct from action items: these are checkpoints, not work.
- Open questionsitems that didn’t close — these become the next meeting’s agenda.
- Context note1–2 sentences on why a decision was made, so a reader six months later doesn’t reopen it.
Writing minutes well
- Lead with the decisionthe first line a reader sees should be what was agreed. Discussion goes in context, not above it.
- One owner per actionif it’s shared, split it. “Ada and Chen will…” means neither will.
- Date every commitmenteven if it’s “this week” — vague dates become missed deadlines.
- Capture the unansweredthe question that stalled the meeting is more valuable than the ones that resolved.
- Skip the play-by-playminutes are not transcripts. If a reader needs full context, they can open the recording.
Knobs in the Options panel
- Depth5-line tl;dr (status updates) · standard minutes · full report (board / external).
- Toneneutral · direct (default for engineering syncs) · formal (board / legal).
- Filler trimremove ums, restarts, off-topic detours — on by default.
- Speaker citationsby name · by role (PM / EM / Designer) · timestamped — pick what helps the reader, not the writer.
- Action-item detectionstrict (only “I will” / “Can you…”) · loose (also catches implied commitments).
- Risks & blockersfold into context (default) · break out into their own list (good for status decks).