End a meeting with agreed actions and send notes people actually use.
Two weeks after a planning meeting, you ask how things are going and get three different answers: one person thought Grace was calling the vendor, Grace thought the matter was still under discussion, and your manager thought it had been decided the other way.
At the time, the meeting seemed to go well and everyone seemed to agree. Meetings rarely go wrong in the middle. Most go wrong in the last five minutes, when people are packing up and nobody says out loud what was agreed.
Reserve the last five minutes of every meeting for closing, and protect that time even if discussion is still going. In those minutes you do a read-back: you go through each item and say the decision and the action out loud, each with a name and a date, so the people in the room can correct you. Then you ask the room whether you got anything wrong, and fix any mistake on the spot.
Shu Fen chairs her team's Q4 planning meeting (an invented example) and closes it like this: "So we're confirming the 60:40 split, events to digital. Arun books the two November events, the Jurong roadshow and the client dinner, by Friday. Grace asks the AV vendor for a revised quote by the 15th. The website refresh is parked, and I'll raise it with Michelle next week. What have I got wrong?"
The read-back does two things. First, it catches misunderstandings while everyone is still in the room. Suppose someone says, "I thought Shu Fen was booking the dinner." The two of them can settle it in about ten seconds, whereas the same misunderstanding left alone can cause two weeks of confusion. Second, it makes people commit out loud, and an action a person has heard their own name attached to is far more likely to get done than one buried in notes they skimmed.
Every action needs exactly one owner, the single named person responsible for it. A vague group owner, such as "Marketing will look into it", means nobody will do it. If two people share a task, name one of them as the lead and treat that person as the owner.
Every action also needs a date, even a rough one. "Next week" is weaker than "by Thursday", but it is better than no date at all.
A parked item is a topic you set aside on purpose to deal with later instead of deciding it now. It still goes into the notes with the name of the person who will follow it up, the way Shu Fen records the website refresh with herself as the person raising it with Michelle.
Send the notes the same day, ideally within an hour of the meeting. Memories fade quickly, and people who weren't there are waiting to hear the outcome. A quick email also catches mistakes in the read-back while people still remember the meeting well enough to correct them.
Send the notes to everyone who attended and to everyone who needs to know. Lesson 6.1, "Decide if this needs to be a meeting at all", suggested leaving some people off the invite. Those people rely on the notes to learn what was decided, so the notes must reach them too.
Notes have four parts: decisions, then actions with owners and dates, then anything parked, then the date of the next meeting if there is one. Decisions go at the top because that is what readers look for first. The subject line should state the outcome. Shu Fen's subject line reads "Q4 planning notes: budget split and November events agreed", and the body looks like this:
Decision: Q4 budget split 60:40, events to digital. Decision: November events are the Jurong roadshow and the client dinner. The mall pop-up and the webinar are dropped for Q4. Action: Arun books the roadshow venue and the dinner, by 18 October. Action: Grace gets a revised AV vendor quote, by 15 October. Action: Shu Fen updates the Q4 budget sheet, by 16 October. Parked: website refresh. Shu Fen raises it with Michelle at next week's one-to-one. Next check-in: 24 October, 3pm.
Keep each line short enough to read on a phone. Leave out the discussion unless the reasoning will matter later, for example if someone might question a decision. In that case one line of "why" is enough, such as a note that the mall pop-up was dropped because Q3 footfall data was weak.
Don't write a transcript. Notes that record at length who said what are slow to write and slow to read, and people rarely open them again. People also become wary of speaking freely if they know every remark will end up in writing.
Many Teams and Zoom set-ups now offer AI transcription and summaries. If a meeting will be recorded or transcribed, tell people beforehand. Treat what the tool produces as a first draft only, because these summaries often miss who committed to what, which is the only part that really matters. Before you send anything, check the decisions and owners against what was actually agreed in the room.
Start the next meeting by going through the actions from the previous one. This is closing the loop, and it takes about two minutes. At Shu Fen's next check-in, she asks Arun whether the venues are booked and asks Grace about the vendor quote.
This review helps in three ways. People who know they'll be asked in front of colleagues are more likely to do the task. Stuck items come up now instead of a month later. Over time it also shows you whether your meetings produce results or only conversation.
If an action is late, don't make a scene. Ask what is blocking it and agree a new date, so the work keeps moving and nobody is embarrassed in front of the team.
Write the notes format once and reuse it. Most chat tools and email programs let you save a draft or template for this. With a template ready, you tend to fill in the sections during the meeting itself, so the same-day email is ready to send a few minutes after the meeting ends.
Write a notes template with three sections: decisions, actions with owners and dates, and parked items. Use it at your next meeting.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).