How to Track Deep Work by Category (And Why the Data Will Surprise You)
June 3, 2026 · 6 min read
Cal Newport's definition of deep work is precise: "Professional activities performed in a state of distraction-free concentration that push your cognitive capabilities to their limit." His argument is that deep work is the activity that produces most of the value in knowledge work — and that most people spend far less time doing it than they think.
The uncomfortable part isn't that people are lazy. It's that people are often genuinely busy — with the wrong things.
Why total hours is a useless metric
"I worked 10 hours today." What does that tell you?
Without knowing what those hours contained, almost nothing. 10 hours of meetings, email, and admin is an exhausting day that may have produced nothing of lasting value. 4 hours of deep work followed by 6 hours of shallow tasks might have been the most productive day of the month.
The number of hours worked doesn't correlate with the quality or value of the output. The type of work does.
This is why time tracking without categories is mostly data noise. You're measuring quantity of presence, not quality of output. It's the equivalent of measuring health by how many hours you spent at the gym — without tracking whether you exercised or just sat on a bench.
The categories that matter
The most useful category system for knowledge work is simple: it should capture whether the time was spent in deep work or not. One way to do it:
Deep Work — tasks requiring sustained concentration that push cognitive capability. Writing, coding, designing, analysis, learning, creating. The work that could only be done in a distraction-free state.
Shallow Work — tasks that are necessary but low-cognitive-demand. Email, scheduling, filling out forms, administrative tasks, routine updates. Valuable, but replicable and interruptible.
Meetings / Collaboration — time spent in synchronous communication. Meetings, calls, pair programming, code reviews where you're the reviewer.
Learning / Reading — consuming information. Not as high-output as deep work, but cognitively demanding and worth tracking separately from shallow tasks.
You can be more granular — separate categories by project, client, or subject area — but these four capture the most important signal: the ratio of deep to shallow.
What your data will likely show
Most people who start tracking by category are surprised by two things:
1. Deep work hours are much lower than expected. People who describe themselves as "working all day" often have 1–2 hours of actual deep work once meetings, email, and interruptions are accounted for. This isn't a failure of discipline — it's often a structural problem with how the day is organized.
2. The shallow work ratio is invisible until it's measured. When you only track total time, the shallow tasks disappear into the total. When you track by category, you can see that 3 hours of your 8-hour day was email and admin. That's a choice — one that's worth making deliberately.
Newport's own practice: tracking deep work hours each day, with a target of 4 hours. He's explicit that this is a hard 4 hours — not the 8 hours at the desk, but the 4 hours of deep, demanding, concentrated work. Measuring that number is what makes the target real.
How category tracking changes behavior
The act of tracking changes the behavior. This is Hawthorne effect, measurement incentive, and accountability all at once.
When you tag every session with a category, you become aware in real time of what kind of work you're doing. Starting a Pomodoro for "email" instead of a flow session for "Deep Work — Writing" is a small act, but it encodes your assessment of the task. Over time you start asking the question before you sit down: is this deep work or not?
That question is more powerful than any time management system.
A few things that typically shift when people start category tracking:
- Meetings get scrutinized. When you can see exactly how many hours per week meetings consume, the cost becomes concrete. That sync that could have been an email gets clearer.
- Deep work gets protected. Knowing you want to hit a deep work target creates an incentive to protect morning hours for it, rather than filling them with email.
- Admin gets batched. Seeing shallow work scattered through the day creates the obvious improvement: batch it. Do all the email in one block, all the admin in another. Preserve the rest for depth.
The stats that tell the real story
Raw session data is useful, but aggregated weekly breakdowns reveal patterns:
- What percentage of your time is deep work vs shallow?
- What time of day are your deepest sessions?
- Which projects get your best hours vs your leftovers?
- Is your deep work ratio increasing over time?
This is the data that lets you optimize at the level that actually matters — not "how do I squeeze 5 more minutes out of my morning," but "how do I restructure my week so deep work happens first, not last."
Getting started
The system doesn't need to be complex. Start with three or four categories that map to your actual work. Tag every session. Look at your weekly breakdown at the end of the week.
What you'll see in the first week is a baseline: this is where your time actually goes, without any optimization. From that baseline, one or two changes usually become obvious without any analysis — you can see them in the data.
Track the ratio, not the total. Improve the ratio.
FocusSharp lets you tag every session by category and see your breakdown over time — today, this week, or the last 30 days. Track your deep work hours — free, no account required.