Skip to main content

Focus · Essay

How I use productive downtime to prevent burnout

The most productive thing I did last year was a week of near-nothing. Why rest is an input to the work, not a reward for it, and how I structure it.

Photo Productive Downtime

The most productive thing I did last year was a week where I did almost nothing. No big launch, no heroic sprint, just deliberate rest. I came back with a clearer head than three months of grinding had given me, and a decision I had been circling for ages made itself in about an hour. I tell this story to younger founders and watch them not believe me, because we have all been trained to think of downtime as the absence of work rather than a part of it.

I used to believe that too. I burned out the way a lot of founders do, quietly and then all at once, and the lesson it left me with is the thing I want to write down here: rest is not the reward for the work. It is an input to it, and treating it as optional is how you slowly make yourself worse at your own job.

Downtime is an input, not a luxury

The work I am paid for is thinking, and thinking degrades when it never gets to stop. Tired judgment is bad judgment that feels exactly like normal judgment from the inside, which is what makes it dangerous. The decisions I made while running on empty were not just slower. They were worse in ways I could not see at the time, because the same exhaustion that produced them also dulled my ability to notice they were off.

So I stopped framing rest as the thing I earn after the work and started treating it as part of the equipment that makes the work possible. You would not run a server at 100 percent utilization and call the headroom waste. The headroom is what keeps it from falling over.

Tired judgment is bad judgment that feels completely normal from the inside. That is exactly what makes it dangerous.

How I actually structure it

The practical version is unglamorous. I protect real evenings and real weekends often enough that they are a pattern and not a rare event I have to be talked into. I take proper breaks between intense stretches rather than rolling one straight into the next, because the recovery is where the previous push actually consolidates into something I can use. And I treat genuinely unstructured time, a walk with no podcast, an afternoon with no plan, as productive rather than indulgent, because that is reliably where my least obvious ideas show up.

This sits right next to how I think about integrating work and life and why I am so strict about defending my deep-work hours. The deep hours and the empty hours are not opposites. They are the same system. One does not function without the other, and I learned that the expensive way.

The discipline of stopping

The hard part is that stopping requires more discipline than continuing. Continuing is the default, especially when you run things you care about and there is always one more reasonable thing to do. Choosing to stop while there is still work undone, on purpose, trusting that you will be better for it, goes against every instinct that got you here. But the instinct is wrong, or at least incomplete. The founders I watch last are not the ones who can grind the longest. They are the ones who learned, usually the hard way, how to stop before the grinding starts costing them the very judgment they are grinding to protect.

I treat my rest like a deductible expense now. It is not the fun part of the budget, and skipping it always looks affordable in the moment. The bill for skipping it, when it finally arrives, never is.

NJ Nikhil Jathar “I treat rest like a deductible expense. Skipping it always looks affordable until the bill arrives.”