Busy Beats Bored

The Wrong Diagnosis

A few weeks ago I cut back on all the things I do after work. Not dramatically, not a full detox, just quietly let them slide. I stopped working on the side project I'd been building. Stopped taking the class I'd been chipping away at. Stopped messing around with new tools. Swapped all of it for phone games and TV at the end of the night.

I told myself I deserved the break. I'd been going hard. This was recovery.

By day three or four I felt a low-grade flatness settling in. Slightly irritable. Slightly foggy. The kind of feeling that makes you look around your life and start wondering what's wrong with it. What's wrong with your job, your relationship, your city. I started mentally auditing things that didn't need to be audited.

It took me until late one night to figure out what was actually happening. The problem wasn't what I'd added. It was what I'd removed.

I wasn't tired. I was bored. And I'd been treating boredom with more rest, which made it worse.

Boredom and Tiredness Feel Almost Identical

This is the trap. Both boredom and genuine fatigue come with some version of "I don't want to do anything." Both make you drag. Both make you less sharp. But the interventions are opposites.

Genuine fatigue needs rest. Boredom needs engagement. If you give rest to someone who's bored, you don't recharge them. You drift them further out.

Most high performers I know are bad at making this distinction, including me. We default to "I must be tired" because that's the more socially acceptable diagnosis. Tired is noble. Tired means you've been working hard. Bored sounds like ingratitude. So we misname it, apply the wrong fix, feel worse, and then wonder what's actually wrong.

The two-minute self-diagnostic isn't complicated. Ask yourself: when did I last do something genuinely engaging that I chose, not something on a deadline or an obligation? If the honest answer is "I can't remember," you're probably not tired. You're running low on input.

The System Needs to Stay On

Here's the mental model I keep coming back to. The human system, cognitively, emotionally, behaviorally, isn't designed for long stretches of low stimulation. It's designed to respond to input. Challenge, novelty, friction, even frustration. These are the signals that keep the system engaged and calibrated.

When you strip all of that out in the name of rest, you don't get a system that recharges. You get a system that starts to idle poorly. The engine is still running, but nothing's engaging the gears, and after a while it starts to knock.

I've seen this pattern in early-career employees more visibly than anywhere else. Student life has long open stretches built into it. Summers, breaks, whole semesters where the pace is variable and the obligations are light. Adult work-life doesn't have those by default. The first instinct is to grieve the open stretches you used to have. But what replaces them, hobbies, side projects, learning something hard, real friendships, even the occasional argument with someone you care about, that's the actual material of an adult life. It keeps the system on. Even the frustrating parts.

You want to feel something. That's not a weakness. That's the correct operating mode.

What This Has to Do With Managing

Here's where I want to be direct with the managers reading this, because there's a version of this conversation that stays personal and a version that doesn't.

When your engagement drops, your team feels it. Not metaphorically, literally. The way you show up in a one-on-one when you're genuinely interested in the person across from you versus when you're flat and going through motions. Those aren't the same experience for the person sitting there, and people know the difference.

You don't have to be performing energy you don't have. But you do have to take seriously that your personal engagement level is not just a personal problem. It's an organizational input. The manager sets the steady state. When you're running at 0.7, your team calibrates to that. They don't know that's what they're doing, but they do it.

I've also noticed this as a leading indicator worth watching in the people you manage. When someone who used to have a lot going on outside of work quietly lets all of it go, that's worth a conversation. Not an interrogation, but a genuine check-in. The side project, the class, the thing they were building. When those disappear, something's often shifting in how they're experiencing their life. Sometimes it's just a busy season. Sometimes it's something worth knowing about.

The Dignity of Having Too Much Going On

There's a version of the productivity conversation that treats busyness as the enemy. And okay, yes, manufactured busyness, the kind you perform to look important, is genuinely corrosive. I've written about that. But voluntary complication is a different thing entirely.

Voluntary complication is what you get when you've stacked your life with things you actually care about. A side project that excites you. A hard skill you're building. A class you're taking on your own dime because you want to know the thing, not because someone's making you learn it. Relationships that require some effort and some friction to maintain. Physical training that taxes you.

This is not the same as being overextended. The texture is completely different. Overextension feels like being pulled from the outside. Voluntary complication feels like you're generating the pull from the inside.

The people I know who are consistently engaged with their lives, who don't drift into that low-grade flatness, they all have one thing in common. They are doing more, not less. Not more reactive work, not more obligation. More chosen challenge.

Engineering Engagement Back In

If you're reading this and recognizing the pattern in yourself, here's the practical version.

Start small. Pick one thing you used to do that you stopped doing. Not the hardest thing, not the most ambitious. Just one thing that used to give you some forward motion and that you've let slide. Restart it this week. Twenty minutes, not twenty hours. Get the system back on.

Then pay attention to what happens. Within a few days you'll likely notice something shift. Not because the thing itself is so important, but because you've reintroduced input into the system. The engine has something to engage with again.

The goal isn't maximum busyness. The goal is minimum necessary engagement, and most people I know are running well below that threshold and calling it rest.

The Uncomfortable Version

I'll close with the thing that took me the longest to accept. Rest is necessary. I'm not arguing against it. But for most high performers, rest is not the scarce resource. Engagement is.

We know how to rest. We do not always know how to keep ourselves engaged when nothing external is forcing us to be. And the cost of getting that wrong isn't dramatic. It doesn't look like crisis. It looks like a week where you felt kind of flat for no reason you can point to, where you were slightly less yourself, slightly less useful, slightly less present.

That week has a cause. Now you know what to look for.