Calendar Tetris is not a personal problem. It is a diagnostic about your org

A senior product manager opens her calendar on Sunday evening to plan the week. Forty-two meeting invites. Eighteen of them recurring. Three back-to-back blocks of 90 minutes or more. One untouched 30-minute lunch on Wednesday, and even that one has a tentative invite layered on top of it.

She thinks this is her problem. She has a productivity book on her nightstand. She's tried calendar blocking, the Pomodoro technique, the "three priorities a day" approach. Some weeks she gets two clean hours of focus time. Most weeks she doesn't.

It is not her problem. It is her org's problem, and she's the symptom.

The average knowledge worker in 2026 attends 21.7 meetings a week and spends 392 hours a year in them. That number is not load. It is structure. It tells you that the org has organised itself such that decisions, alignment, and information flow all route through synchronous co-presence. The 392 hours a year is the cost of that structural choice, and the people whose calendars are most booked aren't the ones with the worst time management. They're the ones whose presence the org has made load-bearing.

There are three structural reasons an org defaults to meetings for everything, and each one points to a different fix.

The first is that decisions need explicit authorisation, and the org hasn't written down who decides what. When a team isn't sure who has the call, every decision goes to a meeting because the meeting is where the authority resolves itself. The fix is decision rights, written down, distributed: who decides on engineering priorities, who decides on hiring, who decides on customer-facing copy, by name. The decision-rights doc is boring to write and saves hundreds of meeting-hours a quarter.

The second is that the org doesn't trust async written communication, often because nobody reads what gets written. So every important update becomes a meeting, because meetings get attendance and docs don't. The fix here is dual: shorter writing (three paragraphs, not three pages) and a culture norm that says "if it's in the channel, you read it." Teams that successfully cut meetings almost always invest in writing as a craft first.

The third is that the manager has become the only person who holds the full picture, and the org keeps her in every meeting to keep the picture coherent. This is the most expensive failure mode, because it scales linearly with how senior the person is, and it gets worse as the org grows. The fix is structural: distribute the picture. The leads run their slices. The manager reads the synthesised version. The all-hands becomes a quarterly briefing, not a weekly recap.

The diagnostic is simple. If a manager looks at her week and sees more than 25 hours of meetings, the question is not "how do I block more time." The question is "which of these three structural issues is producing this calendar." The answer points to a fix that is bigger than a personal habit change, and that is the news, not the personal failing.

If your week is stacked, the test is to remove yourself from three recurring meetings this week and watch what happens. If the meetings function without you, you weren't load-bearing. If they grind to a halt, the org has organised around your presence, and the next conversation is structural.