The Cost of Context Switching: The Hidden Inefficiency of Intensive Work

Couple of years ago, I realized I had been working without pauses. Not metaphorically - literally.

My workflow seemed simple and, at the time, efficient:
finish a task, send it for review, immediately pick up the next one.

While working on the new task, comments would arrive on the previous one. I’d switch, fix things, go back. Then new comments - now on the current task. At the same time, the previous task needs to be deployed and monitored.

And switch again.

That was my day. And the next one. And the one after that.

From the outside, it looked like high productivity. I was always busy, tasks were moving, progress was visible. But internally, it felt different - like constant noise. Nothing ever reached a clear “done” state. My focus was fragmented, and my brain never had the chance to fully close a context.

At some point, my CTO noticed and asked a simple question:
“Why are you working like this?”

My answer was honest:
I felt that if I didn’t pick up a new task while waiting for a review, I was wasting time.
That “waiting” was inefficient.
That I had to stay fully utilized.

He saw it differently:
“You’re not saving time. You’re trading it for constant context switching. That’s not sustainable.”

Then came a surprisingly simple suggestion:
“Don’t start a new task. Take a break. Go for a walk. Make tea.”

We also introduced WIP limits.

At first, it felt counterintuitive.
Not picking up the next task?
Stopping on purpose?

But that’s where the shift happened.

When the number of active tasks is limited, the constant switching disappears. Focus returns. Tasks actually get finished instead of endlessly circulating between states. And interestingly, overall speed doesn’t drop - it stabilizes.

The key insight for me was this:
being constantly busy is not the same as being effective.

Sometimes, it’s just a sign of overload.

Takeaway:
If you’re always “in progress” but never stepping out of it,
that’s not productivity - it’s a system that will eventually lead to burnout.