Meetings as a Productivity Measure
Meeting load and calendar fragmentation are measurable from data you already hold, and they explain more than most measures do.
How much of the week is in meetings, and how the rest is broken up, determines how much work can be done. Both are calculable from calendars and almost nobody calculates them.
The measurement warning in “Meetings as a Productivity Measure” matters whenever software records work patterns. Organisations researching does microsoft teams track your activity can use what Microsoft Teams activity tracking can reveal for time and project context, while outcomes, quality checks and direct feedback remain necessary to explain what the metric cannot show.
The two numbers
Meeting hours as a share of working hours.
For an independent perspective related to “Meetings as a Productivity Measure”, consult the NIST Privacy Framework; it offers a useful external check on definitions, governance and the assumptions built into a proposed measure.
And fragmentation: how much of the remaining time is in blocks long enough to use.
The second matters more and is reported less, because an hour between two meetings is not an hour of work.
Why fragmentation is the stronger measure
Resuming after an interruption has a cost, and it is not small.
Which means four separate hours produce considerably less than one four-hour block.
A calendar at forty per cent meetings can leave almost no usable time, depending entirely on how they are arranged.
Calculating it
Export calendars for a team for a month.
Count scheduled hours, and count gaps longer than ninety minutes.
Report both as weekly averages, by role.
An afternoon of work, and it frequently explains a productivity question that months of other measurement did not.
What it reveals
Roles with no usable time at all, which are usually the ones expected to produce analysis.
Days that are entirely meetings.
And a distribution: a few people carrying most of the load, which is a workload finding rather than a personal one.
The cheap interventions
A no-meeting day or half-day, protected.
Default durations of twenty-five or fifty minutes, which creates recovery gaps automatically.
Clustering meetings rather than spreading them.
Declining optional attendance, which requires permission from above to be real.
All are free and all are reversed within months unless somebody holds them.
The measure that follows
Hours reclaimed is not the point; usable blocks created is.
Track the fragmentation number before and after, which is the only way to know whether the intervention worked rather than just moved things around.
The honest caution
Meetings are not waste by default. Coordination is work, and under-meeting produces its own failures.
The finding is usually about arrangement rather than quantity, which is why fragmentation is the better number to manage by.
The upward version
If senior people's calendars are full, every decision they own becomes a queue.
Which the constraint note covers, and which makes executive calendar load a process measure rather than a personal one.
What to check
What share of your teams' weeks is scheduled?
How many usable blocks does a typical person have?
Is any time protected, and does it hold?
And are your most senior people the constraint on decisions?