Agendas and Pre-Reads

The last page sorted meetings into distinct types, each with its own job. But knowing what kind of meeting you’re holding is only half the work. A status meeting and a decision meeting can both descend into the same fog — people wandering, no clear finish line, everyone leaving unsure what just happened. What keeps a meeting on the rails, whatever its type, is two humble documents you send before it starts: the agenda and the pre-read.

This page teaches both from first principles. An agenda is a promise about what the meeting will accomplish. A pre-read moves the reading out of the room, so the scarce, expensive live time is spent on the one thing that actually needs everyone in the same place at the same moment: talking to each other. Get these two right and half the battle of running a good meeting is already won before anyone sits down.

The principle: an agenda is a list of outcomes, not topics

Most agendas are written as a list of topics — subjects to be discussed:

AGENDA (the common, weak version)
- Budget
- Hiring
- The Q3 launch
- AOB (any other business)

Look closely and you’ll see the problem: none of these tells you when you’re done. “Budget” is not a finish line — you can talk about the budget forever. A topic invites discussion but never ends it, which is exactly why meetings run long and drift. A list of topics is a list of directions to wander in, not places to arrive.

The fix is to write every agenda item as an outcome to reach or a question to resolve. Instead of a subject, state the decision you need to walk out with, or the exact question the room must answer:

AGENDA (the strong version — outcomes and questions)
1. DECIDE: which of the two suppliers we sign for next quarter
2. DECIDE: do we move the launch date, yes or no
3. RESOLVE: who owns onboarding now that Priya has left
4. AGREE: the one metric we'll judge the new process by

Now each item has a built-in finish line. You know the budget item is done when a number is agreed. You know the hiring item is done when the question “who owns onboarding” has a name attached to it. A topic can run forever; an outcome tells you the moment you can stop and move on. This single shift — from nouns to decisions — does more to shorten meetings than any timer.

A useful test: for every line on your agenda, ask “How will we know this item is finished?” If you can’t answer, you’ve written a topic, not an outcome. Rewrite it as the thing that must be true when you move on.

In practice — the ward handover that never ended

A hospital ward held a daily handover meeting titled around topics: “patients,” “staffing,” “equipment.” It routinely ran forty minutes and nurses dreaded it, because “patients” had no natural end — you could always say more about a patient. When the charge nurse rewrote the agenda as questions — “Which patients need a plan change before the next shift? Are we short-staffed tonight, yes or no, and if so what’s the cover?” — the meeting dropped to twelve minutes. Nothing about the ward changed. Only the finish lines did.

Give each item a time and an owner

An agenda of outcomes has direction. To give it a shape — and accountability — add two more columns: a rough time and an owner for each item.

AGENDA — Team sync, Thursday 10:00 (25 min total)
────────────────────────────────────────────────────
#  Outcome / question to resolve          Time   Owner
1  DECIDE which supplier for Q3            10m    Sam
2  DECIDE: move launch date, yes/no         8m    Dana
3  RESOLVE who owns onboarding              5m    Priya
4  Buffer / anything urgent                 2m    —

The time is not a stopwatch you enforce to the second — it’s a budget that forces honesty. Adding up the minutes tells you, before the meeting, whether the agenda even fits the room you’ve booked. Four items that each “need twenty minutes” won’t fit in a thirty-minute slot, and the agenda is where you discover that — not at minute twenty-eight with two items untouched. If it doesn’t fit, you cut an item, shorten one, or book more time. The time column turns a wish list into a plan.

It also changes behaviour in the room. When people can see that the supplier decision has ten minutes, they self-regulate: the meandering story gets shorter, because everyone knows what it’s costing. Time budgets make the invisible cost of talking visible — the same cost you learned to take seriously in The Real Cost of a Meeting.

The owner is the person responsible for that item reaching its outcome — for bringing the context, framing the question, and driving it to a close. Not the same as the facilitator (who runs the whole meeting) and not necessarily the decider. The owner is simply the answer to “whose job is it to make sure item 3 actually gets resolved?” Without an owner, items float: everyone assumes someone else is carrying them, and they quietly evaporate. With an owner, there’s a name to prepare beforehand and a name to look to in the room.

The common trap — the agenda nobody owns

The most common failure isn’t a bad agenda; it’s an ownerless one. The organizer lists the items, sends it out, and assumes the items will somehow drive themselves. Then the meeting opens with “So… who wanted to talk about the budget?” and thirty seconds of silence. Every item needs a name beside it, decided in advance. If you can’t find an owner for an item, that’s often a sign the item doesn’t belong in this meeting — or in any meeting — yet.

Pre-reads: move the reading out of the room

Here is the second big idea, and it’s a lever most teams never pull. A huge amount of meeting time is spent on information transfer — one person catching everyone else up: here’s the data, here’s the background, here’s what happened last month. This is necessary work, but it’s a terrible use of a live meeting, because reading and listening-to-someone-read are things people can do alone, at their own pace, on their own time.

The insight is this: live time is expensive and rare; use it only for what genuinely requires everyone together. And almost nothing requires being together except one thing — interaction: discussion, debate, decisions, working something out that needs several minds bouncing off each other in real time. Information transfer is not that. So move it out.

A pre-read is a short document — a page or two, a set of numbers, a proposal, last week’s results — that you send before the meeting and expect people to have read before they arrive. It carries the information. Then the meeting itself starts where the reading left off: not “here’s what happened” but “given what happened, what do we do?”

WITHOUT a pre-read                 WITH a pre-read
──────────────────                 ───────────────
0–20 min:  presenter reads          Before: everyone reads (async,
           slides aloud; others             at their own pace)
           passively listen
20–30 min: rushed discussion        0–30 min: full discussion and
           at the end, out of time            decision — the whole slot

The gain is enormous. You reclaim the front half of every meeting, which is usually the half swallowed by catch-up. And you get better discussion, because reading privately lets people absorb detail, form a real opinion, and notice problems — none of which happens well while being talked at.

Case study — Amazon’s six-page memo

Starting in the early 2000s, Amazon famously replaced presentation slides in many meetings with a written narrative memo of up to six pages. The meeting opens with everyone reading it in silence — often for the first twenty or thirty minutes — before any discussion begins. The reasoning, as Jeff Bezos described it, is that a well-structured written argument forces clearer thinking than bullet points, and that reading it together in the room guarantees everyone has actually engaged with it rather than skimmed it beforehand. You don’t have to copy the exact ritual — the durable lesson is that separating information transfer from discussion, and putting the information in writing, raises the quality of both. (Treat the “six pages” and timings as their specific convention, not a universal rule.)

Note Amazon’s twist: they read the memo in the room because people don’t reliably read pre-reads at home. That’s a real risk, and you have two honest options. Either build a few minutes of silent reading into the start of the meeting (guarantees engagement, costs some live time), or send it early and set the cultural expectation that arriving unread means arriving unprepared. Which you choose depends on how much your team can be trusted to read ahead — a trust you build over time.

No agenda, no meeting

Put the two ideas together and you arrive at a rule worth making non-negotiable:

No agenda, no meeting. If an invite arrives with no agenda, it’s fair — and healthy — to decline or ask for one before accepting.

This sounds strict, but the reasoning is simple and generous. The agenda is not bureaucracy; it’s the only way an invitee can decide whether they even need to be there. Without it, everyone attends on faith, and faith is how meetings fill with people who have no stake in any of the outcomes. With a clear list of outcomes and owners, each invitee can look and ask: “Do I have anything to contribute to any of these? Am I an owner or a decider on any line?” If the honest answer is no, they can decline with a clear conscience — and the meeting gets smaller, cheaper, and sharper.

So the agenda does double duty. Before the meeting, it’s a filter that keeps the wrong people out and lets the right people prepare. During the meeting, it’s a map that keeps the room on course. A meeting with no agenda has neither — which is why “no agenda, no meeting” isn’t rigidity, it’s respect for everyone’s time.

The common trap — the agenda written in the room

Watch for the meeting that opens with “So, what did we want to cover?” — the agenda being invented live, in front of everyone. This defeats the entire purpose. Nobody could prepare, nobody could decide whether to attend, and the first ten minutes are spent building the map instead of walking it. If you find yourself writing the agenda at the top of the meeting, that’s the signal the agenda should have been written and sent a day earlier.

Circulate early enough that people actually arrive prepared

An agenda sent two minutes before the meeting is barely better than none — nobody can prepare, and nobody can bow out in time. The whole value of these documents depends on timing: they must arrive early enough that people can act on them.

A workable rule of thumb:

Recurring meeting (weekly sync, standup):   agenda by the day before
Decision meeting with a pre-read:            pre-read 24–48 hours ahead
Big / cross-team meeting:                    agenda + pre-read 2–3 days ahead

The heavier the reading and the more people involved, the more lead time they need. A one-page pre-read for a familiar team can go out the afternoon before. A dense proposal for a decision that affects five departments should land two or three days ahead, so busy people can find a slot to read it properly. Sending it early is not just courtesy — it’s the mechanism that makes the pre-read work. A pre-read nobody had time to read is just a longer meeting with extra steps.

A few practical habits that make early circulation actually happen:

• Put the agenda in the calendar invite itself, not buried in a separate message — so it travels with the meeting and is impossible to miss.
• Name the pre-read’s length and the ask. “10-minute read; come ready to pick option A or B.” People budget time better when they know the size and the point.
• Send a short nudge the morning of for anything that needs pre-reading: “Reminder — please read the two-pager before 2pm.”
• If the pre-read isn’t ready in time, move the meeting. A pre-read that goes out an hour before is a signal the meeting isn’t ready to happen. Rescheduling is cheaper than holding an unprepared meeting.

How it connects

The agenda and pre-read are what make everything downstream possible. They set up running the meeting — the facilitator’s job is far easier when there’s a map of outcomes to steer by. They feed directly into capturing decisions and action items, because an agenda written as outcomes practically writes the decision log for you: each resolved item becomes a recorded decision. And the “no agenda, no meeting” rule is the enforcement arm of when to meet and when a message would do — if you can’t name an outcome that needs live discussion, the honest answer may be that this should have been a message.

Try this

Take the next recurring meeting you own. Before it, do two things. First, rewrite its agenda: turn every topic (a noun like “budget”) into an outcome or question (a decision like “DECIDE: approve the revised budget, yes/no”), and put a rough time and an owner beside each line. Second, find the one item that’s really just information transfer — a status update, some numbers, background — and move it into a one-page pre-read you send the day before, so the meeting can open with discussion instead of catch-up. Notice how much shorter and sharper the meeting runs.

Reflect

1. Look at your last few meeting agendas. Were the items written as topics to discuss or as outcomes to reach? Pick one and rewrite it as a question the room must answer.
2. When your meetings run over, is it usually because an item had no finish line — a topic that could go on forever? Which of your recurring items is the worst offender?
3. How much of your typical meeting is spent on information transfer — one person catching everyone else up — that could have been read in advance?
4. Do the people you invite have a real way to judge whether they need to attend? Or do they come on faith because there’s no agenda to check themselves against?
5. When do your agendas and pre-reads actually go out — early enough for people to prepare and decline, or so late that they’re a formality? What would it take to send them a day earlier?

Show reflections

1. Most agendas are topic lists in disguise. The tell is that you can’t say when an item is “done.” Rewriting one item as a question — “which supplier?”, “move the date, yes or no?” — gives it a finish line, and that’s the whole shift this page is teaching. Do it once and the pattern becomes obvious everywhere.
2. Overrun almost always traces to items with no natural end. A topic (“the launch”) expands to fill any time given; an outcome (“agree the launch date”) ends the moment it’s reached. Naming your worst offender points you at the single item to rewrite first.
3. If a large chunk of your meeting is one person talking at the room, that chunk is a pre-read waiting to happen. The test: could this have been read alone, at each person’s own pace? If yes, it doesn’t need live time — and moving it out reclaims the front half of the meeting for the discussion that actually needs everyone present.
4. This is the deeper function of an agenda: it lets invitees self-select. If people can’t tell from the invite whether they’re an owner, a decider, or an unnecessary spectator, the meeting will bloat with attendees who have no stake. A good agenda quietly shrinks the room to the people who belong in it.
5. Timing is what makes pre-reads real rather than decorative. If yours go out minutes before, nobody can prepare and nobody can decline — the documents exist but do no work. The fix is usually a habit, not effort: put the agenda in the invite, and treat “the pre-read isn’t ready” as a reason to move the meeting, not to send it late.