Maker vs Manager: How to Protect Deep Work in a Weekly Operating System

I've experienced this pattern firsthand more times than I care to admit. You start the week with clear outcomes, real Rocks with definitions of done. You're excited, focused, ready to ship. Then meetings fragment your attention. Reactive communications fill the gaps. Deep work gets pushed "to later." By Friday, you've been busy all week and completed nothing that mattered.

The problem isn't the outcomes you chose. It's that the calendar was never designed to hold them. An operating system is only as real as the time you protect for shipping. Without that protection, even the best-planned week becomes an exercise in frustration.

The Two Modes of Work

Paul Graham's original essay on this distinction was about engineers versus executives, but I've found it applies much more broadly. Most work falls into two modes: maker mode and manager mode. Understanding which mode you're in, and when, is the foundation of effective time design.

Both modes are necessary. The failure isn't manager mode itself, it's letting manager mode consume all available time. When meetings and messages fill every gap, there's nowhere left for the deep work that produces outcomes. You end up coordinating work without ever doing work.

The Time Protection Rule

In weekly planning, schedule 2-4 deep work blocks before committing to outcomes. This is the fundamental discipline that makes everything else work. If you can't find the blocks, reduce the commitments. A plan without time is a fantasy.

I learned this the hard way. For years, I would commit to outcomes and then try to fit them into whatever time remained after meetings. It rarely worked. Now I invert the process: first I protect the time, then I commit to what the time can hold.

What a Deep Work Block Actually Looks Like

A deep work block is 60-180 minutes of focused time on one outcome. No meetings, no notifications, no "quick questions." You should have a clear start state (what you're beginning with) and end state (what you're producing). Anything shorter than 60 minutes isn't a block, it's a warmup.

The 60-minute minimum is important. It takes about 20 minutes to get into a flow state on complex work. If your block is only 30 minutes, you've just started thinking deeply when it's time to switch contexts. You end up with the cognitive costs of deep work but none of the benefits.

Batching Manager Work

If manager work is unavoidable, and it usually is, batch it. Instead of checking messages throughout the day, have one window for comms. Instead of scattering admin across the week, have one window for admin. Instead of approving things whenever they come in, have one window for review and approval.

The goal is to reduce context switching. Every time you switch from maker mode to manager mode and back, you pay a cognitive tax. That tax compounds throughout the day. By batching, you pay the tax fewer times and preserve more capacity for deep work.

A Weekly Calendar Pattern

Here's a simple pattern I've used successfully across different roles and contexts. You can adapt the specific days, but the structure matters: protect deep work early in the week when energy is highest, batch coordination in the middle, and reserve Friday for shipping and review.

Notice that meetings are pushed later in the week. Monday morning is often when I have the most mental clarity, it would be a waste to spend it in meetings. By the time Thursday arrives, the deep work should be mostly done. That's when coordination and issue-solving make sense.

The Reality of Emergencies

I know what you're thinking: "This sounds great, but my week is full of emergencies." I've been there. The question is whether those emergencies are real or manufactured. Often, things labeled "urgent" can actually wait a few hours until the next comms window.

When genuine emergencies do occur, the operating system helps rather than hinders. You can re-plan honestly because you know what you were supposed to accomplish. You can make conscious trade-offs because you know what you're giving up. The system isn't a fantasy calendar, it's a recovery mechanism that helps you respond to reality without losing all structure.

Limitations

Teams with heavy coordination needs can't eliminate meetings. That's okay, the goal is to protect blocks, not eliminate manager mode entirely. Even roles that are inherently manager-heavy can protect some maker time for the work that requires deep focus.

The harder challenge is organizations where meeting-heavy culture is the norm. If everyone schedules over focus time, individual time protection won't work. This is a systemic issue that requires team-level agreement about when deep work happens.