Time management for meeting-heavy roles

Most productivity systems assume a day made of long, contiguous blocks you allocate yourself: a to-do list, a priority matrix, a deep-work block from 9 to 11. That model was already strained before meeting load rose. Executives now spend close to 23 hours a week in meetings on average, up from under 10 hours in the 1960s, according to Harvard Business Review's widely cited analysis of internal calendar data. For product owners, project managers, and other meeting-heavy roles, the shape is similar even without the executive title: a calendar made mostly of other people's time.

The deeper cost isn't the hours themselves, it's what switching between them does to attention. Research out of UC Irvine found that after being interrupted, it takes an average of 23 minutes and 15 seconds to return to the original task. A meeting is a scheduled interruption of everything else you were doing, and a day of eight of them is eight resets, not eight discrete slots. Separately, work by Sophie Leroy at the University of Minnesota describes "attention residue": part of your mind stays stuck on an unfinished task even after you've moved to the next thing, which is exactly the state most people are in when they walk from one meeting straight into another.

Time management advice written for a calendar of blocks doesn't hold up against a calendar of resets. What works instead is treating the meetings as fixed and designing everything else, batching, buffers, and what happens after, around them.

Before changing anything, look at what's actually on the calendar for one representative week. Three questions do most of the work:

• Which meetings are recurring by default rather than by decision? Standing meetings tend to outlive the reason they were created. If you can't state what decision or output the meeting produces, it's a candidate to shorten, merge, or drop.
• Where are the meetings clustered, and where are the gaps? Three isolated 30-minute meetings spread across five days do more damage to focus time than the same three back-to-back on one day, because isolated meetings fragment every day instead of just one.
• What happens in the 30 minutes after each meeting ends? For most meeting-heavy roles this is unaccounted-for time spent on notes, follow-ups, and remembering what was said, and it rarely appears anywhere on the calendar.

That third question is usually the biggest lever, because it's time nobody scheduled and nobody protected.

The least examined time cost in a meeting-heavy week is the reconstruction work that follows each meeting: writing up what was decided, finding the action item mentioned in passing, checking what a stakeholder actually committed to versus what you remember them committing to. None of this shows up as a calendar block, so none of it gets protected, which is exactly why it's the first thing squeezed when the next meeting starts on time and the last one didn't finish its own conversation.

This is also the part of the problem that's most directly solvable with better capture, not better willpower. If a meeting is recorded and transcribed as it happens, the reconstruction work shrinks from "remember and re-type" to "look it up." Earkeep runs continuously in the background, transcribing mic and system audio locally the entire time it's open, so the record already exists by the time the meeting ends. There's no bot to invite and no start/stop to remember, because meetings are defined retroactively by selecting the span they covered, or automatically from a connected calendar. Audio is processed only in memory and never written to disk, and transcripts land as plain files you own outright, so an agent can turn a transcript into a summary or task list in the minute after the meeting rather than the evening after.

The companion guide on surviving a day of back-to-back meetings goes deeper into replacing live note-taking with retroactive capture.

Individually, batching, buffers, defended focus blocks, and better capture are small changes. Together they form a rhythm: meetings cluster instead of fragment, the five minutes between them exist instead of vanishing, focus time reads as unavailable instead of empty, and the write-up after each meeting takes minutes instead of an evening. None of this requires renegotiating your role or your manager's expectations. It's mostly calendar defaults and one better tool for capture.

Two roles get role-specific versions of this rhythm: Earkeep for people managers for the 1:1-heavy week, and Earkeep for product managers for the stakeholder- and discovery-heavy one. The mechanics behind retroactive capture and calendar auto-spans are covered in full on always-on capture and calendar connection.

If that sounds worth five minutes to set up, download Earkeep free for macOS and try it against your next back-to-back day.