Meeting Agenda Builder

Overview

Why This Framework Exists

Research by Professor Steven Rogelberg shows that poorly managed meetings cost businesses $25,000 per employee every year. Up to 50% of meetings are completely unnecessary — and of those that are necessary, most are poorly run.

The Meeting Agenda Builder applies the principles from Chapter 16 of Resolute to the tactical level: given that you've decided a meeting is necessary (per your Meeting Canvas), how do you structure and run it so it actually produces outcomes?

The core principle: If a meeting doesn't need decisions or actions, it might not need to be a meeting.

When to Use This Template

• Before any meeting you are responsible for
• When redesigning recurring meetings that feel unproductive
• When preparing for high-stakes decisions that require group alignment
• When onboarding team members into your operating rhythm

When to Use This Template

• Before any meeting you are responsible for
• When redesigning recurring meetings that feel unproductive
• When preparing for high-stakes decisions that require group alignment
• When onboarding team members into your operating rhythm

The framework

Framework Purpose: A tactical template for designing and running a single meeting that drives decisions and outcomes. This is the companion to the Meeting Canvas (MQ4) — MQ4 designs the system (which meetings, what cadence), this template runs each meeting well.

Meeting Agenda Template

1. Meeting Identity

Meeting Name: [Clear, specific name — not "Team Sync" but "Weekly Pipeline Review"]

Meeting Type (select one):

• [ ] Decision-Making: We need to decide something specific
• [ ] Problem-Solving: We need to resolve a challenge or blocker
• [ ] Planning: We need to align on future actions
• [ ] Performance Review: We need to assess progress against goals
• [ ] Information Sharing: We need shared understanding (consider: does this need a meeting, or an email?)

Cadence: [One-off / Daily / Weekly / Fortnightly / Monthly / Quarterly]

Duration: [Time-box — shorter is almost always better]

2. Purpose and Success Criteria

Purpose Statement: [One sentence — why this meeting exists]

Success Criteria: [What must be true at the end for this meeting to have been worth everyone's time?]

• [ ] [Specific outcome 1]
• [ ] [Specific outcome 2]
• [ ] [Specific outcome 3]

The Exit Test: If you cannot define success criteria, cancel the meeting.

3. Attendees and Roles

The Participant Test: For each person, ask: "Can we achieve the meeting's purpose without them?" If yes, they don't need to attend. Send them the summary instead.

4. Pre-Work

[What attendees must review or prepare BEFORE the meeting. Pre-work shifts thinking time out of the meeting, making discussion time more productive.]

Pre-Work Principle: Never use meeting time for information that could be consumed asynchronously. Meeting time is for discussion, debate, and decisions.

5. Agenda Items

Time-Boxing Rules:

• Every item has a time allocation — no exceptions
• Facilitator calls time. If the discussion isn't resolved, the group decides: extend (by cutting another item), park for offline, or schedule a follow-up
• Start and end on time, every time. This is a respect issue, not an efficiency issue.

Agenda Design Principles:

• Put decision items early (when energy is highest)
• Group related topics together
• End with clear actions and owners (never end with "let's circle back")

6. During the Meeting

Facilitator Checklist:

• [ ] Start on time — don't wait for latecomers
• [ ] State the purpose and success criteria at the top
• [ ] Confirm the agenda (any changes?)
• [ ] Keep discussions on topic — park tangents
• [ ] Call time on each item
• [ ] Summarise each decision as it's made
• [ ] End with: decisions made, actions assigned, owners confirmed, deadlines set

Parking Lot: [Capture topics that come up but aren't on the agenda. Address after, not during.]

• [Topic — Owner — Follow-up by date]

7. Decisions and Actions

[Completed during or immediately after the meeting]

Decisions Made:

Actions Assigned:

Follow-Up Distribution: Summary sent to all attendees + informed parties within 24 hours.

8. Meeting Effectiveness Review

[Complete periodically — not every meeting, but regularly for recurring meetings]

Effectiveness Score (1-5): [Score]

What to improve next time: [Specific, actionable improvement]

Quality Indicators

As a facilitator or partner, look for these indicators of a well-designed agenda:

• [ ] Every meeting has a clear purpose statement (not just a title)
• [ ] Success criteria are defined before the meeting starts
• [ ] Each attendee has a reason to be there
• [ ] Pre-work shifts information consumption out of the meeting
• [ ] Every agenda item has a time allocation, owner, and desired outcome
• [ ] Decisions and actions are captured with owners and dates
• [ ] The meeting could not have been an email

Integration with Meeting Canvas (MQ4)

The Meeting Canvas answers: "What meetings are necessary, what should we discuss, and how do we solve problems together?"

The Meeting Agenda Builder answers: "Given that this meeting is necessary, how do we run it so it produces outcomes?"

Use together: Design your operating rhythm with the Meeting Canvas, then apply this template to each meeting type in your rhythm.

Integration with Waymaker Commander

When using the Waymaker platform:

• Meeting Agendas as Documents: Save completed agendas in Commander Documents, linked to the relevant project or team
• Actions as Tasks: Push action items directly into Commander Taskboards with owners and due dates
• Goal Alignment: Link meeting outcomes to Goal Canvas progress tracking
• Operating Rhythm: Meeting agendas connect to the broader MQ4 operating rhythm in your management plan