Keep team meetings under 12% of work hours

Cap the team at 12 percent of paid hours

A recurring invite lands before you think: no owner, no decision, no end. A no-owner invite is the easiest to miss and the hardest to justify. Count it as paid time, because a full calendar is a recurring cost, not a badge of activity. Set the cap before you audit.

Audit a representative month of team calendars. Use a month that includes normal project work, not a holiday week or a launch week. Count every scheduled meeting hour, including calls, short check-ins, and one-to-ones, against paid hours, not remembered hours. You should end with one number: the team's meeting load as a percentage of the workweek. If it is above the cap, you are paying for meetings that may not be earning their keep.

A Norwegian worker sample in NBER working paper 35706, from a U.S. economics research group, showed that meetings used 12 percent of work hours on average and 14 percent of firm wage bills. Use 12 percent as the time cap and 14 percent as the money warning.

Sixty percent of workers who regularly have meetings spend more than one hour per workday in meetings. A team already above the cap has a recurring pattern, not a bad week.

Price standing invites in salary, not room cost

Price every standing invite in salary terms. The cost is paid time, not coffee, not the room, not the calendar color. Use the salary of each person on the invite, because that is the resource being consumed. Put a cost column next to every invite.

Say a salary is $75,000; the annual meeting budget is about $9,000. That gives you a number you can defend in a planning conversation, and it makes the choice visible: this invite is spending a share of someone's salary.

Then ask what each recurring invite is buying. Sort each invite: status updates are reports, decision meetings are choices, working sessions are builds. An invite that cannot name the decision, the blocker, or the upward connection it creates is a tax on focus. In a Resume Now survey, 64% of workers reported that at most half of their meetings were productive.

Cancel only what fails the survival test

Cancel the invite that fails the test. Keep a recurring meeting only if it decides, unblocks, or connects upward. Otherwise cancel, batch, or move it async. The calendar should have fewer recurring blocks and a written reason for each survivor.

Do not cancel everything at once. A dramatic cleanup makes you look difficult and pushes the team into side channels. Tell the team the cap, not just the cut. Cut the lowest-value recurring invites first, give short notice, and offer a replacement path.

When you cancel, send a short note: what you are removing, why, and what replaces it. 'I am removing the recurring status call. Please post updates in the project doc. Book a short slot with me when a decision is needed.' It is direct, not difficult.

Batch similar conversations into a recurring block, then choose the replacement:

• Post a written update or shared doc for status.
• Book a short decision slot with a named owner.
• Set a periodic review, an end date, and a stop rule for project work.

Protect upward connections, not meeting volume

Protect the meetings that create upward growth interactions. A positive association ran between how often and how intensely workers met, and their subsequent wage growth. Wage growth was stronger when workers interacted with more senior colleagues. In an activity comparison, meeting time was the strongest wage-growth predictor.

The relationship is correlational, not causal, so extra meetings would not automatically produce a raise. Meet in the right places, not more. Those places are decisions that move the team, blockers that stop delivery, and upward connections that expose work to senior judgment.

Make upward interactions visible. Send a senior colleague a short written brief before the meeting when context is needed. Ask for a decision in writing first when the meeting is only to hear it. Keep the meeting when it is to shape the work. The point is a short brief before the meeting, not a longer meeting.

Run a regular calendar audit. Reprice the surviving invites against the cap. When the load creeps back above the cap, remove a recurring invite before adding another.