Three things without which a meeting is pointless
Most advice on how to run a meeting starts with the agenda. That is the second step. The first is deciding whether the meeting should happen at all — and three things settle it.
A purpose stated as a question. Not "discuss the roadmap" but "which of the three features ships first". A topic can be talked about indefinitely; a question has an answer, and the moment it is answered the meeting ends.
People who can answer it. If the person who decides is absent, you are not holding a meeting, you are holding a rehearsal of one.
A written outcome. A decision nobody wrote down did not happen: in two days half the room will remember a different version, and the argument about who agreed to what costs more than the note would have.
Eight people for an hour is a working day of the company gone. Not "an hour" — a day. Any question about whether a meeting is worth it becomes easier once the number is on the table.
Before the meeting
Does this need a meeting at all
A meeting earns its place when a decision requires people to hear each other: there is disagreement, the choice affects several teams, or the question is too tangled for text. Everything else is a message, a document with comments, or a decision one person is authorised to make alone.
The honest test: write the message you would send if the meeting were cancelled. If it says everything — send it. This one habit removes more meetings than any policy.
Who to invite and who not to
Invite whoever the decision depends on and whoever will carry it out. Everyone else gets the notes. "Just to stay in the loop" is what turns a working group of five into a lecture for fifteen, where the cost per decision rises threefold and the quality falls: in a large room people stop objecting.
| Size | What it is good for | What breaks |
|---|---|---|
| 2–3 | Working through a specific question | Nothing — the most productive size |
| 4–7 | A decision affecting several teams | Needs a facilitator, otherwise the loudest wins |
| 8–12 | Informing, alignment | Discussion dies; the quiet ones stop speaking |
| 13+ | Announcements only | This is a broadcast. Consider whether it should be a letter |
The agenda as the price of entry
No agenda, no meeting — as a rule, not a preference. The agenda does two things at once: it tells people what to prepare, and it forces the organiser to formulate the question. Half of unnecessary meetings die at this step, because the author cannot write down what exactly is being decided.
Each item needs three attributes: a verb, an expected outcome and a time budget. "Pricing" is a topic. "Approve the price for the new tier — decision — 15 minutes" is an agenda item. We covered how to assemble one in the piece on the meeting agenda.
During the meeting
Three roles
The facilitator keeps the process, not the content: watches the clock, gives the floor, cuts drift. The note-taker records decisions and tasks — and this cannot be the same person, because running a discussion and writing it down simultaneously does not work. Participants come prepared.
The most common failure is the manager who is simultaneously facilitator, note-taker and the loudest opinion. Under that configuration the meeting turns into a monologue with pauses for agreement.
Timing
Set the end time and announce it at the start. Sixty minutes is the ceiling for substantive work; after that attention drops and people start agreeing to be done. For each agenda item name the budget aloud: "fifteen minutes on this". When the budget runs out, you either decide or move the item — you do not silently continue.
Cutting the drift
The rule is the same as everywhere: give the discussion an address. "This is important and it is not this meeting — Anna, Sergey, twenty minutes tomorrow, I will book it." A refusal without an address kills the topic; a redirect keeps it.
Getting the quiet ones to speak
Silence in a meeting is not agreement, it is most often the cost of speaking being too high. Two techniques work. Ask by name and by domain: not "any thoughts?" but "Dmitry, what breaks on the infrastructure side if we ship this on Friday?" And ask the most junior person first: after a senior opinion has been voiced, disagreeing with it becomes an act of courage rather than a normal contribution.
What to do with disagreement
Disagreement is the reason the meeting exists, so it should not be smoothed over. It should be made explicit: what exactly do the positions differ on, what evidence would change each side's mind, who decides if the evidence is unobtainable today.
If a dispute goes past ten minutes without new arguments, it is not a dispute about facts but about priorities — and it is settled not by discussion but by whoever owns the decision. Say that aloud and move on.
Four types of meeting, four different rules
| Type | Purpose | Length and size | What must remain |
|---|---|---|---|
| Operational | Sync the immediate work | 15 min, up to 9 | Tasks for today, blockers |
| Decision | Choose between options | 45–60 min, 3–7 | The decision, its rationale, the owner |
| Project status | Check against the plan | 30 min, leads | Deviations and risks with dates |
| Retrospective | Change the process | 60 min, the team | Two or three changes with owners |
The operational meeting is the one most often run wrongly: it is treated as a mini-version of everything else, and discussion leaks into it. It has a separate set of rules, which we covered in the piece on the daily standup.
After the meeting: without this step it did not happen
Within a day — ideally within the hour — the participants and everyone affected should get the record. Not a transcript: three blocks.
DECISIONS
· Ship tier B first. Rationale: it unblocks two enterprise deals.
Decided by: Anna (product).
TASKS (owner and date are mandatory)
· Sergey — pricing page for tier B, by 12 Sep
· Dmitry — estimate the migration, by 9 Sep
OPEN QUESTIONS
· Discount policy for annual plans — back to it on 15 Sep, owner: Anna
A task without an owner is nobody's; a task without a date is never. Both fields are non-negotiable, and this is the shortest path from a conversation to something actually happening. How a full record is structured is in the piece on meeting minutes.
A meeting policy: a sample you can adopt
Rules stop being personal preference the moment they are written down. This one fits on a page and can be adopted as is.
1. NO AGENDA — NO MEETING
The agenda goes out at least 12 hours ahead. Each item: verb,
expected outcome, time budget. No agenda — the meeting is cancelled
by anyone, without discussion.
2. WHO ATTENDS
Those the decision depends on and those who will execute it.
Everyone else receives the notes. Optional attendance is stated
explicitly in the invitation.
3. ROLES
Facilitator and note-taker are two different people, named in the invite.
4. TIMING
The end time is announced at the start. Default length 30 minutes,
60 is the ceiling. Past the budget: decide or reschedule.
5. THE RECORD
Decisions, tasks with owner and date, open questions — within 24 hours
in the shared channel.
6. THE RIGHT TO DECLINE
Anyone may decline a meeting whose purpose they do not understand,
by asking the organiser one question: what are we deciding?
Four antipatterns
A meeting instead of a message. Status updates, announcements, "let me walk you through it" — all of it is text, and text is read four times faster than it is spoken.
A meeting for attendance. A recurring slot nobody dares cancel. The cure is a review date: every quarter each recurring meeting is either confirmed or dropped.
A meeting without a decision. Ends with "let's think about it" — meaning it will be held again, with the same people and the same result. If the decision was not made, the honest ending names what is missing and who brings it by when.
A meeting with twenty people. Above a dozen participants, discussion stops physically. Either it is a broadcast (then it is a letter) or the guest list needs cutting.
Where Whisperer fits
In how to run a meeting, the last step is the expensive one. Keeping the record while chairing is impossible; a dedicated note-taker drops out of the discussion; and "we'll go through the recording later" is a thing nobody ever does.
Whisperer joins a live call and keeps a streaming transcript during the conversation itself: two independent audio streams — microphone and system audio — so replies are labelled by speaker and it is clear who proposed what. It works on a conversation in progress: uploading a finished recording is not supported.
Afterwards you get a meeting map with topics, decisions and tasks as separate nodes, so the review takes a couple of minutes — you see which agenda items closed and which surfaced instead. Tasks go to the tracker with an assignee and a date rather than into somebody's notebook. If the call runs across languages, there is real-time speech translation. The free tier is 60 minutes, enough to test it on one real meeting.
Frequently asked questions
How long should a meeting be?
Thirty minutes by default, sixty as the ceiling for substantive work. An operational sync is fifteen. Length is set by the number of agenda items and their budgets, not by what the calendar offers — the default hour in most calendar apps is the single largest source of wasted time.
Who should take the minutes?
Anyone except the facilitator. Chairing and recording at the same time does not work: one of the two always suffers, and it is usually the record. In small teams the role rotates; the alternative is an automatic transcript with a review afterwards.
How often should meetings happen?
As often as decisions are actually needed. A recurring meeting is justified when work genuinely interlocks; otherwise it is a report that could be read. Every quarter, review each recurring slot: has anything changed as a result of it in the past month?
Do I need a meeting if I could just write?
If the question has one correct answer and no disagreement — write. A meeting earns its place where positions differ, where the decision affects several teams, or where the subject is too tangled for text. The test: write the message you would send if the meeting were cancelled; if it covers everything, send it.
What if people show up unprepared?
That is an agenda problem, not a discipline problem: people prepare when it is clear what for. Send the agenda in advance with materials attached, and state explicitly what each participant is expected to bring. If the key person is unprepared, the honest move is to reschedule rather than spend an hour improvising.
How do you run meetings with a remote team?
Announce the speaking order in advance and name the next person aloud — online there is no non-verbal queue. Put links and numbers in the chat. Keep to shorter formats: attention online runs out faster. And do the record in writing without exception — remotely there is no "we agreed in the corridor" to fall back on.
How do you know a meeting went well?
One question: did every participant leave with something that changed their plans — a decision, a task, a cancelled piece of work? If the answer is no, the meeting was a report, and reports can be read with the eyes.
The bottom line
Running a meeting well is not a talent, it is a procedure: a purpose stated as a question, only the people who matter, an agenda with time budgets, a facilitator separate from the note-taker, and a record with owners and dates within a day. The antipatterns are equally short: a meeting instead of a message, a meeting for attendance, a meeting without a decision, a meeting with twenty people.
The simplest place to start is the last step, because it is the one that fails first. Create an account — 60 free minutes a month — turn on the transcript at your next meeting and compare what you would have written from memory with what the conversation actually contained.