How to build meeting follow-up into a system
What was supposedly decided in a meeting is remembered by no one a week later. This is often less a problem of individual memory than a structural problem of an organization that lacks a system for follow-up.
Why meetings end up with no follow-through
Right after a meeting, participants' minds are filled with the afterglow of the discussion and the switch to their next appointment. Carrying out the decisions feels days away, and in the meantime it gets swept aside by other priorities. As Ebbinghaus's forgetting curve (1885) shows, people rapidly forget what they learned over time unless they review it. Meeting decisions are no exception: decisions on which no first action is taken that same day tend to become less likely to be carried out as time passes.
That is exactly why, in follow-up, speed matters more than quality. Sharing a bulleted list of decisions within 1 hour tends to produce a higher execution rate than sharing perfect minutes a week later.
Breaking down action items - the 4-element model
Action items that get carried out usually have all of the following 4 elements. If any one is missing, the execution rate tends to drop.
- Who
- Who is responsible ("The whole team" means no one does it)
- What
- What exactly will be done ("Look into it" never gets done)
- When
- By when it will be finished ("As soon as possible" never comes)
- Why
- Why it is needed (Without knowing the purpose, its priority drops)
The difference between good and bad action items
| Wording that does not get done | Wording that gets done |
|---|---|
| "Strengthen collaboration with marketing" | "Tanaka: set up a 30-minute meeting with Yamada in marketing by 6/3" |
| "Estimate the cost" | "Suzuki: post cost estimates for options A/B to Notion by 6/5 17:00" |
| "Settle the direction by next time" | "PM: propose direction A at the next meeting on 6/10, with 20 minutes set aside for discussion" |
| "Everyone thinks about it" | "Everyone: post opinions as comments on the Notion page by 6/8" |
The left column has no clear subject, abstract actions, and no deadline. The right column states the subject, verb, deadline, and place.
Building follow-up into a system - a 3-layer structure
Secure follow-up through a system rather than relying on individual memory or effort. It works well to design 3 layers: an immediate layer right after the meeting, a check layer within a week, and a review layer a few weeks later.
- Post the decisions as a bulleted list in chat
- Register action items in the task management tool
- Send the invitation for the next meeting
- Automatic progress reminders to the people responsible
- Share the official version of the detailed minutes
- The PM reassigns tasks that have not started
- Review the previous action items
- Confirm together what is done, not done, or continuing
- Analyze why items are unfinished and remove blockers
Styles of minutes - full minutes vs summary minutes
If you think of minutes as a complete transcript of the meeting audio, both the effort to write them and the effort to read them are too great for them to be used. What tends to work in real organizations is summary-style minutes.
| Aspect | Full minutes | Summary minutes |
|---|---|---|
| Length | About 3,000 Japanese characters for a 1-hour meeting | About 400 Japanese characters for a 1-hour meeting |
| Time to write | 30-45 min | 5-10 min |
| Time to read | 10+ min | Under 1 min |
| Fidelity | Even the speakers' words are kept | Only the decisions are kept |
| Practical use | The discussion can be reconstructed later | The next action is clear at once |
| Recommended for | Legal records, regulatory compliance | Nearly all ordinary business meetings |
A very simple template is enough for summary minutes. One efficient method is to paste it into the calendar invitation and fill it in in real time during the meeting.
Linking with task management tools
Action items only mean something when they are not just written in the minutes but copied into a task management tool such as Asana, Jira, Linear, or Notion. Enforce the rule that tasks decided in the minutes are registered in the tool within 24 hours.
Meeting recording tools such as Otter and tl;dv have features that automatically extract action items and send them to task tools. Together with our calendar app comparison, this is also a good opportunity to review your company's meeting stack.
Failed follow-up is a sign of poor meeting design
If you feel follow-up is not working, it is often a sign that the meeting itself is poorly designed. Meetings that end with unclear action items usually come down to one of these causes: the issues were never sorted out, the decision-maker was not present, or the discussion scattered until time ran out.
A high-quality meeting always takes time 5 minutes before the end for everyone to confirm out loud what was decided today and what the next actions are. This 5-minute ritual raises the baseline quality of follow-up. When working on optimizing recurring meetings, improving how meetings end is a measure that tends to show results first.
A follow-up system is part of business meeting etiquette and part of asynchronous communication as well. Combine minutes and deadlines to build a culture in which decisions are reliably carried out. The questions to confirm can be narrowed to 3: "What did we decide today?", "Who does what next?", and "When do we meet next?". Meetings that confirm these out loud and post a summary in chat right away rarely end without follow-through.