Question
What is meeting fragmentation?
Quick Answer
Managers and makers operate on fundamentally incompatible time schedules — and most knowledge workers live in both modes without recognizing the structural conflict.
Example: A team lead blocks Tuesday morning for deep architecture work. At 9:15, a product manager drops a 30-minute sync on her calendar at 10:30. From the PM's perspective, it's a trivial request — one slot among many. From the team lead's perspective, the four-hour creative block is now two fragments of 75 and 135 minutes. The architecture work doesn't happen. Not because she's lazy, not because the meeting was unnecessary, but because two incompatible time systems collided and the manager schedule won by default.
This concept is part of Time Systems in the How to Think curriculum.
Learn more in these lessons
Go beyond the answer
This topic is part of Build Systems Beyond Yourself — a guided sequence of 20 lessons.
After completing this path you will have documented your key workflows, identified where YOU are the bottleneck (your bus factor is currently 1), built delegation criteria for systems, tools, habits, and people, and begun the identity shift that makes letting go feel like freedom instead of failure — because operational excellence means your systems run reliably without your constant attention.
Start the path →