Table of Contents
- Meeting Management
- Why Meeting Management Matters
- Types of Project Meetings
- Meeting Lifecycle
- Meeting Preparation
- Facilitation Techniques
- Decision Recording
- Action Tracking
- Meeting Etiquette
- Virtual Meeting Best Practices
- When NOT to Have a Meeting
- Meeting Effectiveness Checklist
- Common Meeting Anti-Patterns
- Related Resources
Meeting Management
Meetings are a fundamental governance mechanism in project and programme management. When run well, they drive decisions, align stakeholders, and maintain momentum. When run poorly, they waste time, drain energy, and erode confidence.
Why Meeting Management Matters
Effective meeting management:
- Ensures timely decisions are made at the right level
- Maintains project momentum and accountability
- Provides a forum for escalation and issue resolution
- Creates a documented audit trail of decisions and actions
- Builds trust and engagement among stakeholders
Types of Project Meetings
Different meetings serve different purposes across the project lifecycle. Understanding each type helps you design the right cadence and format.
| Meeting Type | Purpose | Frequency | Duration | Chair |
|---|---|---|---|---|
| Project Board | Strategic decisions, stage approvals, escalations | Monthly or at stage boundaries | 60-90 mins | Senior Responsible Owner |
| Steering Committee | Cross-project governance, portfolio alignment | Monthly or quarterly | 90-120 mins | Programme Director or Sponsor |
| Daily Standup | Progress updates, blocker identification | Daily | 15 mins max | Scrum Master or PM |
| Team Meeting | Coordination, planning, problem-solving | Weekly | 30-60 mins | Project Manager |
| Workshop | Collaborative working, design, analysis | As needed | 2-4 hours | Facilitator |
| Retrospective | Reflection, continuous improvement | End of sprint or stage | 60-90 mins | Facilitator |
| Risk Review | Risk identification, assessment, response planning | Fortnightly or monthly | 30-60 mins | Risk Owner or PM |
| Show and Tell | Demonstrate deliverables, gather feedback | End of sprint or milestone | 30-60 mins | Product Owner or PM |
Meeting Lifecycle
Meeting Preparation
Thorough preparation is the single greatest factor in meeting effectiveness.
Before the Meeting
| Activity | Responsibility | Timing |
|---|---|---|
| Define the meeting purpose and desired outcomes | Chair | 1 week before |
| Draft and circulate the agenda | Chair or PM | 3-5 days before |
| Distribute pre-read materials | Contributors | 3-5 days before |
| Confirm attendees and quorum | Chair or PA | 2 days before |
| Book room or set up virtual meeting link | Organiser | At scheduling |
| Prepare any presentations or papers | Contributors | 2 days before |
| Review previous actions and minutes | Chair | Day before |
Agenda Design
A well-structured agenda is the backbone of an effective meeting. Every agenda should include:
- Meeting title and date – clear identification
- Attendees and apologies – who is expected and who has sent regrets
- Review of previous minutes and actions – continuity and accountability
- Numbered agenda items with time allocations – keeps discussion focused
- Item owners – who is presenting or leading each item
- AOB (Any Other Business) – time-boxed to prevent scope creep
- Date of next meeting – maintains rhythm
Agenda Item Structure
Each agenda item should specify:
| Element | Description |
|---|---|
| Title | Brief, descriptive name |
| Owner | Person presenting or leading discussion |
| Time | Allocated duration in minutes |
| Type | For information / For discussion / For decision |
| Pre-read | Reference to any supporting documents |
Facilitation Techniques
Good facilitation ensures all voices are heard and meetings stay on track.
Core Facilitation Skills
- Time management – start and finish on time, enforce time-boxes
- Parking lot – capture off-topic items for later discussion without derailing the agenda
- Round-robin – invite each participant to speak in turn, preventing dominant voices from taking over
- Summarising – regularly summarise key points to confirm shared understanding
- Challenging constructively – ask probing questions to test assumptions
- Reading the room – gauge energy levels and adjust pace accordingly
Decision-Making Approaches
| Approach | When to Use | Pros | Cons |
|---|---|---|---|
| Consensus | Important decisions needing buy-in | High commitment | Time-consuming |
| Majority vote | Group decisions with clear options | Democratic, quick | May alienate minority |
| Delegated authority | Operational decisions within tolerance | Fast, empowering | Requires clear boundaries |
| Escalation | Decisions beyond the group’s authority | Appropriate governance | Can cause delays |
| Consultative | Leader decides after hearing views | Balanced speed and input | Leader must listen genuinely |
Decision Recording
Every decision made in a meeting should be recorded clearly.
A decision record should capture:
- Decision ID – unique reference for traceability
- Decision statement – what was decided, stated unambiguously
- Rationale – why this option was chosen
- Decision maker – who had the authority
- Date – when the decision was made
- Impact – what changes as a result
Action Tracking
Actions are the bridge between meetings and progress. Without disciplined action tracking, meetings become talking shops.
SMART Actions
Every action should be:
- Specific – clearly defined deliverable
- Measurable – you can tell when it is done
- Assigned – single named owner (not a team)
- Realistic – achievable within the timeframe
- Time-bound – specific due date
Action Register Fields
| Field | Description |
|---|---|
| Action ID | Unique identifier |
| Description | What needs to be done |
| Owner | Named individual responsible |
| Due date | When the action must be completed |
| Status | Open / In progress / Complete / Overdue |
| Source | Meeting and date where the action was raised |
Meeting Etiquette
Ground Rules
Establish and agree ground rules at the start of a project. Common rules include:
- Arrive on time and prepared
- One conversation at a time
- Laptops closed unless presenting (or cameras on for virtual)
- Mobile phones on silent
- Respect time-boxes
- Challenge ideas, not people
- Decisions are final once made (no re-litigation outside the meeting)
- Apologies must be sent in advance with a deputy nominated if needed
Virtual Meeting Best Practices
Virtual and hybrid meetings require additional discipline to be effective.
Before the Meeting
- Test technology in advance
- Share joining links with clear instructions
- Distribute materials electronically with sufficient lead time
- Consider time zones when scheduling
During the Meeting
- Use cameras where possible to maintain engagement
- Mute when not speaking to reduce background noise
- Use the chat function for questions to avoid interrupting
- Call on individuals by name to ensure participation
- Use screen sharing for visual materials
- Record the meeting if agreed by participants
After the Meeting
- Share the recording link alongside minutes
- Ensure actions are captured in a shared tool, not just in chat
When NOT to Have a Meeting
Not everything requires a meeting. Before scheduling, consider alternatives.
a meeting?} -->|Need a decision| B[Meeting] A -->|Sharing information| C[Email or Update] A -->|Need input from 1 person| D[1:1 Conversation] A -->|Brainstorming ideas| E[Workshop or
Collaboration Tool] A -->|Status update| F[Dashboard or
Written Report] classDef blue fill:#108BB9,stroke:none,color:#fff class A,B,C,D,E,F blue
Cancel or replace a meeting when:
- There is no agenda or clear purpose
- Key decision-makers cannot attend
- The topic can be resolved by email or a quick conversation
- There is nothing new to discuss since the last meeting
- Pre-read materials have not been prepared or circulated
Meeting Effectiveness Checklist
Use this checklist to assess whether your meetings are effective.
| Criteria | Yes / No |
|---|---|
| The meeting has a clear, stated purpose | |
| An agenda was circulated at least 2 days in advance | |
| Pre-read materials were provided where needed | |
| The meeting started and finished on time | |
| All agenda items had designated owners | |
| Decisions were clearly recorded | |
| Actions were assigned with owners and due dates | |
| Minutes were distributed within 24 hours | |
| Actions from the previous meeting were reviewed | |
| Participants felt the meeting was a good use of time |
Common Meeting Anti-Patterns
| Anti-Pattern | Symptom | Solution |
|---|---|---|
| The Status Report | Going round the table reading updates | Use a written status report; reserve meetings for discussion |
| The Marathon | Meetings regularly overrun | Enforce time-boxes; split into multiple shorter meetings |
| The Monologue | One person dominates | Use round-robin; facilitator to actively manage airtime |
| The Groundhog Day | Same topics revisited repeatedly | Track decisions formally; refer back to the Decision Log |
| The Ghost Meeting | Recurring meeting with no content | Cancel or reduce frequency; require justification to keep |
| The Cast of Thousands | Too many attendees, no one contributes | Limit attendance to those with a role; use RACI to determine who needs to attend |
Related Resources
- Decision Log – recording and tracking project decisions
- Communication Plan – planning stakeholder communications
- Organisational Structure – governance boards and reporting lines
- Assurance – quality assurance and gate reviews
- Project Reporting – status reporting and dashboards