Where it sits
A useful and slightly uncomfortable test to run on a day's calendar.
Tell it apart
Opposite of Shallow Work
What it doesn't mean
The criterion is replicability and cognitive demand — shallow tasks require minimal training and can be performed by almost anyone. Necessary, urgent and consequential work can still be shallow, and calling it unimportant is a misreading that makes the framework useless.
The opposite. Shallow work FEELS PRODUCTIVE because it is easy, socially engaging and generates visible completions — which is precisely why it crowds out deep work rather than being pushed aside by it.
What it really means
The common misreading is that shallow means unimportant. It doesn't, and the mistake ruins the framework, because it turns a diagnostic into a value judgement about your colleagues' work.
The actual criterion is replicability and cognitive demand. Shallow tasks require minimal training and can be performed by almost anyone. That says nothing about whether they matter. Approving a payment, forwarding the right message to the right person, confirming a date — these can be urgent, consequential and necessary, and still shallow.
What the label actually tests is: does this specific task require you?
The more interesting claim, and the one that explains why nothing changes when people resolve to focus more, is about how shallow work feels.
The intuitive story is that shallow work is drudgery we would escape if we could. Newport's argument is the reverse. Shallow work is easy, socially engaging, and produces immediate visible completions — a cleared inbox, a resolved thread, a person thanking you. It is, moment to moment, more rewarding than deep work, which produces nothing observable for hours and often feels like failing.
So shallow work does not crowd out deep work by being demanding. It crowds it out by being more pleasant and immediately validated.
Underneath both sits the structural observation: knowledge work lacks a culture of systematic improvement. Manufacturing spent a century measuring and redesigning how work is done. Knowledge work largely doesn't — there is no equivalent of a production line study for how a Tuesday gets spent. So the default arrangement persists, and the default arrangement favours whatever is easiest to start.
Which, as Newport noted in 2012, is why a veteran knowledge worker will spend most of the day answering email, and describe the day as busy.
Where it comes from
of attention depth
English
'Shallow' describes the attention the task demands, not the task's importance. A great deal of shallow work is mandatory, and some of it is the most consequential thing you do all week.
- 21 November 2012
Cal Newport publishes the deep and shallow distinction, observing that a veteran knowledge worker will spend most of the day answering email.
- 5 January 2016
Deep Work formalises the pair.
In real life
- Clearing forty emails, rescheduling two meetings and filling in an expenses form: a full, busy morning, all of it shallow work.
- Approving an urgent payment takes thirty seconds and almost no thought. It matters — and it is still shallow work.
- 'I was flat out all day and got nothing real done.' 'Shallow work. The inbox ate you.'
Questions
Q01What counts as shallow work?
Logistical tasks needing little training, easily replicated, often performed while distracted. Email is the archetype, but so are most status updates, most scheduling and most approvals.
Q02Is shallow work avoidable?
Not entirely, and the framework does not claim it should be. The argument is about ratio and scheduling, not elimination.
Q03Why does it dominate?
Because it is easy and socially engaging, so it feels like productivity — and because it produces visible completions, which deep work rarely does until the very end.
Sources
- Knowledge Workers are Bad at Working (21 November 2012) — Cal Newport.
- Deep Work — Cal Newport.
- work (etymology) — Wiktionary.