Meeting Load Versus Focus Hours: A Two Week Audit You Can Run

If your team is missing dates and nobody can say why, run a meeting load versus focus hours audit before you change the plan. It takes two weeks, needs no new tools, and usually explains more than a retrospective does.

The method is counting. For fourteen days, everyone records how their working hours split between meetings, interrupted work and uninterrupted work. Then you put the numbers next to who the plan depends on. That comparison is where the answer usually is.

What to count

Three buckets, and only three. More categories make people give up by day four.

• Meetings. Any scheduled time with someone else, including stand ups, one to ones and calls that were meant to be five minutes.
• Fragments. Working time broken into pieces shorter than an hour by messages, tickets, questions or context switching.
• Focus. An unbroken block of an hour or more on one thing.

The hour threshold is arbitrary and that is fine. What matters is that everyone uses the same threshold, so the numbers can be compared.

Count each working hour as a meeting, a fragment or a focus block. Fourteen days is enough. The comparison that matters is between a person's focus hours and how much of the plan runs through them.

The two week method

1. Announce the purpose honestly. This is a workload check, not a productivity check, and the numbers will never appear in a performance review. Say that first or the data will be flattering and useless.

2. Give everyone the same simple record. A row per day, three numbers. Filled in at the end of the day, not in the moment.

3. Include yourself. Managers who exempt themselves get a smaller response rate and a less honest one.

4. Run it over a normal fortnight. Avoid a launch week, a holiday week or the week of an offsite. If you cannot find a normal fortnight, that is already a finding, and so is a cluster of short sick days in the fortnight after a launch.

5. Do not chase perfect data. Rough numbers from everyone beat precise numbers from half the team.

The template

Copy this into a shared sheet. One tab per person, or one sheet with a name column if your team is comfortable with that.

| Day | Meeting hours | Fragmented hours | Focus hours | Longest single block |

|-----|---------------|------------------|-------------|----------------------|

| Mon | | | | |

| Tue | | | | |

| Wed | | | | |

| Thu | | | | |

| Fri | | | | |

The last column does most of the work. Someone with four focus hours in four separate blocks is having a very different week from someone with one four hour block, and only that column shows it.

At the end of the fortnight, add three rows per person: total meeting hours, total focus hours, and the number of days with no block over an hour.

What the numbers usually show

Two findings come up again and again.

The people the plan depends on have the least focus time. The person reviewing everyone's work, answering the hard questions and sitting in the planning meetings is the same person whose tasks are on the critical path. Their meeting load is a direct tax on the dates you promised, and it is one of the quiet signs a team is past capacity.

Fragmentation is worse than the meeting count suggests. A day with two hours of meetings can still have zero focus blocks if those meetings sit at 11am and 2pm. The gaps are real hours and they produce very little. This is why the longest block column matters more than the totals. The same fragmentation turns up later in the tickets, where burnout shows before a survey catches it.

A third finding shows up in mixed teams: newer people often have plenty of focus time and not enough context, while experienced people have all the context and no time. That imbalance is fixable, and it is invisible without the audit.

What to do with the result

Change the calendar before you change the plan.

• Protect one block, not a whole day. A recurring two or three hour block that nobody may book, on the same day each week, is easier to defend than a no meeting Friday that quietly erodes.
• Move the meetings, not just delete them. Pushing three meetings to the same afternoon costs the same hours and returns a morning.
• Give the load bearing people the biggest blocks. If one person's focus time is on the critical path, treat it as a scheduled resource.
• Re-run the count in a quarter. One audit is a snapshot. Two is a trend, and a trend is what convinces people who did not believe the first one.

The audit is cheap and the argument it settles is expensive. Fourteen days of counting is a small price for finding out that your schedule problem was a calendar problem.