What does it mean that manager time versus maker time?

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.

Try this: Audit your last five workdays. For each day, mark every hour as M (manager mode — meetings, coordination, emails, decisions) or K (maker mode — deep work, writing, coding, designing). Then count your longest unbroken K-streak each day. If it's under three hours on most days, your schedule is structurally optimized for manager work regardless of what your job title says. The audit makes the invisible structure visible.