Parental Burnout: When the Project Runs Hot

I manage projects for a living. One of the first things you learn is that if you run a team at 110% utilization with zero slack, you don’t get 110% output. You get a few good weeks, and then you get cascading failures, missed dependencies, and a key person quietly burning out while everyone insists everything is fine.

Around month eight with Owen, I was the key person. And everything was not fine.

I didn’t have a word for it at first. I just knew I was snapping at small things, dreading the 3pm-to-bedtime stretch, and feeling a flat grey nothing where I used to feel like a competent person. It took me an embarrassingly long time, given my literal profession, to look at myself and go: oh. This is burnout. The project is running hot.

Burnout is not the same as being tired

This distinction took me a while. Tired is a resource problem — you’re low on sleep, you recover with rest. Burnout is a systemic problem. I was getting okay-ish sleep by month eight and still felt hollowed out, and that mismatch is what finally tipped me off.

The research framing that helped me most splits burnout into three components: exhaustion, cynicism or detachment, and a reduced sense of accomplishment. I had all three. I was exhausted, I’d started going through the motions of bedtime like a robot, and I felt like nothing I did actually moved anything forward, because with a toddler nothing ever stays done.

That last one is the killer for someone like me. My whole identity is “I close tickets.” Parenting an eight-month-old is a project where you close the same ticket 400 times and it reopens every morning. There is no done. For a completion-driven brain, that’s quietly corrosive.

The capacity math I’d been ignoring

If a client asked me to staff a project with one resource, full time, no backup, no scheduled time off, indefinitely, I would tell them it’s going to fail. I’d put it in a risk register in red. And yet that was exactly the arrangement I’d built for myself at home and never questioned.

My wife and I had drifted into a setup where I “had it handled” in the evenings and on weekend mornings, because I’m the data guy, I have the systems, I can run the routine. That worked great right up until it didn’t. There was no slack in the schedule. The first unexpected thing — a sick week, a work crunch — and the whole thing buckled.

The fix, when I finally treated it like a real capacity problem, was almost insultingly straightforward. We needed slack and a backup resource. That meant my wife and I actually splitting coverage deliberately instead of by default, building in genuine off-shifts where the other person is fully not-on-call, and — the hard one — me accepting that “handled less well by someone else” is infinitely better than “handled perfectly by a person who’s flaming out.”

The shame part, which is the real obstacle

Here’s the thing I almost didn’t write. Admitting I was burned out felt like admitting I wasn’t cut out for this. I have a son I desperately wanted. I get to be his dad. What kind of person gets to do that and feels burned out?

That shame is exactly why I sat in it for weeks instead of saying anything. And it’s nonsense. Burnout isn’t a referendum on how much you love your kid. I’d never look at a burned-out engineer and conclude they didn’t care about the product. They cared too much, with too few resources, for too long. Same thing.

The moment I actually said the words out loud to my wife — “I think I’m burned out and I don’t know how to say that without sounding ungrateful” — was the moment it started getting better. She wasn’t shocked or hurt. She was relieved, because she’d been feeling some version of it too and was equally afraid to say so.

What actually pulled me out

No single thing. It was a few boring adjustments compounding, which is the least satisfying answer for a guy who wanted one clean fix.

We scheduled real off-time, on the calendar, non-negotiable — two hours each, twice a week, where the other person owns everything. I started taking a walk alone after Owen went down instead of immediately opening the laptop. We lowered the bar on the house; a messy living room is a fine trade for a parent who isn’t running hot. And I talked to my doctor, because part of “is this burnout or something more” is genuinely a question for a professional, not for me at 1am.

I’d love to tell you I built a burnout-tracking dashboard, and reader, I did briefly try, and that was honestly a symptom of the problem more than a solution. The fix wasn’t more measurement. It was more slack.

One thing that helped put the burnout in context: once I stopped trying to optimize every minute, I could think more clearly about what was actually driving the exhaustion. In our case, some of it was the relentless financial decision-making of the first year — I’d recommend doing the childcare math early so it’s not a lurking stressor when you’re already depleted. And if screen time has become a coping tool — it did for us — our post on screen time under age 2 takes a guilt-free look at what the research actually says. Sometimes the thoughtful-but-imperfect approach is the right one.

The hair loss that hit around the same time — and yes, I looked it up — turns out to have its own perfectly biological explanation. Our post on postpartum hair loss is the companion piece for partners who are watching this happen and feeling helpless.

If you’re reading this at the end of a day where you’ve got nothing left and you feel guilty for even having the thought: you’re not failing, and you don’t love your kid any less. You’re a single resource running at full capacity with no backup, and that fails for everyone, every time. Build in the slack. Say it out loud to someone. The project doesn’t need you at 110%. It needs you to still be standing in a year.