Standard : Meeting Load Index

Description

Meeting Load Index measures the proportion of available team time consumed by scheduled meetings — particularly recurring meetings — as a proxy for leadership governance efficiency and a leading indicator of cognitive overload and reduced deep work capacity. In organisations where meeting load is high, people experience fragmented attention, reduced capacity for complex thinking, and a paradox where more coordination produces less coordination quality.

Leaders who actively manage meeting load are investing in one of the most direct forms of team capacity creation available to them — without adding headcount, without increasing budget, and without reducing ambition. Every unnecessary meeting removed is genuine capacity returned to purposeful work.

How to Use

What to Measure

  • Total calendar hours consumed by scheduled meetings per team member per week
  • Proportion of a standard working week (40 hours) consumed by meetings
  • Number of recurring meetings per team and their total weekly duration
  • Meeting types: decision-making, information sharing, coordination, ritual (standup, retrospective), and social — to identify where load is concentrated
  • Team members' self-reported sense of having sufficient uninterrupted time for deep work

Formula

Meeting Load Index = (Total scheduled meeting hours per person per week / Available working hours per week) × 100

Optional:

  • Recurring meeting burden: (Total recurring meeting hours per week / Total meeting hours) × 100 — isolates the structural load from ad-hoc meeting pressure
  • Deep work time: (Hours with 2+ consecutive uninterrupted hours / Total working hours) × 100 — a complementary measure of the impact of meeting load on focus capacity

Instrumentation Tips

  • Extract meeting data from calendar systems (Microsoft 365, Google Workspace) rather than relying on self-report — automated extraction provides more reliable and consistent measurement
  • Segment by role type — some roles have legitimate higher meeting loads than others; compare against role-appropriate benchmarks
  • Run a quarterly meeting audit: review every recurring meeting against its purpose and attendance list, and challenge those that fail to meet a clear value test
  • Combine quantitative load data with qualitative team feedback: "Do you have enough uninterrupted time for deep work?" provides essential context to the numerical measure

Benchmarks

Meeting Load Interpretation
Under 25% of working week Excellent — majority of time is available for focused work
25–40% of working week Good — reasonable meeting load for most collaborative roles
40–55% of working week Moderate — meeting load is constraining; deep work capacity is diminished
Above 55% of working week Poor — meetings are consuming the majority of team capacity; urgent reduction needed

Why It Matters

  • Meeting overload is one of the most pervasive forms of organisational waste Research consistently shows that a significant proportion of scheduled meetings are unnecessary, could be shorter, or could be replaced by asynchronous communication — making meeting load reduction one of the highest-return improvement opportunities available.

  • Deep work requires protected, uninterrupted time Cognitively complex work — strategy, design, analysis, writing — requires sustained focus. Fragmented calendars prevent deep work even when nominal capacity exists, reducing both quality and throughput of the work that matters most.

  • High meeting load is a proxy for unclear governance Organisations with high meeting loads often have unclear decision rights, insufficient asynchronous information flow, or excessive coordination requirements — problems that meetings are used to paper over without addressing the root cause.

  • Reducing meeting load creates capacity without cost Every hour of unnecessary meeting time returned to focused work is equivalent to a proportional increase in effective team capacity — making meeting load reduction a zero-cost productivity investment when done thoughtfully.

Best Practices

  • Conduct a quarterly meeting audit: review every recurring meeting, challenge its purpose and frequency, and remove those that fail to meet a clear value standard
  • Implement meeting-free time blocks (e.g. no meetings before 10am or on specific days) to protect deep work capacity structurally rather than relying on individual calendar management
  • Default to shorter meeting durations: 25 minutes rather than 30, 50 minutes rather than 60 — create space between meetings and reduce padding time
  • Replace information-sharing meetings with well-structured written communication where possible — asynchronous communication is often faster and more accessible than synchronous meetings
  • Model the behaviour you want to see: leaders who decline unnecessary meetings and keep their own meetings tight create permission for others to do the same

Common Pitfalls

  • Reducing meeting count without reducing meeting load — combining multiple meetings into one long meeting does not address cognitive fragmentation
  • Treating meeting attendance as a proxy for engagement or commitment — the leader who always attends every meeting is not necessarily the most engaged leader
  • Removing necessary coordination meetings in a meeting reduction drive, creating confusion and misalignment
  • Measuring average load without identifying the tail — some team members may be at severe overload while the average appears acceptable

Signals of Success

  • Team members report having sufficient uninterrupted time for deep work in pulse surveys
  • Meeting audit results show a declining count of recurring meetings over successive quarters
  • Calendar analysis shows a growing proportion of days with 2+ hour uninterrupted blocks
  • Delivery quality and throughput improve following meeting load reduction — confirming that protected focus time is producing better work
  • [[Impediment Resolution Time]]
  • [[Decision Escalation Rate]]
  • [[Capacity-to-Strategy Alignment Rate]]

Aligned Industry Research

  • Deep Work (Cal Newport, 2016) Newport's research demonstrates that the capacity for deep, focused work is the primary determinant of individual and organisational performance on cognitively demanding tasks — making meeting load reduction a strategic investment in output quality, not just efficiency.

  • No Meeting Wednesdays (Asana, Atlassian, and others) Multiple technology companies have published research showing that introducing structured meeting-free time significantly improves employee satisfaction, reduces burnout, and increases high-quality deep work output — providing empirical support for meeting load reduction as a leadership practice.