Meeting frequency rate

Meeting frequency rate is the average number of meetings a person attends in a given period, usually measured per week. It counts how often the calendar pulls someone into a meeting, regardless of how long each one lasts. A person with eighteen meetings a week has a high frequency rate even if every meeting is short, because each one breaks the day and resets their focus.

The simplest way to read it is per person. If a team of ten attends 150 meetings across a week, the frequency rate is 15 meetings per person per week, or three a day. That number tells you how fragmented the working day is. Frequency is deliberately separate from duration. Two people can each spend ten hours a week in meetings, but the person who spends it across twenty short calls has far less usable focus time than the person who spends it across five longer ones.

Frequency matters because the damage from meetings is not only the time inside them. It is the context switching around them. A thirty-minute meeting in the middle of the morning can cost the whole morning, because the work either side never reaches depth. Measuring frequency captures that hidden cost, which a total-hours figure misses entirely, in the same way that watching cycle time reveals delays a simple workload count would hide.

The headline figure is meetings per person per period, which is total meeting attendances divided by headcount. The richer signal comes from how those meetings are distributed across the day and the week, because the same count can fragment a calendar gently or severely. The inputs below are what you need to capture.

1. 1

   Meeting attendances

   Count each meeting a person attends, not the number of distinct meetings on the calendar. A meeting with eight people contributes eight attendances. This is what ties frequency to the actual interruption load on real individuals rather than to the schedule in the abstract.

2. 2

   Period and headcount

   The window you measure over and the number of people you measure across. Per week per person is the most readable unit. A daily figure swings too much with the day of the week, and a monthly one blurs the rhythm that matters.

3. 3

   Distribution across the day

   Where meetings land. Three meetings back to back leave a long clear afternoon. The same three scattered one per hour destroy the whole day. Capturing the gaps between meetings tells you how much focus time the frequency actually leaves behind.

4. 4

   Recurring versus one-off

   How much of the frequency comes from standing series rather than ad hoc calls. Recurring meetings set the floor of the frequency rate, the load that exists every week before anything new is booked, so they are where structural change has to start.

Once you have these, the most useful derived measure is uninterrupted focus blocks per day, which counts how many gaps of, say, two hours or more sit between meetings. A person can have a modest frequency rate and still no focus blocks at all if the meetings are spaced to leave only short gaps. Frequency rate sets the scale of the interruption problem, and the distribution tells you how much that interruption actually costs the work that feeds metrics like sprint velocity.

A metric tree decomposes meeting frequency into the sources that generate it, so you can see whether the calendar is full because of standing meetings, ad hoc calls, or being copied onto meetings that do not need you. Each source has a different owner and a different fix.

The first level splits frequency into recurring meetings, one-off meetings, and optional attendances. Recurring frequency is driven by how many standing series exist and how often each repeats. One-off frequency is driven by how readily people book ad hoc calls instead of resolving things asynchronously. Optional attendances are driven by whether being added to a meeting is treated as a request or an obligation, and whether people feel able to decline. A fourth branch, team size, captures the headcount the rate is divided across, since the same total of attendances spread over more people lowers the rate per person.

This structure lets you diagnose precisely. A high frequency rate driven by recurring series needs a calendar review. The same rate driven by ad hoc calls needs better asynchronous habits. The tree tells you which conversation to have.

A healthy meeting frequency depends heavily on the role. The benchmarks below are weekly meetings per person and assume an individual whose job is mostly producing work rather than coordinating it. Managers and leaders sit far higher by design, because coordination is the work.

A useful companion benchmark is focus blocks per day. Most individual contributors need at least one uninterrupted block of two hours or more each day to do meaningful deep work. If the frequency rate is leaving zero such blocks, the number is too high regardless of how it compares to the role ranges above, because the cost is showing up directly in the work that is not getting done.

Improving frequency means cutting the number of separate interruptions, not just trimming minutes. The levers fall into removing standing meetings, replacing ad hoc calls with asynchronous work, and clustering whatever remains to protect focus.

The metric tree approach to improving frequency starts by finding which source generates the most interruptions. If recurring series dominate, an asynchronous habit change will barely move the number. The fix is the standing-meeting audit.

KPI Tree lets you connect each source to the person who owns it. The number of standing series sits with the team lead who scheduled them. The async resolution rate sits with whoever sets the team working norms. The decline rate on optional invites sits with each individual and the culture around saying no. With RACI ownership on every node, the accountable owner is named, and when the frequency rate climbs for a team the platform pushes the change to that owner so the calendar gets reviewed before fragmentation quietly becomes the norm.

1. 1

   Treating frequency as a proxy for hours

   A low meeting-hours total can still mean a badly fragmented day if those hours are spread across many short calls. Frequency and duration are different problems and need to be read together, never one in place of the other.

2. 2

   Counting meetings, not attendances

   The number of meetings on a shared calendar says nothing about the load on any one person. Count attendances per individual, or the metric describes the schedule rather than the people living in it.

3. 3

   Ignoring distribution

   Two people with identical frequency rates can have completely different days depending on whether their meetings are clustered or scattered. A count with no sense of spacing misses where most of the damage comes from.

4. 4

   Cutting frequency without cutting work

   Removing meetings while leaving the coordination they were doing unaddressed just pushes the work into messages and longer threads. Reduce frequency by moving work to a better channel, not by deleting the channel and hoping.

5. 5

   Applying one benchmark to every role

   A frequency rate that is unhealthy for an individual contributor is normal for a manager. Judging everyone against a single number flags the wrong people and misses the ones whose focus time has genuinely collapsed.