We Spend Too Much Time Managing Work Instead of Doing It

Most knowledge workers spend their days feeling busy without actually moving anything forward. I think this is what’s really going on, and what you can do about it.

Most of us are working harder than ever and somehow have less to show for it.

That sounds dramatic, but I don’t think it is. It is just the normal texture of a lot of modern work now. You finish the day tired. You answered the messages, joined the meetings, updated the tasks, moved the cards, checked the dashboards, and kept the machine alive.

Then someone asks what you actually made today, and the answer gets harder to explain.

At first, it’s tempting to blame laziness. But I don’t think that’s right. Most people I know are not lazy. They’re overloaded, responsive, and constantly switching contexts. Then you might blame apathy, but that doesn’t quite fit either. Most people do care about doing good work.

The deeper problem is that we’ve accidentally built our workdays around managing work instead of doing it.

You start Monday with a decent amount of energy. By noon, you’ve reorganized your tasks twice, sat through two status meetings that mostly repeated other conversations, and replied to dozens of Slack or Teams messages. You were busy in the technical sense. You were moving, reacting, coordinating.

But the work itself — the thing that needed judgment, patience, and sustained attention — barely got touched.

I think this is the default mode for a lot of knowledge work now. We’ve been inside it long enough that it no longer feels strange.

Shallow work keeps winning

Cal Newport wrote about this in Deep Work back in 2016, and the idea has only become more relevant. His basic distinction is simple: shallow work is email, meetings, coordination, admin, status updates, and all the small pieces of professional maintenance. Deep work is the cognitively demanding work that creates real value.

The problem is that shallow work is easier to schedule, easier to see, and easier to measure.

Deep work is not like that. It often looks quiet from the outside. You can spend three hours thinking through a hard problem and have very little visible proof until the solution finally clicks. That makes it awkward in a work culture that wants constant evidence of activity.

So shallow work expands. It fills the open space. It gives everyone a sense that things are moving.

And the pile has only gotten bigger. McKinsey has estimated that the average interaction worker spends around 28% of the workweek managing email. That’s roughly 11 hours a week before you add Slack, Teams, async standups, project management tools, and the quiet tax of finding information across all of them.

The time tracking problem nobody talks about

The hard part is that most of us have a surprisingly inaccurate picture of where our time goes.

This is not a character flaw. It is just how memory works. Research on retrospective time estimation suggests that we are not especially good at reconstructing duration after the fact. We remember the obvious events and compress the rest.

The 20 minutes spent searching for a file disappears. So does the 15-minute “quick look” at an industry article. So does the fog after a meeting, when you are technically back at your desk but not really back inside the work yet.

None of this shows up cleanly when you try to account for the day from memory.

That’s the useful argument for automatic time tracking. Not surveillance. Not turning yourself into a spreadsheet. Just replacing a vague story about the day with something closer to evidence.

Some tools, like Memtime, reconstruct activity data in the background so you can compare what you thought happened with what actually happened. The point is not to monitor every minute. The point is to notice the gap between intention and reality.

Why busyness feels so convincing

I don’t think this is purely a time tracking problem, or a willpower problem. The modern work environment is set up to push us toward busywork.

• Coordination looks like work. When you send a message, update a status, or comment on a doc, there is visible proof of activity. Deep work often lacks that proof until much later. So we gravitate toward the visible stuff, even when it is not the valuable stuff.
• Notifications are designed to feel urgent. A Slack or Teams ping feels like a tiny emergency. Most of the time it isn’t, but responding quickly is socially rewarded. It makes you feel useful. Full focus does not give the same immediate feedback.
• Most tools measure activity, not output. Email, chat, and project management tools are very good at counting movement: messages sent, comments added, tickets updated. They are worse at measuring whether meaningful work actually moved forward.

The real cost is cognitive

It is easy to describe this as a time problem. Too many meetings. Too many messages. Too much coordination.

That’s true, but it misses the deeper cost.

Focused work has a warm-up period. Your brain has to reload the problem, the constraints, the relevant details, and the half-formed ideas you were holding in mind. That state is fragile. It does not survive constant interruption very well.

Gloria Mark’s research at UC Irvine has shown that interrupted work comes with real costs: more stress, more frustration, more time pressure, and more effort. One widely cited finding from her research is that it can take around 23 minutes to return to a task after an interruption.

That number sounds extreme until you watch yourself work for a day. A message takes 30 seconds to answer, but the recovery is not 30 seconds. The damage is in the return. Stack enough interruptions together and the day becomes one long state of leaving and coming back.

This reminds me of Nassim Taleb’s idea of fragility: some things are harmed by disorder, shocks, and volatility. Deep work is fragile in exactly this way. It doesn’t need much to break. A few badly placed meetings, a few notifications, a few context switches, and the conditions that made the work possible are gone.

What seems to help

There is no perfect solution to this, especially if you work inside a company with its own meeting culture and expectations around responsiveness.

But a few things do seem to help.

The first is getting more accurate about where your time actually goes. You cannot improve a workday you are misremembering. Whether you use a notebook, calendar audit, or automatic time tracking, the useful move is the same: compare your story of the day with the day itself.

After that, the biggest gains usually come from subtraction rather than optimization.

• Fewer communication channels.
• Email checked at specific times instead of continuously.
• Longer blocks for work that actually requires thinking.
• Fewer meetings that exist only because nobody wants to decide asynchronously.
• Fewer decisions about what to do next.

The goal is not to build a perfect productivity system. That can become another form of managing work. The goal is to spend less mental energy arranging the work and more of it doing the work.

If you want a better framework for this, I think the books that change how you think about work are more useful than another app stack. Tools can help, but only after the underlying problem is clear.

Make peace with the truth

Most knowledge workers are not failing because they lack discipline. They are working inside systems that reward the appearance of progress more reliably than progress itself.

Companies measure the wrong things. Tools reward the wrong behaviors. The default workday gets chopped into pieces too small for the work that matters.

You may not be able to fix all of that. You probably can’t change the meeting culture by yourself, or remove the expectation that everyone should be available all the time.

But you can get honest about where your time goes. You can protect a few hours before the day gets eaten. You can remove some of the channels, rituals, and habits that make work feel productive while keeping the real work just out of reach.

That is a small step, but it is not a cosmetic one.

Because once you can see the difference between managing work and doing it, it becomes much harder to pretend they are the same thing.