Ask any knowledge worker where their time goes and you'll get a vague, frustrated answer: "meetings, basically all of it." Ask them to name the specific meetings eating their week and most people can list two or three, the ones that annoyed them recently, and nothing else. The rest of the damage is invisible, spread across a dozen smaller things that never individually felt worth complaining about.
That gap between how full a calendar feels and what it's actually full of is the reason most attempts to "get more focus time" fail before they start. You can't fix a problem you can't see clearly, and most people are trying to fix a feeling instead of a measured reality. The fix is a specific, one-hour exercise: a focus audit. Here is exactly how to run one on your own calendar this week.
Step 1: Pull your real calendar history, not your memory of it
Export or screenshot your last four full weeks of calendar entries. Four weeks matters more than it sounds like it should, because any single week gets distorted by something unusual: a conference, a product launch, someone's vacation coverage. Four weeks smooths that out and gives you a picture of your actual normal, not your best or worst week.
Most calendar tools let you export as .ics or CSV from settings. If yours doesn't make that easy, screenshots of each week view work fine. You're not building a database, you're building a list you can look at once.
Step 2: Tag every single entry into one of five buckets
This is the part people want to skip, and it's the part that makes the exercise work. Go through every calendar entry from the last four weeks, no exceptions, and tag it with one of these:
Deep work. Uninterrupted blocks of 45 minutes or more, no other participants, actual thinking, writing, building, or analysis work.
Necessary coordination. Meetings where a real decision required multiple people synchronously, and the decision genuinely couldn't have been made over a message or a shared document.
Status theater. Meetings that exist to report information that could have been a written update, a dashboard, or a two-line message instead.
Recurring by default. Anything on a repeat schedule where you can't immediately state a current reason it still needs to exist.
Reactive and unplanned. Ad hoc calls, "got a minute?" pings that turned into 40 minutes, walk-up interruptions that weren't on the calendar at all until they happened.
Be honest and specific. A meeting doesn't get to be "necessary coordination" just because it involves other people, it has to have actually required a live conversation to reach a decision or resolve something that a document couldn't.
Tagging four weeks of a typical calendar takes 30 to 45 minutes. That's the whole cost of the exercise, and it's the highest-leverage half hour most people can spend on their own working life.
Step 3: Add up the hours, per bucket, per week, then average
Total each bucket for each of the four weeks and divide by four. This is your baseline, and it will very likely surprise you. A common pattern for someone in a meeting-heavy corporate role looks something like this:
- Deep work: 4 to 8 hours a week
- Necessary coordination: 5 to 8 hours a week
- Status theater: 4 to 7 hours a week
- Recurring by default: 3 to 6 hours a week
- Reactive and unplanned: 4 to 9 hours a week
If your deep work number lands under 10 hours a week, that's two hours a day or less of genuinely uninterrupted work time, in a role where deep, uninterrupted thinking is presumably a large part of why you were hired. That's not a personal failing and it's not something more discipline fixes. It's a structural fact about where your hours are currently defaulting to, and now you have the specific number instead of a vague feeling.
Step 4: Calculate your protection budget
Add up status theater, plus recurring-by-default, plus half of reactive and unplanned. This total is your realistic protection budget, the hours you can plausibly reclaim without needing to change your job, your team, or anyone's permission to exist. For most people this lands somewhere between 6 and 14 hours a week.
Write that number down somewhere you'll actually see again. It's the number that turns "I wish I had more focus time" into a specific, defensible target, and it's the number that makes the next, harder step, actually proposing changes to specific recurring meetings, feel worth the mild discomfort of asking.
What the audit gives you that a feeling never will
The value of this exercise isn't the audit itself, it's what it makes possible afterward. A vague sense that "I have too many meetings" is easy for other people, and for yourself, to wave off. A specific number, seven hours a week going to meetings you can't articulate a current purpose for, is much harder to argue with, including in your own head at 11 p.m. when you're trying to talk yourself out of finally sending that "can we cancel this recurring sync" message.
Run the audit this week, before you try to change anything. The measurement comes first. Everything you do after it, deciding which meetings to cut or shrink, building a calendar structure that actually protects the time you get back, having the specific conversations that make it stick, only works if it's aimed at real numbers instead of a general feeling that your week is too full.
If you want the complete system for what comes after the audit, including which meetings are worth challenging, exactly what to say when you propose cutting or shrinking one, and how to build a calendar structure that survives contact with other people's booking habits, I wrote a full guide that walks through all of it step by step: https://manggaleh.gumroad.com/l/ngpky.
Disclosure: this article links to my own paid ebook on the same topic.
