Separating deep work from shallow work

Protect distinct blocks for cognitively demanding work, separate from logistics.

Why it works

Deep, demanding work requires sustained, uninterrupted attention that fragments instantly when interleaved with email and small tasks. Separating them gives cognitively heavy work a clean runway, while shallow tasks — which tolerate interruption — are batched where they do no damage.

How to do it

1. Label each task as deep (high-concentration) or shallow (logistical).
2. Schedule deep blocks at your peak-energy hours, free of notifications.
3. Batch shallow tasks into one or two dedicated windows.
4. Cap total shallow time so it doesn’t crowd out deep work.

Evidence

The deep/shallow distinction rests on documented switch costs and attention residue: interleaving demanding and trivial work degrades the demanding work disproportionately. (observational)

The "deep work" framing is a popularization; the evidence is for switch costs generally, not for a specific deep-work protocol.

Sources

• Newport (2016), Deep Work (synthesis of attention and performance research)
• Leroy (2009), attention residue, Organizational Behavior and Human Decision Processes

Common mistake

Scheduling deep work but leaving notifications on, so the protected block is still shredded by pings the protection was meant to exclude.