Meeting notes can be detailed without telling anyone what to do tomorrow. I care more about whether the record advances the work than whether it recreates the conversation.
Three sections may be enough
Decisions, actions and open questions. Decisions identify the chosen direction. Actions name who will do what and by when. Open questions identify the missing information or approval.
Images were discussed is not an action. A named person will share three image options by Thursday describes a next step, provided that responsibility was actually agreed. Precision should record ownership, not invent it.
Do not turn every opinion into a decision
An idea mentioned in a meeting is not automatically an approved direction. Presenting one person’s suggestion as a team decision creates avoidable disagreement. If no decision was reached, the note should say so.
I record important choices with concise reasons and link to a decision log where more detail is needed. Meeting notes do not need to replace every other project document.
Share while corrections are still useful
A summary arriving a week later may allow a misunderstanding to persist too long. Sharing close to the conversation and confirming unclear items is more useful. Silence should not automatically be treated as explicit agreement in every situation.
Sensitive or irrelevant personal remarks do not belong in the record. The purpose is to preserve information needed for the work, not every word someone spoke.
Start the next meeting with the previous actions
Before opening a fresh agenda, review outstanding tasks. If something remains incomplete, identify the obstacle rather than merely noting its status. A task that is no longer needed can also be closed deliberately.
Without this loop, every meeting can feel like another beginning. I use the note as a short bridge carrying responsibility between conversations, not as a lengthy substitute for memory.