Not good work versus bad work. Work that needs your full attention to produce value, versus work that does not — and how much of each your day can hold.
Deep work creates new value; shallow work keeps things running. Deep work is demanding, focused effort that is hard to replicate — writing, designing, solving a hard problem. Shallow work is logistical and can be done while distracted — email, scheduling, most meetings. You need both, but shallow work expands to fill any day you do not defend.
| Deep work | Shallow work | |
|---|---|---|
| Attention needed | Full, uninterrupted | Partial, interruptible |
| Examples | Writing, coding, strategy, studying | Email, scheduling, status updates, admin |
| Value created | High, hard to replicate | Low to moderate, easy to replicate |
| How it feels | Effortful, often satisfying | Easy, busy, often draining |
| Daily capacity | About 1–4 hours | Effectively unlimited |
| Effect of interruption | Severe — high restart cost | Mild |
The practical move is batching. Put deep work in your best hours, in protected blocks, and push shallow work into one or two windows later in the day. Answering email twice a day instead of forty times does not make you less responsive in any way that matters — it makes you available for the work that does.
Shallow work is not the enemy. Unscheduled shallow work is.
Answering routine email and messages, scheduling, filling in forms, most status meetings, light admin and reformatting documents — tasks that need doing but not your full attention.
Most people manage one to four hours of genuine deep work. Beginners often start nearer one hour; four hours is a commonly cited ceiling even for experienced practitioners.
No — much of it is necessary. The problem is when it fills the hours you would otherwise use for deep work. Batching it into fixed windows keeps it in its place.