Planning meetings and collaboration
Event meeting effectiveness review: a ten-minute check
Your planning committee meets every week, the meetings feel long, and nobody can say what they have actually decided lately.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A meeting effectiveness review looks at the last four to six meetings and asks six questions answered from records, not feelings: were decisions made, were actions closed, were the right people present, did the time match the agenda, were papers read, and did anything need a meeting at all.
Run it in ten minutes at the end of every sixth meeting, and change one thing at a time.
Six questions, with evidence to look at
| Question | Where to find the answer | What a weak answer looks like |
|---|---|---|
| 1. Were decisions made? | Count agenda items marked 'for decision' against decisions recorded in the decision log. | Most decision items carried forward. |
| 2. Were actions closed? | Compare actions set last meeting with those marked done at this one. | Same actions reappear with a new date. |
| 3. Were the right people there? | Check attendance of the decision owners for each item. | Items discussed with the approver absent. |
| 4. Did time match the plan? | Compare the agenda's timings with the clock. | The first two items used the whole meeting. |
| 5. Were papers read? | Ask whether anyone needed the paper explained in the meeting. See pre-read pack. | Papers presented aloud for the first time. |
| 6. Was a meeting needed? | For each item, ask if a written update or decision request would have done. | Status round-the-table took more than a third of the time. |
How to run the review
- Pick the last four to six meetings and gather agendas, minutes and the action list.
- Answer the six questions from the records, in about ten minutes, without debating individual cases.
- Write one sentence per question: strong, mixed or weak, with the evidence.
- Choose one change for the next six meetings, not three.
- Put the review date in the diary, and read the result at the start of that meeting.
Changes that usually help
- Move status items to asynchronous updates and keep the meeting for decisions.
- Send decision requests with options, owner and date before the meeting.
- Add a standing item at the start: actions overdue, using the follow-up routine.
- Invite the approver only for the items they decide, and put those first.
- Cap the meeting by agenda, not by the clock alone: items that do not fit move to a written route.
What not to measure
Avoid scoring people, or counting the number of meetings as a measure of effort. The review asks whether the meeting did its job: decisions, actions and the right people. If the answers are strong, shorten or cancel the meeting.
Worked example · Fictional example
A weekly committee meeting that never ends
Fictional organisation and figures, written to show the level of detail that is useful.
The planning committee of a fictional chamber of commerce meets for 90 minutes every week. A review of six meetings found 21 items marked for decision and 7 closed. The same four actions appeared in four consecutive minutes with new dates.
About half of each meeting was status round-the-table. The committee moved status to a Thursday written update, sent decision requests two days ahead and shortened the meeting to 45 minutes. At the next review, 11 of 14 decision items were closed and no action had appeared more than twice.
Use this yourself
Meeting effectiveness worksheet
Fill in once per review. Keep the completed sheets to see whether changes helped.
- Meetings reviewed (dates):
- Decision items listed / decisions recorded:
- Actions set / actions closed on time:
- Items where the decision owner was absent:
- Time planned vs time used for the first three items:
- Papers that needed explaining in the meeting:
- Items that could have been written updates or decision requests:
- Rating for each question: strong / mixed / weak:
- One change for the next six meetings:
- Owner of the change and review date:
Handle it in-house, or bring in help?
Your team can usually handle this when
- The chair or secretariat can read the records and be honest.
- Committee members accept changes to the meeting format.
- Only one or two items weigh the meetings down.
Outside planning help earns its fee when
- The meetings have become a standing complaint and nobody can change them from the inside.
- Several committees meet separately and decisions cross between them.
- The record of decisions is missing, so the review has no evidence.
Want an outside view of your meeting system?
A conference project lead can read your agendas, minutes and action lists, report what the meetings are producing, and set up a lighter rhythm of written updates and decision-only meetings. The committee decides what changes. Send the last four agendas and minutes.
Questions organisers ask
How often should we run a review?
Every sixth meeting is enough for a weekly committee. Run it sooner if the meetings feel stuck.
Who should lead the review?
The secretariat or project lead, using the records. The chair reads the result, since the chair also shapes the meeting.
What if there are no minutes?
Start recording decisions and actions for the next four meetings, then review. A review without records becomes a debate about feelings.
Should we cancel meetings that score well?
A strong score means the meeting is working. If it is short and productive, keep it. Cancel only when the same decisions could be made in writing.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.