Drain the shallows

Aggressively limit and batch low-value shallow work so it doesn’t crowd out deep work.

Why it works

Shallow work — logistical, low-cognitive tasks — expands to fill available time and feels productive while displacing the deep work that actually creates value. Quantifying how much shallow work a role truly requires, and batching the rest into bounded windows, caps its footprint so it cannot quietly consume the hours that should go to demanding cognitive work.

How to do it

1. Estimate the realistic depth ratio your role needs and budget shallow work to fit it.
2. Batch email and admin into defined windows instead of doing them continuously.
3. Question or decline shallow commitments that crowd out your deep work blocks.

Evidence

A practitioner prioritization strategy consistent with task-switching costs and with the general finding that frequent interruption from administrative work fragments attention. The specific "depth ratio" budgeting is Newport’s heuristic rather than a tested metric. Mark et al.’s interrupted-work study grounds the interruption cost empirically: fragmenting work with shallow tasks raises stress and effort even when the work still gets done. (mechanistic)

How much shallow work is truly optional varies enormously by role; the practice is about being deliberate, not about eliminating all administrative work.

Sources

• Mark, G., Gudith, D., & Klocke, U. (2008). The cost of interrupted work: More speed and stress. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI '08), 107–110.

Common mistake

Confusing busyness with productivity — letting a full day of shallow tasks feel like an accomplishment while the work that matters never gets a block.