Meeting Agenda Builder

When to use

Triggers:

• "Build an agenda for [meeting]"
• "What should we cover in [meeting name]?"
• "Structure the [weekly / quarterly / kickoff / review] meeting"
• "1-on-1 template for [role]"
• "Planning a workshop / offsite"
• Before a meeting, when the user wants to avoid it dragging

Don't fire for:

• Meeting notes after the meeting (use meeting-notes-to-action-items)
• Meeting recaps to clients (use email-template-library — follow-up pattern)
• Large conference / event programmes (different planning discipline)

The filter — do you need this meeting?

Before building an agenda, ask:

Would an async message + a 5-minute reply accomplish the same outcome?

If yes, kill the meeting.

Meetings earn their slot when:

• Decision required with active discussion — multiple people, real trade-offs
• Alignment needed — people need to hear + ask live, not just read
• Creative work — brainstorming, problem-framing, working-through-a-gnarly-thing
• Relationship — trust-building, onboarding, addressing tension
• Accountability ritual — weekly rhythm that keeps a team moving

Meetings waste time when:

• Status updates that could be a document
• Information dumps with no discussion
• "Just checking in" without an agenda
• Recurring meetings that don't have specific items this time

The best agenda discipline is upstream: cancel meetings that don't earn a slot.

The 6 meeting archetypes

Most AU SME meetings fit one of these. Each has its own structure.

1. Weekly team stand-up (15–30 min)

Purpose: short, high-frequency rhythm to surface blockers + coordinate.

Structure:

• Start with a 2-min "what's changed since last week" from the leader
• Round-robin: each person 2 min on — what I did / what I'm doing / what's blocking me
• Parking lot: capture things that need deeper discussion (don't solve in stand-up)
• End with commitments for the week (1–3 per person)

Timing discipline: strict. 30 min max. Long stand-ups mean the format is wrong.

Exit criteria: every team member leaves clear on their week's commitments + blocker owner.

2. Decision-making meeting (30–60 min)

Purpose: make a specific decision that can't happen async.

Structure:

• Before the meeting (this is the key): pre-read document circulated 24–48 hours ahead. States the decision needed, options considered, recommended option, risks.
• In the meeting (30 min):
  • 5 min: confirm everyone read the pre-read + any clarifying questions
  • 20 min: discussion of the real contentious points (not a recap)
  • 5 min: decision + who owns execution + by when

Exit criteria: a decision is made. If the decision can't be made, the meeting clarifies what's missing and schedules a follow-up.

Anti-pattern: walking into a decision meeting without a pre-read. The first 30 min becomes education; the decision happens on surface-level info.

3. Brainstorm / problem-framing (45–90 min)

Purpose: open up a problem space before converging on solutions.

Structure:

• 5 min: facilitator frames the problem + the constraints ("We need to solve X within Y")
• 15 min: silent / individual idea generation on paper or shared doc (yes, silent — avoids HiPPO effect)
• 20 min: rapid share, no critique yet
• 20 min: cluster + discuss + poke at the top 3 ideas
• 10 min: decide what to try next (a decision, an experiment, a follow-up meeting)

Exit criteria: 2–3 candidate approaches identified + who does what next.

Anti-pattern: starting with "let's hear ideas" — extroverts dominate, quieter thinking gets lost.

4. Quarterly review (2–4 hours, sometimes half-day)

Purpose: step back from the week-to-week and look at where the business is going.

Structure:

• 30 min: numbers review — revenue, pipeline, customer metrics, cash, staff. Facts only, no interpretation yet.
• 45 min: what happened this quarter — wins, losses, key learnings. Each person contributes.
• 45 min: look forward — what's the next quarter's focus? 1–3 priorities, not 15.
• 30 min: specific commitments — who does what by when to execute the next quarter's focus
• 15 min: process check — what about how we work should change?

Exit criteria: a 1-page "next quarter plan" with priorities + commitments + review date.

Pre-work: numbers + individual reflection are pre-circulated. No reading in the meeting.

5. 1-on-1 (30–45 min, usually weekly or fortnightly)

Purpose: relationship + individual coaching. NOT status update.

Structure:

• 5 min: how are you? (genuinely)
• 20 min: their agenda — what do they want to raise? (They own this.)
• 10 min: your agenda — what do you want to raise? (Feedback, projects, clarifying direction.)
• 5 min: action items + next time

Exit criteria: both sides leave feeling heard; any blockers identified + owned.

Anti-pattern: 1-on-1 becomes a status-report meeting with managerial Q+A. That's not a 1-on-1; that's middle management inefficiency.

6. Client catch-up / account review (30–45 min)

Purpose: maintain the relationship + surface issues before they escalate.

Structure:

• 5 min: how's everything going? (open — invite them to raise things)
• 15 min: your updates on their work (not status report; highlights + any decisions needed)
• 15 min: their priorities shift — is the next 30 / 60 / 90 days still right?
• 10 min: any changes, next steps, forward calendar

Exit criteria: shared understanding of what's next + any scope/cadence adjustments agreed.

Pre-work: review their account (CRM, recent emails, current deliverables) before the call.

Agenda template (for any meeting)

# [Meeting name] — [Date]

**Facilitator**: [Name]
**Attendees**: [List]
**Duration**: [Time]
**Pre-work**: [Link to any pre-read + what they should do before]

## Purpose
[One sentence — why are we meeting?]

## Desired outcome
[One sentence — what does "meeting succeeded" look like?]

## Agenda

| Time | Topic | Owner |
|---|---|---|
| 00–05 | Check-in / context | [Facilitator] |
| 05–25 | [Main topic 1] | [Owner] |
| 25–40 | [Main topic 2] | [Owner] |
| 40–50 | Discussion / open floor | — |
| 50–60 | Decisions + commitments | [Facilitator] |

## Parking lot
Things to capture but NOT solve here:
- [ ]
- [ ]

## Action items (fill in during the meeting)
| Item | Owner | Due |
|---|---|---|
|  |  |  |

Timing discipline

• End 5 minutes early. People remember meetings that gave them buffer more than meetings that ran over.
• Start on time. Waiting for the last person penalises the ones who arrived on time.
• Have a timer visible. Even for the facilitator. Helps everyone self-govern.
• When you've reached the outcome, end the meeting. "Looks like we're done — let's get 20 minutes back."

Meeting-free days

A practice worth installing: one day a week (often Thursday or Wednesday) with no recurring meetings. Gives the team uninterrupted deep-work time.

If a meeting keeps getting booked on the meeting-free day, it's a flag that either:

• The day isn't actually protected (boundary problem)
• The meeting genuinely needs to happen weekly (in which case move it to a regular meeting day)

Remote / hybrid considerations

• Video-on default for meetings with more than two people; it makes the human connection much more effective
• For remote stand-ups, written stand-ups in Slack / Teams often beat live video
• Record decision meetings if you have team members in other time zones
• For important meetings: don't mix "in-room" people with "on-screen" people without explicit facilitation — the on-screen people get excluded by default

Anti-patterns

• Recurring meeting that never has real items — cancel or reduce cadence
• Meeting owner is not in the room — no one decides; send to the owner async
• Agenda of 12 items for a 30-min meeting — pick 3; carry the rest over
• Status update meetings — make them async written updates
• "Let's circle back on that" without a specific when or who — becomes orphaned
• No action items captured — the meeting didn't produce output
• Meetings that should have been a Slack message

Output format

Per request:

1. The agenda — per template, with time allocations
2. Pre-work brief — what participants need to do + read before
3. Facilitator notes — specific prompts / questions to use during key segments
4. Exit criteria — what success looks like at the end
5. Timing check — is the duration right for the agenda? If not, suggest what to drop

What this skill does NOT do

• Facilitate the meeting. Agendas are a tool; facilitation is a skill.
• Take the notes. Use meeting-notes-to-action-items after the meeting.
• Handle conflict. Agenda structure helps prevent it; managing it in the room is a different skill.
• Replace good meeting hygiene. Starting late, no pre-read, ambiguous ownership — no agenda fixes these.

Tier access

Base. Universal SME need. Pro-tier adds meeting-health analytics — track whether meetings are ending with decisions + action items over time.

Related skills

• meeting-notes-to-action-items — the after-the-meeting half
• customer-retention-churn-signals — client catch-up agendas pair with the retention-ops cadence
• thl-meeting-notes-to-followups (internal) — THL-specific post-meeting workflow

References

• Cameron Herold — Meetings Suck
• Patrick Lencioni — Death by Meeting