Skills
A meeting ends on time because of decisions made before it starts
Overrunning is a design failure rather than a discipline failure, and almost all of the fix happens outside the room.
By Zubin Mistry3 min read
Overrun is designed in
Meetings that run late are usually blamed on people talking too much, and the remedy proposed is firmer chairing. That mostly fails, because the real cause was settled before anyone sat down: nobody decided what the meeting was for, who needed to be there, or what would constitute finishing. A group asked to discuss a topic will discuss it indefinitely, since there is no condition under which discussion is complete.
The most useful distinction is between a meeting that needs to reach a decision and one that exists to share information or generate ideas. Those have different shapes, different attendees and different endings, and the mixed meeting that tries to do all three is the one that always overruns.
State the outcome, not the topic
An agenda item written as a topic — "Q3 planning" — has no end state. The same item written as an outcome — "agree which two of the four projects we staff in Q3" — tells everyone what finishing looks like, which lets you notice when you have got there and lets people tell whether they need to attend at all.
This also exposes items that should not be a meeting. If the outcome is "everyone knows the new process", that is a document. If it is "I need three people to react to a draft", that is a shared file with comments. The most efficient chairing decision is frequently to cancel, and the reason it happens so rarely is that nobody wrote the outcome down and so nobody noticed.
Pre-reads work, with one condition
Sending material in advance converts twenty minutes of presentation into five minutes of questions, but only if people read it, and by default they will not. The condition that makes it work is being explicit and consistent: say that the first few minutes are for reading, and then actually hold that silence rather than starting anyway because it feels awkward.
Reading in the room feels wasteful and is not. It guarantees a common starting point, it puts everyone at the same level of preparation regardless of how their week went, and it removes the person who derails a discussion with a question answered on page two. It is more socially difficult than it is practically difficult.
Managing the room without authority
Junior people often assume they cannot steer a meeting they did not convene. In practice a few moves are available to anyone and are received as helpfulness rather than presumption. Asking what we are trying to decide, when a discussion has drifted. Offering to note the actions. Asking, near the end, whether we have an owner and a date for each thing agreed.
The most valuable of these is naming the drift. When a conversation has moved onto a genuine but different problem, saying so — "this seems like a separate question, should we take it away?" — is almost always welcomed, because several people had noticed and none of them wanted to be the one to interrupt. That intervention alone recovers more time than any other.
Timeboxing helps if it is set at the start rather than imposed halfway, since announcing a limit mid-discussion reads as a judgement on whoever is talking. Agreeing at the outset that an item gets fifteen minutes makes the later interruption procedural rather than personal.
The ending is the part that gets skipped
Most meetings stop rather than conclude. The clock runs out, people leave, and the decisions exist only in several slightly different memories. Two minutes reserved at the end for stating what was decided, who owns what, and by when converts a conversation into something that will actually happen.
Send that summary the same day. It is short, nobody else will do it, and it quietly settles disputes that would otherwise surface in three weeks as a disagreement about what was agreed. It also makes clear when nothing was decided, which is uncomfortable and useful, because a meeting series that produces no decisions is easier to cancel once that is written down.
The honest limit
Some meetings exist for reasons that have nothing to do with their stated purpose. A standing meeting can be a way for a senior person to feel informed, a ritual that maintains a relationship between teams, or a habit nobody has the standing to end. Applying good design to those changes very little, and pushing hard against them can look like a junior person misunderstanding the politics.
It is worth telling the difference before spending capital. Where a meeting has a real job, the techniques above work and people are grateful. Where the meeting is the point, the achievable goal is to make it shorter and to spend the rest of your attention elsewhere.
Common questions
Can I decline a meeting as a junior employee?
Sometimes, and asking is safer than declining. "Is it useful for me to be there, or would the notes be enough?" gives the organiser an easy out and signals that you are thinking about your time rather than avoiding work. In some cultures this is entirely normal and in others it is not, so watch what your peers do first.
What if the person chairing lets it overrun every time?
Volunteer for the parts they are not doing rather than critiquing the chairing. Offering to circulate an agenda beforehand or notes afterwards is help, not criticism, and it fixes most of the practical damage without anyone having to lose face.
How long should a meeting be?
Shorter than the default your calendar tool offers, which is a real and slightly absurd influence on how long meetings are. Setting twenty-five or fifty minutes rather than thirty or sixty also gives people a gap to travel or think, and the shorter time is almost always sufficient once the outcome is defined.
Editor, After the First Job
Zubin covers first months, managing up, money at work and the questions readers actually send in and is happiest when a piece answers the question completely.
