Workplace communication
End a meeting with decisions rather than impressions
A meeting becomes useful after it ends, when everyone knows which decision was made, who owns the next action and what remains open.
‘We discussed the launch’ is a record of activity, not an outcome. Someone absent from the meeting cannot tell whether the launch date changed, whether a proposal was rejected or whether the conversation merely raised questions. A useful close makes those distinctions explicit before everyone leaves.
Reserve the final few minutes for the outcome rather than squeezing it into a hurried farewell. The person facilitating can read back three things: decisions made, actions accepted and questions still open. These are different categories. Putting all three into one list of notes makes it easy to mistake an idea for an instruction.
Write the decision as a complete sentence
Use a sentence that could stand alone in a later update. In a hypothetical launch meeting, ‘We will publish the existing service page on Thursday; the proposed calculator is outside this release’ is more useful than ‘Website ready Thursday’. It names the scope and the boundary. Where the decision depends on a condition, include that condition rather than implying certainty.
Add a short reason when future colleagues are likely to question the choice. ‘The calculator is deferred because its figures have not been checked’ preserves the constraint without reproducing the whole debate. The point is not to document every opinion. It is to prevent the next meeting from reopening a settled question because nobody remembers the basis for it.
An action needs an accepting owner
Avoid assigning work to ‘the team’. Name one person who has accepted responsibility, the required output and a due date. That person may coordinate contributions from others, but the record should make it clear who will report completion. Ask for acceptance in the meeting; silence is a weak substitute for agreement.
Replace ‘check copy’ with something observable, such as ‘Alex will confirm the final service description in the shared document by Wednesday at 15:00 London time’. The name and timing here are illustrative. Use the actual owner, date and time zone for your work. If the owner cannot commit, record the dependency and who will resolve it rather than inventing a deadline.
Leave uncertainty visible
An unanswered question is not a failed meeting. It becomes a problem when the summary makes it look settled. Record what remains unknown and the next step for obtaining an answer. For a choice requiring approval, identify the approver and the material they need. Do not quietly convert a recommendation into an authorised decision.
Send a concise outcome note through the team's agreed channel and point to one maintained record. Invite factual corrections, especially from action owners. At the next relevant check-in, start with these commitments instead of reading the previous conversation aloud. The measure of a good meeting record is whether somebody can act from it—not how comprehensively it captures the room.
