BookYol

Concept

Shallow Work

Shallow work is Cal Newport's name for logistical tasks that are not cognitively demanding, such as email, scheduling and status updates, which are often done while distracted, create little new value and are easy for someone else to replicate.

Newport introduced the term in Deep Work (2016) as the counterpart to deep work, and the pairing is the point: the two compete for the same hours. Shallow work is not useless. Answering a client, booking a meeting room and filling in a form keep an organisation running, and some of it cannot be avoided. The problem is proportion. Shallow tasks are easy to start, give a quick sense of completion and arrive constantly, so without a deliberate limit they expand to fill the day, and the hard work that builds a career and creates new value gets whatever is left. Newport offers a simple test for telling the two apart: ask how long it would take to train a smart recent graduate, with no special training in your field, to do the task. The shorter the training, the shallower the task. The test helps because it moves the question from how busy a task feels to how much skill it actually uses. Newport's advice is not to eliminate shallow work but to contain it: batch it into blocks of its own, and protect the remaining hours for depth.

A real-life example

Hakan, a lawyer at a firm in Konya, logged one ordinary Tuesday in fifteen-minute rows. Of nine hours, fewer than two went to the appeal he was actually being paid to draft; the rest was email, calendar juggling, a status call and two forms. Nothing on the list was pointless. But when he asked how long a bright trainee would need to learn each item, almost every answer came out in days.

How to use it

  1. 1Log one ordinary workday in half-hour rows and mark each row deep or shallow; the ratio, not the feeling, is your starting point.
  2. 2For every shallow item, ask how long a smart graduate would need to learn it; the shorter the answer, the stronger the case for batching it or handing it off.
  3. 3Gather tomorrow's shallow tasks into one or two fixed blocks, so they stop breaking into the hours you have kept for depth.