The operating rhythm: making meetings earn their place

Meetings are not the problem, structure is

Most people who complain about meetings are not complaining about talking to colleagues. They are complaining about conversations with no purpose, no decision, and no memory. The same people will happily spend an hour in a well-run session that unblocks their week.

A business needs a rhythm: a small, predictable set of recurring conversations that catch problems early, make decisions at the right level, and keep everyone's picture aligned. Without one, coordination happens in ad hoc messages, which is slower, noisier, and leaves no record.

Design the rhythm before the agenda

Before scheduling anything, decide what the business genuinely needs to know at each interval. A useful frame is four levels of cadence, each answering a different question:

Daily: what is stuck today? A short session, fifteen minutes at most, focused only on blockers. Not a status round-robin. If someone has nothing blocked and nothing to flag, they can say so in a sentence and be done.

Weekly: what did we commit to, and what is at risk? Thirty minutes with the people who own the work. Review the small number of outcomes in flight, surface decisions needed, and adjust the week. This is where most operational management actually happens.

Monthly: are we on track against the bigger picture? Sixty to ninety minutes, wider attendance, looking at metrics, capacity, risks, and any cross-team trade-offs. Output is adjustments to plans, not a review of activity.

Quarterly: what are we choosing to do next? A longer session to re-prioritise. Decide what starts, what stops, and what the next quarter is for. The output is a short list of priorities with owners, not a presentation.

Not every business needs all four. A team of five might need only weekly and quarterly. A business running delivery for multiple clients usually needs the weekly and a per-client review. Choose deliberately, then hold the shape steady, because predictability is half the value.

Every meeting needs a job description

If you cannot write these five things down, the meeting should not exist:

1. Purpose. The question it exists to answer, in one sentence.
2. Attendees. Only people who contribute to or act on that answer.
3. Input. What people need to have read or prepared beforehand, and when.
4. Output. What exists at the end: a decision, a prioritised list, an updated plan.
5. Length. A hard stop, kept even when the discussion is unfinished, because running over is how one meeting damages the rest of the day.

A recurring meeting that cannot fill in the output line is usually a reporting habit. If the output is "information shared", ask whether it could be a written note instead.

Make the agenda about decisions

A standard agenda reads like a table of contents: project A update, project B update, finance, risks. It produces a polite recital in which nobody has to choose anything.

Start from the decisions instead. The organiser collects the open decisions in advance, prioritises them, and allocates time in proportion to their difficulty. Everything that is purely informational goes out as a short written note before the meeting, and is assumed read. Time in the room is then spent on the two or three things that genuinely need discussion.

A practical pattern for each decision item: state the question, give the background in two sentences, name the options, name who decides, then decide. This structure prevents the familiar drift into open-ended conversation.

Write things down, once, in one place

A decision that is not written down gets relitigated. Notes should be short and structured: what was decided, who owns it, by when, and what is still unresolved. Three or four lines per item is enough. Circulate them the same day, in the same place every time.

Resist the temptation to keep notes in three tools. A single shared document or channel per cadence is enough, and searchability matters more than elegance.

Default to asynchronous where it works

Some coordination does not need a conversation: status updates, announcements, links to work in progress, questions that one person can answer when convenient. These belong in writing, where they are searchable and do not interrupt anyone.

Synchronous time should be reserved for what genuinely benefits from it: disagreement that needs resolving, decisions with several trade-offs, planning that requires shared understanding, and anything where tone or nuance matters. A useful habit is to ask, before booking a meeting, whether the outcome could be achieved with a written message and a deadline for responses. Often it can.

Protect the space between meetings

The rhythm is only useful if people have time to act on what it produces. If the calendar is fragmented into half-hour slots, the effect of a good meeting is cancelled by the absence of uninterrupted work. Practical measures:

• Keep the same meeting days each week and cluster them, so other days stay clear.
• Protect blocks of two hours or more for work that requires concentration.
• Cancel meetings when there is nothing to decide, and say so in advance.
• Do not fill a freed slot with a new recurring meeting by default.

The cost is visible if you count it

It helps to be concrete. To calculate what a recurring meeting costs, multiply the number of attendees by its duration, and consider that cost against the output. A weekly hour with eight people occupies a full working day every week, in aggregate. That is a fair price for a decision-making forum and an unreasonable one for a status update that could be read in five minutes.

This is not an argument for fewer meetings as an end in itself. It is an argument for knowing what each one is for.

Signs the rhythm is broken

• The real decisions happen elsewhere. If the meeting discusses but the corridor decides, attendance will quietly decay.
• The same item appears every week. It is not being decided; it is being deferred. Give it an owner and a decision date.
• Nobody brings anything to review. Either the input requirement is not being enforced, or the meeting is not the right forum for that question.
• The meeting is used to find out what is happening. That means information is not flowing in writing, and the fix is upstream.
• Attendance keeps growing. Usually a sign the purpose has become vague; invite by role, not by hierarchy.

Start with one change

You do not need to redesign a company's calendar to test this. Take the meeting that most people dread, write the five-part job description for it, cut its attendee list, and make the agenda a list of decisions. Run it that way for a month.

If it improves, do the same to the next one. A rhythm that is designed on purpose, reviewed twice a year, and defended when it slips will do more for delivery than any tool you can buy.