Batch shallow work outside your peak hours, not throughout the day

Why This Is a Rule

Shallow work — email, Slack, administrative tasks, routine meetings — doesn't require peak cognitive capacity. But when distributed throughout the day, it fragments your peak hours into unusable 30-minute slots between interruptions. Each context switch from deep to shallow work costs 15-25 minutes of attention residue (Leroy, 2009), so even a "quick 5-minute email check" during a deep work block actually costs 20-30 minutes of productive capacity.

Batching shallow work into dedicated blocks outside your biological prime time solves both problems: it protects your peak hours for deep work, and it makes shallow work more efficient (batched email processing is faster than responding to each email individually throughout the day).

The key insight is that shallow work during peak hours is a double waste — you're using high-quality cognitive time on low-quality cognitive tasks while simultaneously fragmenting the remaining peak time with context switches.

When This Fires

• Planning your daily or weekly schedule
• Deciding when to check email, Slack, or other communication tools
• Scheduling routine meetings you have control over
• Any time you notice shallow work creeping into your peak hours

Common Failure Mode

Checking email "just once" during your deep work block. The check itself takes 2 minutes, but the attention residue — the unresolved email sitting in your working memory while you try to return to deep work — costs 15-25 minutes. Three "quick checks" during a 3-hour peak window can destroy 60-75 minutes of peak cognitive capacity. The batch approach eliminates this entirely by confining all email to non-peak blocks.

The Protocol

(1) Identify your biological prime time (see Measure your biological prime time with hourly ratings over 10 workdays). (2) List all recurring shallow work: email, Slack, administrative tasks, status updates, routine meetings. (3) Schedule two shallow work blocks — one before and one after your peak hours. (4) Move all shallow work into these blocks. (5) During peak hours, close email, set Slack to Do Not Disturb, and work only on deep tasks. The shallow work will still get done — just during hours where your brain doesn't have better things to do.