Slacking Off Well Can Boost Your Performance: The Hidden Efficiency of Workplace Downtime

That day I sat in front of my computer all day, attended four meetings, replied to dozens of messages, and even pushed a few commits.

But when I brushed my teeth that night and reflected on the day, only two words came to mind: spinning wheels.

It wasn't that I wasn't busy; I just wasn't using my brain. It wasn't that I didn't want to work; I simply couldn't.

All afternoon, I pretended to be online on Slack while frantically Alt+Tab-ing between Chrome and VSCode, feigning research while my mind had long drifted away.

I used to think that was slacking off.

It wasn't until a later one-on-one, when my manager asked why I seemed to be in good shape lately—my proposals were clear and my reactions quick—that I realized my so-called "slacking off" was actually a subtle form of self-regulation.

We haven't stopped trying. We're just trying, in an undisturbed way, to regain our own rhythm.

We habitually view slacking off as the opposite of efficiency.

But I increasingly feel that truly smart slacking off is a recovery mechanism, a hidden time-management skill.

Especially today, when remote collaboration has become the norm and tasks are broken into ever smaller pieces, if we don't proactively carve out breathing room for ourselves, we'll be dragged along by pings, standups, and upstream and downstream pressure.

Those who slack off well not only live longer but also go further.

My "scientific evolution of slacking off" 😄 probably started with these things:

At 8:30 in the morning, I log on half an hour early, before the message bombardment begins, and tackle the two tasks that require the most brainpower: refactoring the interface logic of a module, or writing a piece of complex data-processing code. That's my clearest and quietest window.

Once everyone is online, messages start pouring in like rain. I don't reply immediately. I know this is my free zone.

At that moment, I might be reading a technical blog on database optimization, cleaning up my script library, or opening an architecture sketch I hadn't had time to organize, comparing it to see if it can be simplified further.

No one says I'm doing something else. Because the code I need to write and the PRs I need to submit are already done during my high-energy window.

Slacking off isn't about delaying delivery; it's about actively adjusting my mental pacing.

I've tried not doing this.

Back then, I'd start replying to Slack messages as soon as I logged on, answering everything immediately. The problem was, by the time I could finally sit down to write code, it was already 4 p.m., my brain was mush, and there was no logic to speak of.

The result: all messages answered, but my own backlog untouched.

So I started doing the opposite: finish output first, then handle input.

Once this rhythm is established, it's like adding a cache layer to the human brain: you don't have to respond to the outside world every second, but each step moves you more steadily forward on the parts you're truly responsible for.

Some say, "Isn't that too utilitarian?"

But I believe slacking off isn't utilitarian; it's self-rescue.

Our generation of engineers is too good at looking busy.

We can rattle off a bunch of updates in standup (it's all acting, really), and check off boxes in Jira.

But if you ask me: which core module did I actually advance this week, which key performance bottleneck did I solve—only those few dozen lines of core code written while clear-headed count.

So I no longer feel guilty about slacking off.

For example, some slacking off looks like debugging, but I'm actually setting up a local playground to reproduce an edge case from a week ago.

Some slacking off is muting a meeting to listen to requirements while organizing my own utility functions.

Some slacking off is pretending to look for documentation while testing a lesser-known command in the terminal to run data validation more efficiently.

None of this is avoidance; it's laying the groundwork for my next deep output.

Of course, the most important prerequisite is: you must be able to deliver reliably first.

Those who can truly slack off are often those who have already gained the initiative. They can clearly distinguish what truly requires their own hands, what can be delayed, waited on, or even skipped without anyone dying.

Once you've finished the most important things—especially the parts your boss cares about most, the highest-priority items—no one will question where the rest of your time went. Because the results speak for themselves.

Once in an online meeting, I turned on my camera but pointed it at an idle laptop.

I was actually in the kitchen washing cups with Bluetooth earbuds on, listening to the requirements while my mind replayed the service-splitting plan I'd written that morning, thinking about how to reduce coupling.

When the host called on me, I responded quickly and even added a performance-related note.

After the meeting, my boss praised me in the group chat for being thorough.

I don't think I deceived anyone. I just allocated my attention reasonably.

Slacking off isn't the goal; it's my way of fighting information overload and sustained pressure.

It lets me, after days of debugging APIs, chasing bugs, and tracking progress, keep a little unfilled space;

it lets me, in every gap while waiting for others to respond, catch my breath instead of being drained by anxiety;

it reminds me: not all time needs to be filled; what truly matters is what you leave behind.

I can now tell the difference: who is anxiously fake-busy, and who is steadily deep-producing.

The former reply to Slack the fastest, edit documents the most frequently, and attend the most meetings, but often say at the end of the day, "I feel like I didn't accomplish anything."

The latter may be quiet all day, but when they act, it's a whole package of efficiency improvements, complete monitoring scripts, or a performance-boosting pull request.

The true meaning of slacking off isn't doing less; it's creating gaps for yourself that allow you to keep creating value.

If you've ever had these moments:

You're already close to burnout but still afraid to stop;

You've answered countless Slack messages but can't remember what you actually did today;

After meetings, your mind is a mess, and you feel like you've been firefighting all day...

Then maybe we should ask a different question: not how to work harder, but how to regain a little initiative.

You don't need to become a high-output machine.

You just need to find those few blank spaces that belong to you, and in those spaces, cultivate a bit of endurance, a bit of inspiration, and a bit of uninterrupted thinking ability.

My favorite slacking-off moment is when, during the few seconds while test cases run in the terminal, a new idea for module encapsulation suddenly pops into my head.

At that moment, I know I'm not wasting time; I'm just reclaiming my own way of working.

And truly advanced slacking off is never about appearing idle on the surface, but about having an ordered mind within.