Meeting Design

Designing Meetings That Don’t Waste Time

If your calendar looks like a game of Tetris, you’re not alone. Most teams don’t have a meeting problem…they have a design problem.

A meeting is a tool. Like any tool, it works brilliantly when it’s used for the right job, by the right people, with the right constraints. When it isn’t, it becomes organisational tax…paid in attention, morale, and momentum.

Here’s how to design meetings that actually earn their seat on the calendar.

Start with the only question that matters: “What should be different afterwards?”

Before you send an invite, write one sentence:

“At the end of this meeting, we will have __________.”

Not “talked about”…not “aligned”…not “checked in”. Something concrete:

  • a decision

  • a prioritised list

  • a plan with owners and dates

  • a risk flagged and escalated

  • a problem solved (or narrowed down)

If you can’t finish that sentence, you don’t have a meeting…you have a vague feeling. Put it in a doc or Slack message instead.

Choose the right meeting type (most meetings are the wrong type)

Meetings usually fall into four categories. Name the category explicitly so everyone knows how to show up.

1) Decision Meeting

Output: a clear decision + owner + next step
Rule: no pre-read, no decision

2) Working Session

Output: a draft, a solved problem, a built thing
Rule: open a doc, work live, leave with something tangible

3) Status Update

Output: shared visibility
Rule: default to async; only meet for exceptions, blockers, and trade-offs

4) Connection / Culture

Output: trust, context, cohesion
Rule: protect these meetings…but keep them lightweight and optional when appropriate

The chaos starts when you think you’re running a decision meeting, but you’re actually running a status update wearing a decision-meeting costume.

Use constraints to force clarity

A meeting without constraints will expand to fill the time available.

Try these constraints:

  • 25 minutes instead of 30 (you’ll be amazed)

  • No agenda, no meeting (simple, ruthless, effective)

  • One decision per meeting (especially for leadership teams)

  • “Parking lot” rule for off-topic issues

  • “Two-way door vs one-way door”: reversible decisions get 10 minutes, irreversible ones get deeper thought

Default to async, then meet for the hard parts

A good modern rhythm looks like this:

  • Async for: updates, sharing context, collecting input, lightweight reviews

  • Meet for: disagreements, trade-offs, fast decisions, sensitive topics, complex problem-solving

If people are only attending to “stay in the loop”, you’ve built a visibility problem, not a meeting need.

Make the calendar honest: rename recurring meetings by their outcome

Most recurring meetings are legacy meetings…they exist because they always have.

Do a reset. Rename them like this:

  • “Weekly Team Meeting” → “Weekly Decisions + Blockers”

  • “Marketing Sync” → “Campaign Priorities + Trade-offs”

  • “Project Update” → “Project Risks + Escalations”

If a meeting can’t be renamed by outcome, it’s probably not earning its recurrence.

A simple meeting template you can copy-paste

Title: [Outcome] – [Topic]
Purpose: At the end, we will have ________.
Type: Decision / Working / Status / Connection
Pre-read: (link) or “none”
Agenda (time-boxed):

  • 0–3: context + outcome

  • 3–15: discussion / options

  • 15–20: decision / plan

  • 20–25: owners + dates + recap
    Attendees: Deciders / Doers / Experts
    Notes: Decisions + Actions captured live in doc

The anti-waste checklist (steal this)

Before you hit “Send”, check these five boxes:

1) The purpose is specific

Write it in the invite:

Purpose: Decide X / Solve Y / Produce Z

2) The right people are in the room

Use this simple filter:

  • Deciders: people who can say yes/no

  • Doers: people who will execute the next steps

  • Experts: only if their input is needed for the outcome

Everyone else? Send notes after.

3) There’s a pre-read or a prompt (not a massive deck)

If you need context, send one page or three bullets.
If it takes longer than 5 minutes to consume, you’re back to wasting time.

4) The agenda is time-boxed

A proper agenda is a timer, not a list.

Example:

  • 0–5: context + desired outcome

  • 5–20: options and discussion

  • 20–25: decision and owners

  • 25–30: recap + risks + close

5) The meeting ends with receipts

End with a recap that includes:

  • what we decided

  • what we’re doing next

  • who owns what

  • by when

If you don’t do this, you’re scheduling the same meeting again next week.

The real goal: fewer meetings, better ones

Time-wasting meetings don’t just cost hours…they cost energy. They fracture focus, make people cynical, and slow teams down in ways no one can quite measure.

The fix isn’t “run meetings better” in a generic way. The fix is to design them on purpose…with an outcome, the right people, a timer, and receipts at the end.

Your team doesn’t need more time.

They need better design.