Productive Meetings & Team Cadence

Why your meetings feel the way they do, and why it isn't anyone's fault.

In January 1944 the Office of Strategic Services published the Simple Sabotage Field Manual, declassified in 2008 and still available in the CIA's reading room. It taught civilians in occupied territory how to paralyse an organisation without weapons — using procedure, caution and enthusiasm for process.

Its instructions to anyone in a supervisory role included: hold conferences when there is more important work to be done. Refer all matters to committees for further study. Bring up irrelevant issues as frequently as possible. Haggle over precise wordings. Refer back to matters decided at the last meeting and re-open the question of whether the decision was advisable.

Sit with that list, then open your calendar.

The critical point of this module, and the reason it comes first: not one of those tactics requires bad intent. Every one can be performed by a conscientious person who believes they're being thorough, and who will be described in their review as careful and collaborative. That was the design — the OSS needed sabotage that was invisible to the enemy and comfortable for the saboteur, and what they landed on was ordinary organisational virtue applied without a decision to reach.

So your team isn't sabotaging you. Nobody ever taught them to lead a meeting. We learn it the way we learn most workplace behaviour: by copying whoever ran the meetings we sat in when we were twenty-four.

A bad meeting is a thermometer. It's a symptom — of unclear process, unclear decision rights, or a habit nobody has questioned. We're going to fix the reading.

The task before step 2 👉Score your last meeting.

The objective, the five meeting types, and the agenda myth.

Most meetings open with slides. They should open with a destination.

👉 What's the objective of this meeting?

👉 Why are we here, and what do we need to leave with?

👉 What exactly do I need from each person?

Then the part that makes people uncomfortable: stop sharing the agenda. An agenda is your private tool for sequencing topics and budgeting time. It does almost nothing for the people receiving it. Swap the word "agenda" for "objective" in your invitations.

❌ "Q3 roadmap sync — see attached deck." ✅ "The objective of this session is to choose between roadmap options A and B. By the end I need a decision on which we resource, and the three risks you think I'm underweighting."

Almost every work meeting is one of five types, and naming yours tells you how to run it:

To inform — people receive and understand something. What matters is confirmation, not discussion. Most of these shouldn't be meetings. To discuss or gather input — opinions, ideas, knowledge. Roughly 60% work better async, because people need time to digest before they have a view worth having. To decide — a final discussion to make the call or approve. To solve a problem — usually urgent, needs several brains in the same place at once. 1:1s and connection /Team building— the relationship is the point. No async version exists for the last one.

The last two are what gets crushed when the first three eat the week. Module 6 is about protecting them.

👇The task before Module 3.

Write the objective for every recurring meeting you own (or one meeting this week), one sentence each. Any you can't write, bring to the group. That's the finding, not the failure.

A good question surfaces an assumption, exposes a risk, or forces someone to take a position. A bad question lets everyone nod.

"Do you have any questions or comments?" is the most polite way ever invented to end a meeting without learning anything. It assumes agreement, collects nothing, and signals that the decision was already made. It's a closing formality, not a tool.

The rule is three prepared questions, written in your notes before you walk in. Which three depends entirely on your objective — which is why Module 2 came first. Without a destination you can't tell a useful question from a polite one.

O — Objective. Start with the destination, not the deck. F — Feeling. Read the energy before diving into content. Q — Questions. Bring at least three that get you to the objective.

👇The task before Module 5.

Run one meeting with three written questions. Notice how long people talk compared to last time. Most people report the meeting ending early, which surprises them.

Most people think a good meeting is about charisma, or an agenda, or keeping it to 30 minutes. It isn't. After running and sitting through thousands of them, the difference between a meeting that moves work forward and one that quietly wastes an hour comes down to two things:

1. 🤓Know what type of meeting you're in — and prep for that type.

A meeting to make a decision is not the same animal as a meeting to gather opinions. When you don't name the type, you bring the wrong prep, ask the wrong questions, and everyone leaves unsure what just happened. Naming the type is half the work.

2. 🧐Ask powerful questions.

A meeting is only as good as the questions in the room. Weak questions get you status updates and silence. Powerful questions get you the thinking you actually came for. Prep gets the right people and information in the room; powerful questions get the value out of them.

That's the entire framework. Everything below is just applying these two moves to the meetings you already run.

Some meetings barely need prep. Some live or die by it. Here's the quick map, then the three that deserve real attention.

The light ones

These run fine on instinct.

The next three don't.

The three that reward prep — and powerful questions.

These are the meetings where "winging it" costs the most, because each one is really about getting information into or out of a room. The more you front-load the prep, the better the questions land.

Moving meetings async isn't a productivity trick that ends with an emptier calendar. It's a reallocation, and this module is about what you're reallocating toward.

Robin Dunbar, the evolutionary anthropologist, argued that human language evolved as a substitute for social grooming. Primates maintain alliances by grooming each other, which releases endorphins and builds the trust that makes cooperation possible — but as groups grew, grooming stopped scaling, and our ancestors would have had to spend nearly half their waking hours doing it. Language emerged as the efficient version of the same function. Talk is how we bond. It isn't a soft addition to cooperation; it's the mechanism.

Which means the 1:1, and the ten minutes before a workshop where someone mentions their kid was sick, is not the filler between real work. It's the infrastructure that makes the real work possible. Delete it and you've asked a group to cooperate without the thing our species uses to cooperate.

On problem-solving, a study in Science by Woolley and colleagues found groups show a measurable collective intelligence factor — not strongly correlated with members' individual intelligence, but correlated with social sensitivity and with how evenly conversational turn-taking was distributed. Groups where one person dominated performed worse.

Put that beside everything else in this training and the argument closes: the format where one person talks and everyone listens is the lowest-intelligence format available to us, and we made it the default — while the highest-intelligence formats are the ones we cancel when the week gets tight.

One last number. In that same Microsoft research, 81% of employees said it mattered that their manager helps them prioritise their workload, and fewer than a third said their manager had ever given clear guidance in a 1:1.

Those conversations aren't happening.

Something else is sitting in their slot.

The job: Inform the team or a stakeholder about something and confirm they actually understood it — even if that just means a few questions at the end.

Prep that makes it work: The hard part of an informative meeting is that people nod without absorbing. So your prep is about clarity and verification, not just delivery. Decide the one thing they must walk away knowing. Cut everything that isn't in service of that. Then plan how you'll check understanding, because "any questions?" almost always gets you silence.

Powerful questions to ask:

👉(Template: Informative meeting)

The job: Gather opinions, knowledge, and experience — brainstorms, input from other departments or stakeholders, exploring an idea. Risks get weighed and ideas explored, but nothing is decided here. It's a discussion, and that's the point.

Prep that makes it work: The most common failure is treating an opinion meeting like a decision meeting and pressuring people to "land it." Don't.

Your prep is about framing the question wide enough to get real range, and inviting the right mix of perspectives — not just the people who agree with you. Send the topic ahead of time so people arrive with thought, not reflex.

Powerful questions to ask:

👉(Template: Opinion meeting)

The job: Make a final call — approve something, continue a project, or choose between options.

Prep that makes it work: This is the meeting that most needs prep, because the decision quality is set before anyone walks in. Whoever prepares the session — async or live — has to gather and share all the necessary information beforehand so the decision-maker(s) have everything they need. If people are reading the context for the first time in the room, you're not in a decision meeting; you're in a slow, expensive opinion meeting. Name the decision-maker. Name the options. Share the evidence ahead of time.

Powerful questions to ask:

👉(Template: Decision meeting)

Here's the part nobody puts on the calendar invite: over 60% of the meetings in most departments can be done async — and they actually work better that way.

That's not a productivity hack. It's a quality upgrade. When you move the right meetings to async, four things happen:

People have time to think. A live meeting rewards the fast answer. Async rewards the good one. You get considered opinions and real evaluations instead of raw, half-formed ideas blurted to fill silence.

It's not just the loudest voice anymore. In a room, the most confident or senior person sets the tone and everyone else calibrates to them. Async flattens that — the quiet expert and the loud generalist get the same blank space to write into.

Better input, not faster input. When the format isn't a ticking clock, you get thoughtful evaluation instead of reaction. The opinion meeting that produces three real arguments async would've produced one confident shrug live.

Nobody's work is held hostage to a calendar. The worst tax of meetings is the wait. A decision that needs six people doesn't wait for the one slot all six are free — which is often days out. Async, the work keeps moving while people weigh in on their own time.

So which 60%? As a rule of thumb: Informative and Opinion meetings are almost always better async — broadcasting information and gathering input don't need everyone breathing the same air at the same time. Even a lot of Decision prep belongs async, with the live session reserved only for the final call (if you need one at all). What genuinely needs to be live: 1:1s, anything emotional or relational, real-time problem-solving, and decisions where you need to read the room.

The move isn't "have fewer meetings." It's: default to async, and earn the right to be live. Before you send the invite, ask the most powerful question of all —

"Does this actually need to be a meeting?"

More often than you'd think, the honest answer is no. And the work is better for it.

The closing task — team norms you will think you can commit to follow: