How to run effective meetings: a working checklist

A meeting works when one person owns it, it has a decision to reach, and everyone leaves knowing who does what next. In our experience most bad meetings have already failed one of those three before anybody speaks. The fixes are unglamorous and they are mostly done in advance: write the decision down as a question, invite the people who can answer it, send whatever has to be read beforehand, and finish by saying the owners and dates out loud so nobody has to guess. If you cannot write the question, you have a document to circulate, not a meeting to hold.

The checklist

Three lists. The first one is the one that matters — most meetings are won or lost before they start.

Before — the day before, not the hour

Write the decision as a question in the invite title. Invite the people who can answer it and nobody else — a spectator is a cost. Attach the pre-reading and say plainly that the first minutes are for reading it if people have not. Decide who is running it, which is not automatically the most senior person present.

Before — the invite itself

[Decision to reach] — [who decides] — [what to read first]. That title does more work than an agenda nobody opens. If two decisions belong in one meeting, they are two agenda items with two time boxes, not one long conversation that eats the second one.

During — the first two minutes

Say the question out loud and say what happens if it is not answered today. That single sentence is the difference between a discussion and a decision. Then say who is taking the record, because if nobody is named, three people take partial notes and none of them are the record.

During — the middle

Keep the question visible. When the conversation drifts somewhere useful but different, name it and park it in writing rather than following it or killing it — a parked item with an owner is how you leave the room with one decision instead of half of three.

During — the last five minutes

Stop early on purpose and read back three things: what was decided, what was explicitly not decided, and each action with an owner and a date. Read them aloud. Something written down but never said aloud is the kind of thing people remember differently a fortnight later.

After — within the day

Send the recap while the meeting is still recent. It does not need to be long — decision, non-decision, actions with owners and dates, and the parked list. Sending it the same day is what makes it the record. Leave it three days and you are circulating a recollection, which people argue with rather than correct.

The ones to cancel instead

Three kinds are not fixable by better facilitation. A status meeting where each person reads their update to people who could have read it. A recurring meeting nobody can name the purpose of. And a meeting called because a written decision is hard to make and a conversation feels easier — that one produces the same difficulty, later, with more people in it.

Questions

What makes a meeting effective?

A named owner, a decision written as a question, and a close that states who does what by when. Meetings that have all three tend to work regardless of length or format; meetings missing any one of them tend to fail regardless of how well they are run.

How long should a meeting be?

As long as the question needs, which is usually shorter than the calendar default. Thirty minutes for one decision and fifty for two is a better habit than an hour for whatever comes up. Ending early is a feature and people notice it.

Who should take notes in a meeting?

Not the person running it — facilitating and recording compete for the same attention and the record loses. Name someone at the start, or capture the audio and let the summary be the first draft, which is the only way the person leading also ends up with a record.

Should I cancel recurring meetings?

Cancel any recurring meeting whose purpose nobody in it can state in one sentence. A useful test: cancel it for three weeks and see what breaks. Usually the answer is nothing, and occasionally the answer is something important, which tells you what the meeting was actually for.

What should go in the meeting invite?

The decision as a question in the title, the pre-reading attached, and the list of attendees kept to people who can answer it. An agenda in the body is fine but it is read far less often than the title, so the title has to carry the point.

How do I stop meetings from drifting?

Park the drift in writing rather than following or killing it. Say "that is real, it is not this, I am writing it down with your name on it" — that sentence keeps the question alive without making the person who raised it feel shut down.

What is the ideal number of people in a meeting?

Small enough that everyone present would be missed if they were not there. A useful test before sending the invite: for each name, write the sentence explaining why the decision needs them. If you cannot write it, they get the recap instead.

How do you end a meeting on time?

Reserve the last five minutes on the agenda for the read-back and treat that as the hard stop, rather than the end of the hour. A meeting that finishes at fifty-five minutes with a clear record beats one that runs to sixty and dissolves.

None of this needs a product. The one part that is genuinely hard without help is the last-five-minutes read-back, because the person running the meeting is the person least able to take the record — which is the problem we build for. Scriben is recording people know about. You say what the pen is and what it does, they agree, and then it stays out of the way for the rest of the conversation — that second half is the product, and it only works after the first. Recording law varies by jurisdiction and by profession: see recording people lawfully before you start.