The Manager's New Brief

7.1

Ch. 7 — Meetings, Writing, and the Rhythm of a Healthy Team

Part II — Directing the work

💡 Core idea

Most teams do not have a meeting problem so much as a purpose and writing problem: too much live status, too little shared thinking, and no durable record of decisions.

If the work of the week only exists in rooms, the team has no memory and no way to include people who were not there. Writing is not bureaucracy. It is how thinking becomes shareable. Henrik Karlsson argues that thinking happens in writing. That is the intellectual case for the habits in this chapter. Vicki Boykis adds the standard: write for people, not for a generic audience or a model.

Meetings also have a measurable personal cost that is easy to misread. In a five-day diary study, Luong and Rogelberg (2005) found that the number of meetings in a day was associated with greater end-of-day fatigue and subjective workload; total time spent in meetings was not. Frequency of disruption, not raw minutes, was the load. The sample was small (37 administrative employees), so treat it as a precise warning, not a universal constant: more meetings can tire people even when the hours look modest.

Four meeting types, and almost no others

By default, a meeting should do one of four things: decide, explore, inform, or bond. “Inform” should be rare; most information can be written and read. If you cannot name the type, cancel or convert the meeting.

A simple hygiene rule: no agenda, no meeting; no decision recorded, it did not happen. An agenda and decision template is only useful if someone can state the ask. Rands treats a clear ask as the basic unit of a manager’s agenda. Without it, people leave having spoken and not having agreed.

In the room, Rands offers three reflexes: act last, read the room, taste the soup. Do not fill silence with your solution before you have heard the people closest to the work. Notice who is not speaking. Check the thing itself — the draft, the number, the prototype — rather than the performance around it.

When the room is tense, name the dynamic instead of steering around it. Leadership Garden is a short guide to that move. Avoidance feels polite. It is how the same meeting happens twice.

Writing carries status; live time carries decisions

Status can be read. Decisions, disagreement, and genuine exploration usually cannot — or not well. Move updates out of the room. Keep live time for what requires back-and-forth.

This is the same principle Ben Balter applies to 1:1s (Chapter 9): do not waste the only protected synchronous time on status that could have been written. It applies to the team meeting as well.

A decision that is not written will be relitigated (Chapter 6). An action that is not named will be dropped. The meeting was not the work. The record is.

A small rhythm is enough

You need less ritual than you think:

For hybrid and remote teams, write down async norms: expected response times, what “done” looks like in a document, and when to get on a call. A short team handbook — how we communicate, how we meet, how we decide, how we use tools — saves months of mind-reading.

Cancel freely. Adding a ritual is easy. Removing one is management.

Tools

🤖 AI-era tip: Close the loop in fifteen minutes — then a human sends it

Use an approved assistant to turn raw notes into a draft decision log and action list quickly. Then a named owner cleans, corrects, and sends. Auto-summaries miss jokes, tensions, and the thing everyone was careful not to say. The decision-maker should still be in the room for the decision. A summary is not a substitute for presence, and a fluent recap is not proof that the record is true.

Takeaways

Evidence