No Agenda, No Meeting.
Why every meeting invite needs an agenda, and how to add one.
Imagine getting a calendar invite that just says "Quick sync" with zero context… and having no idea what it's about. We've all gotten one. Most of us have sent one, too.
Subject from Quick sync to Q3 launch: go/no-go decision
Name the decision, list what you'll cover, and attach the read-ahead—that's it.
On the receiving end of one? Jump to a polite reply
Before: the mystery invite
Am I in trouble? Do I need to prepare? What is this even about? 😰
An invite like this makes everyone on it context-switch twice—once to figure out what it's about, and again in the meeting when they arrive unprepared. A meeting without an agenda is like calling a function without documentation—you don't know what inputs to prepare or what outputs to expect.
After: same meeting, with an agenda
- Current status of API migration (5 min)
- Open questions on the deployment window (10 min)
- Decision: go/no-go for the beta release (15 min)
Everyone arrives prepared. The meeting is focused. Better decisions get made. ✨
Same time slot, same 30 minutes—but now everyone can prepare, the meeting stays on track, and you might even finish early.
Why this matters
Depending on whose survey you read, knowledge workers spend one to two full days a week in meetings—before they even start the "real work."
Every agenda-less meeting carries hidden costs:
- People show up unprepared, so the first 10 minutes is spent catching everyone up—information that could have been shared as a document.
- Without clear goals, meetings drift. You end 30 minutes later with no decisions and a vague promise to "circle back."
- Context-switching to and from a mystery meeting breaks up the deep focus work that creates actual value.
- Nobody can tell whether they're needed, so everyone comes "just in case."
When you're on the receiving end
Everyone gets a mystery invite now and then. No agenda? Ask for one, or decline politely. It's a reasonable request, and it often gets you a better meeting.
What to send back
Happy to join once there's an agenda and a desired outcome. Until then, could we start in a doc or thread?
If you're organizing
Before you schedule a meeting, ask yourself:
Can this start as a document instead?
You'd be surprised how often it can. A few minutes of writing often replaces waiting days for mutual availability and a 30-minute meeting. If you've done the writing and still need to meet, you've just created the agenda.
Writing scales; meetings don't. A well-written document can reach hundreds of people at their convenience without interrupting anyone's flow. A meeting reaches only the people in the room, only at that exact moment.
- Write first, meet second. Transfer context asynchronously and schedule a meeting only if the conversation requires it.
- Include clear goals. What decision needs to be made? What question needs to be answered? If you can't put it in a sentence, start with a doc.
- Time-box the agenda. A few minutes per item tells people what matters and keeps the meeting from drifting.
- Attach a read-ahead. Let people prepare on their own time instead of draining the first 10 minutes on information transfer.
Agenda template
Goal: [the decision we need to make or the question we need to answer] Agenda: 1. [Context or status update] (5 min) 2. [Open questions to discuss] (10 min) 3. Decision: [what we're deciding] (15 min) Read-ahead (please read before we meet): [link]