You will be able to tell deep from shallow work in your role and explain why shallow work tends to take over.
Think of the last time you produced something at work you were proud of. A proposal that won the client, a piece of analysis that changed a decision, code that worked first time in production. Now think about the conditions. Chances are you weren't answering chat messages every four minutes while you did it. You probably had a stretch of time, maybe early in the morning or late at night, when nobody needed you.
That kind of work has a name, and it tends to lose out to everything else in a working day. This lesson explains what it is and why it gets squeezed.
Cal Newport, a computer science professor at Georgetown University, wrote Deep Work in 2016. He defines deep work as professional activity done in a state of distraction-free concentration that pushes your thinking to its limit. It produces something of value, improves your skill, and is hard for someone else to replicate. Think of the strategy section of a proposal, the design of a new system, an analysis of why sales fell in one region, or the first weeks of learning a difficult skill.
He contrasts it with shallow work: logistical tasks that do not need much concentration, are often done while distracted, and are easy to replicate. Booking a meeting room is shallow work. So are routine email replies, claim forms, tracker updates and the status call where you mostly listen.
Shallow work is not bad, and much of it has to be done. Somebody has to book the room and reply to the client. The question Newport asks is about proportion: how much of your week goes to each, and whether the deep share is enough for the outcomes your role is judged on. For most knowledge workers, those outcomes depend heavily on deep work, while the day is mostly filled with shallow work.
Roles differ. A receptionist or a customer service officer may spend most of the day on work that looks shallow by this definition, and that is the job. Even then, there is usually some deep work in it, such as improving a process or learning a system properly, and it tends to be the work that leads somewhere.
If deep work matters so much, why does shallow work take over? Three reasons come up again and again.
Shallow work is visible. When you reply quickly, colleagues see your green status on Teams, your fast answer on WhatsApp and your name all over the email thread, whereas two hours of quiet thinking leaves no trace until the result appears, sometimes days later. Newport argues that in many workplaces, where it is hard to measure what someone produces, people fall back on looking busy as a stand-in for being productive.
Shallow work is quick to finish. Each email answered gives a small sense of progress. Deep work is the opposite: it is slow, uncertain and often uncomfortable in the first half hour. Given the choice between a task you can finish in two minutes and one that might take two hours, most people pick the two-minute task, and then the next one.
Shallow work is also what other people ask about. Your manager wants to know whether you replied to the client, and a colleague follows up on the form, but nobody chases the deep work until it is already late. This is the important but not urgent problem from lesson 1.1, Busy is not the same as productive, seen from another angle.
There is one more force at work. In 1955 the British historian C. Northcote Parkinson published an essay in The Economist that opened with a line now known as Parkinson's law: work expands so as to fill the time available for its completion. He wrote it partly as satire about government offices, but the observation has stuck because people recognise it.
Shallow work is especially prone to this. Give email an hour and it will fill the hour, and give it the whole day and it will fill that too. If you don't set limits, it takes whatever is free, and deep work gets the leftovers. That is one reason lesson 3.3 had you put messages into blocks: a 30-minute block puts a ceiling on it.
The same law works in the other direction. A clear, protected two-hour block for a demanding task often produces more than a vague "work on it today", because the limit concentrates effort.
Priya looked at her time map from lesson 1.4 with this in mind. The campaign brief and her analytics course were deep. Most of her other hours, including email, chat, approvals and many of the meetings, were shallow. The deep share of her week was around 8 hours out of 45. She hadn't thought of her job as mostly shallow, and that number surprised her.
Marcus found a similar pattern, with one difference. Some of his "shallow" driver calls were really problem-solving that needed full attention. He decided to label those deep when they involved working out the cause of a late delivery, and shallow when they were simple rescheduling.
You don't need a precise figure. A rough share, deep against shallow, is enough to show whether the work your role is judged on is getting the time it needs. Go back to your own time map and label each line, then estimate what share of your week was deep.
Label each item on your weekly time map as deep or shallow and estimate the share of your week that was deep.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).