Types of Meetings and Their Distinct Purposes

The Real Cost of a Meeting showed that every meeting is expensive in a way the calendar hides — you pay in the combined, uninterrupted time of everyone in the room. So the next question is not “should we meet less?” but “when we do meet, what is this meeting for?” That single question, asked honestly, prevents most of the meetings that feel long and produce nothing.

This page gives you a small, sharp vocabulary. There are only a handful of things a meeting can usefully do, and each one is a type. Once you can name the type of a meeting, you know who should be there, how long it should run, what to bring, and — most importantly — when it is over. The core insight of this whole part lives here: a meeting goes wrong mostly by trying to do several jobs at once.

Every meeting is really doing one of six jobs

Strip away the labels people give meetings and you find only six distinct purposes underneath. Almost any legitimate meeting is one of these:

Job          The one question it answers
---          ---------------------------
Coordinate   "Who is doing what next, and is anyone stuck?"
Plan         "What are we going to do, and in what order?"
Reflect      "How did that go, and what do we change?"
Review       "Is the work good enough — yes or no?"
Decide       "Which option do we choose?"
Connect      "How is this person actually doing?"

That is the whole map. A daily standup is a coordinate meeting. Sprint or project planning is a plan meeting. A retrospective is a reflect meeting. A demo, a design review, or a quality check is a review meeting. A meeting called to pick between two vendors is a decide meeting. A one-on-one is a connect meeting.

Notice that each job answers exactly one question. That is not an accident — it is the definition of a well-formed meeting. The moment a meeting is trying to answer two of these questions at once, it starts to feel heavy, and it usually finishes without properly answering either.

The six types, up close

Coordinate. The job is to sync who is doing what and surface blockers — nothing more. It is fast, frequent, and shallow by design. A ward handover at shift change and a warehouse morning huddle are both coordinate meetings: everyone leaves knowing what to do today and who needs help. What a coordinate meeting must not become is a problem-solving session — that is a different job.

Plan. The job is to turn a goal into a sequenced set of work. Planning is slower, needs the people who will do the work, and produces a concrete output: a list of committed tasks or a plan for a stretch of time. It happens at the start of a cycle, not daily.

Reflect. The job is to look back at a finished piece of work and decide what to keep and what to change. A retrospective, a project post-mortem, an incident review — all reflect meetings. Their output is a small number of changes the team will actually make, not a list of complaints.

Review. The job is to judge whether work is good enough: a design review, a demo to a customer, a code review walkthrough, a chef tasting a new dish before it goes on the menu. The output is a verdict — approve, revise, or reject — plus the specific reasons.

Decide. The job is to choose. A decision meeting brings the few people who own or inform the choice, lays out the options, and leaves with one option selected and recorded. If nobody in the room can actually make the call, it is not a decision meeting — it is a discussion that will need a real one later.

Connect. The job is human, not tactical: to understand how a person is doing, build trust, and clear the air. The regular one-on-one is the classic example. Its output is not a task list; it is a stronger working relationship and early warning of problems.

In practice — naming the type in the invite

A team lead at a mid-sized clinic started putting the type in the meeting title: “Coordinate: Monday handover (15 min)”, “Decide: which scheduling tool (30 min)”, “Reflect: Q2 retro (45 min).” Nothing else changed — same people, same rooms. Within a few weeks people showed up with the right mindset: they stopped trying to redesign the scheduling workflow during the 15-minute handover, because the word coordinate had already told them that was out of scope. The label did the work a firm facilitator would otherwise have had to do.

Why mixing jobs is the leading cause of bad meetings

Here is the mechanism, and it is worth understanding rather than just memorizing. Each job has a natural mode: a pace, a mindset, and a definition of “finished.”

• Coordinating is fast and shallow — you skim across everyone.
• Reflecting is slow and open — you sit with what went wrong.
• Deciding is convergent — you narrow options down to one.
• Reviewing is evaluative — you judge against a standard.

These modes actively fight each other. When you try to decide inside a coordinate meeting, the fast pace rushes the decision and the decision drags out the coordination — both jobs get done badly. When a reflect meeting drifts into planning the fix in detail, the reflection gets cut short and the plan gets made without the people who should build it. Mixing modes doesn’t average out to “okay at both”; it usually produces “bad at both.”

There is also a hidden cost: the wrong people are in the room. Each job has its own natural attendee set. Coordinate meetings want the whole working team. Decide meetings want the few people who own the choice. When you fuse them, you either drag decision-makers into daily standups or trap the whole team in a decision that three people should have made. Either way you are burning the expensive resource from the last page — collective attention — on people who have no job to do.

The common trap — the “quick update that turns into a debate”

The most common way meetings blow past their time is the coordinate meeting that hits a real problem and quietly turns into a decide-or-reflect meeting. Ten people who came to give a 30-second update now watch two of them debate an architecture choice for twenty minutes. The fix is a simple, repeatable move: when a meeting tries to change jobs mid-flight, name it and defer it. “That’s a decision, not an update — let’s take it offline with the two people who own it.” You are not refusing to solve the problem; you are refusing to solve it in the wrong meeting, with the wrong people, in the wrong mode.

Each type has a natural cadence, attendee set, and output

Because the job determines the mode, it also determines almost everything practical about the meeting. If you know the type, you can derive the rest instead of guessing.

Type        Cadence            Who's there              What it produces
----        -------            -----------              ----------------
Coordinate  daily / per shift  the working team         shared picture + blockers named
Plan        start of a cycle   the doers + owner        committed, sequenced work
Reflect     end of a cycle     the working team         a few concrete changes
Review      when work is ready doers + the judge(s)     a verdict + reasons
Decide      when a choice      the deciders + informers one recorded decision
            is needed
Connect     weekly / biweekly  two people               trust + early warnings

Read across any row and the meeting almost designs itself. A reflect meeting at the end of a two-week cycle, with the working team, aiming for a few concrete changes — that tells you it should be a longer, calmer slot than a standup, that outsiders shouldn’t attend, and that if it ends without any agreed changes, it failed regardless of how good the conversation felt.

This is why agendas and pre-reads become easy once the type is fixed: the type tells you what preparation the meeting needs. A decide meeting needs the options written up before the meeting so the room can converge instead of discover. A coordinate meeting needs almost no prep at all. Preparation should match the job.

The evidence — meetings people rate as pointless

Surveys of office workers consistently find that a large share of meetings are rated as unproductive or unnecessary by the people who attend them, and “no clear purpose” or “wrong people in the room” show up repeatedly among the top complaints. The precise percentages vary from study to study and should be taken as rough, but the direction is consistent: meetings fail far more often from unclear purpose than from bad facilitation. Naming the type is the cheapest available fix, because it addresses the most common cause.

Naming the type sets the right expectations

Once you name a meeting’s type out loud — in the title, in the first sentence, on the agenda — you are quietly setting four things at once:

1. Tone. A connect meeting invites openness; a decide meeting invites brevity. People calibrate automatically once they know which one they’re in.
2. Preparation. The type tells everyone what to bring: options for a decision, a demo for a review, nothing but their status for coordination.
3. Length. Coordinate meetings are short by nature; reflect and decide meetings need room to breathe. The type sets a sane default before anyone books an hour out of habit.
4. When it’s over. This is the big one. Each type has a clear finish line — blockers surfaced, plan committed, decision recorded, verdict given. A meeting with a named type knows when to stop.

A meeting with no named type has none of these. It has no natural tone, no obvious prep, no honest length, and — fatally — no finish line. So it expands to fill the hour someone booked, every single week.

The unnamed recurring meeting that drifts

This is the most dangerous meeting on any calendar, so it deserves its own warning: the standing recurring meeting that never had a clear type.

It usually starts for a real reason — a project kickoff, a tense period, a new team forming. Someone makes it recurring “so we stay aligned,” and the original reason quietly expires. But the meeting doesn’t. Because it has no defined job, it can never be finished — there is no verdict to give, no decision to record, no plan to commit. So it becomes a catch-all: a little coordinating, a little venting, a little half-deciding, a little status theater. Everyone leaves vaguely dissatisfied and no one can quite say why, so no one cancels it. It survives on inertia, not value.

The cure is a single blunt question, asked of every recurring meeting on the calendar: “Which one of the six jobs does this do?” If you can’t answer in one word, the meeting doesn’t have a type — and a meeting without a type should be split into the real meetings hiding inside it, shrunk to the one job it actually does, or killed outright. Most calendars have at least one of these. Finding and fixing it will buy back more time than any other single change in this part.

Case study — Amazon’s typed, written meetings

Amazon is well known for a distinctive meeting practice that took hold in the 2000s: many meetings begin with everyone silently reading a written narrative — often described as a “six-page memo” — before any discussion. What is easy to miss is that this only works because the type of the meeting is fixed in advance. The memo is written for a specific job — usually to decide or to review — and the silent read forces the room into the matching mode from minute one. You can debate whether the format suits your organization, but the underlying lesson is portable and cheap: decide what a meeting is for before it starts, and shape everything else around that one job.

How it connects

Types are the backbone of this whole part. Agendas and pre-reads get simple once the type is fixed, because the type dictates the prep. Running a meeting is mostly the discipline of keeping the room in the meeting’s one mode. Capturing decisions and following up matters most for decide and reflect meetings, whose whole value is the output they produce. And making standups, planning, retros, and reviews useful is this page applied to the four recurring rituals most teams run. One-on-ones — the connect type — get a full part of their own in One-on-Ones.

Try this

Open your calendar for the next two weeks and, next to each recurring meeting, write the single job it does using one of the six words: coordinate, plan, reflect, review, decide, connect. If a meeting needs two words, mark it — that is a mixed meeting, and it is probably your worst one. If a meeting needs no word, mark it harder — that is an untyped drifter. For at least one meeting you host this week, put the type in the title (e.g. “Coordinate: Tuesday sync — 15 min”) and watch whether people show up with the right mindset.

Reflect

1. Which of your recurring meetings can you not label with a single one of the six job-words? What is it actually trying to do?
2. Think of a recent meeting that felt long and unproductive. Was it trying to do two jobs at once — and if so, which two, and how did their modes fight?
3. For a meeting you host, does the current attendee list match the job? Who is there who has no role in that specific job?
4. Is there a standing meeting on your calendar whose original reason has expired but which still runs every week? What would happen if you cancelled it for a month?
5. What would change in how people prepare for, and behave in, your meetings if every invite stated its type in the first line?

Show reflections

1. The meetings you can’t label in one word are your highest-value targets. An honest answer usually reveals a fusion (“it’s kind of a status update but also where we make calls”) — which is exactly the mixing this page warns against. The fix is to split it or shrink it to its real job.
2. This connects the feeling of a bad meeting to its cause. Good answers identify the two jobs (e.g. coordinate + decide) and notice how the fast mode of one rushed the slow mode of the other, leaving both half-done.
3. Attendee lists tend to grow by habit and politeness, never shrink. Naming who has no role in the specific job is the first step to giving people their time back — and it usually makes the meeting sharper, not weaker.
4. Almost every calendar has one of these drifters. The “cancel it for a month” test is deliberately concrete: if nobody misses it, you have your answer. If a real need surfaces, you now know its actual type and can rebuild it properly.
5. The point is that naming the type does the work a firm facilitator would otherwise have to do — it sets tone, prep, length, and the finish line for free, before anyone enters the room. Most people find the label changes behavior more than they expected.