Before I had a kid, I had a productivity system. Time blocking, spaced repetition, the Eisenhower matrix, a reusable notebook for daily planning. I'd read the books, tried most of the systems, and landed somewhere that worked for a person with eight uninterrupted hours and genuine control over how they spent them.
Then we had a kid. The system did not survive contact with a newborn.
This isn't about how I rebuilt the perfect system. I haven't. It's about what actually survived, and what I learned discovering that most productivity advice is written for people with uninterrupted blocks of time, which parents of small children almost never have.
You are not going to win the time battle
The first thing I had to accept: I was not getting my time back. I was going to do less than before, full stop, and the sooner I stopped trying to make the numbers add up the old way, the better.
This sounds obvious. It took me four months to actually believe it. I kept looking for the hack that would let me maintain pre-kid output. There is no such hack. You are splitting your attention with a person who has no concept of your goals and zero obligation to cooperate with them.
What you can do is get ruthlessly selective about what matters. The bottleneck when you have a kid is not time. It's cognitive load. Figuring out what to cut is often more valuable than squeezing more from the hours that remain.
Asymmetric tasks become your best friend
An asymmetric task is one where the time invested is small relative to the value it returns. Forty minutes with a dense technical paper might unlock two weeks of clearer thinking. Ten minutes of planning on Sunday afternoon might prevent three days of scattered context-switching.
Before I had a kid, I didn't think much about this. I had time for both high-leverage and low-leverage work. Now the low-leverage stuff is mostly cut or delegated, which means what remains is high-leverage by default. There's something clarifying about that, even when the clarity is uncomfortable.
I think in terms of load-bearing tasks: things that, if I skip them, other things stop working. For work, that's architecture decisions and code reviews blocking other engineers. For home, it's the planning sessions that keep the week from falling apart. Everything else gets measured against that bar.
Protect your transition windows
When the kid finally naps or goes to bed, the instinct is to decompress. Scroll, watch something, stare at the ceiling. Sometimes that's exactly right. But the first twenty minutes of a transition window are often the highest-value work time in my day.
What makes them work is that they can't be extended. You have maybe ninety minutes before the nap ends or you fall asleep. That hard deadline creates focus that an open afternoon rarely does. Some of my best technical writing has happened in post-bedtime windows precisely because the clock was already running.
The key is knowing in advance what you're going to work on. If I have ninety minutes and spend twenty deciding what to do, I've burned a significant fraction of the window before I've started. I try to end every morning with one sentence written down: tonight I'm working on X. That sentence does more planning work than anything else I do.
Do not try to multitask with a kid
I spent several months trying to work while watching my son. It doesn't work. The work is bad, the parenting is worse, and I'm not actually present for either one. The context-switching overhead between watching a toddler and writing an architecture doc is not small.
What I found is that some things are genuinely compatible with a kid in the room if the kid is occupied: podcasts, audiobooks, walking, light household tasks. Not work, but ways to stay current with what's happening in my field. That indirectly supports the work.
Enforcing a real separation between kid-time and work-time improved both. Trying to blend them made both worse.
Redefine what done looks like
The most useful shift I've made as a parent is separating effort from output expectations. Before, I judged a work session by whether I finished what I'd planned. Now I judge it by whether I did focused work with the time I had. Ninety minutes of genuine concentration on something load-bearing is a good session, even if I didn't finish. Progress beats completion of something peripheral.
This sounds like lowering your standards. I don't think it is. It's changing what you measure. Tracking completion rate when your schedule is fragmented by an unpredictable infant is a fast path to feeling like a failure every day. Quality of effort is something you can actually control.
There are still days where nothing happens. The nap doesn't come. Bedtime runs three hours. I get nothing done. Those days are real and there's nothing to optimize about them. You close the laptop and you're a parent for the rest of the day.
The goal isn't to be productive in spite of having a kid. It's to be productive in a way that doesn't pretend the kid doesn't exist.
---
If you're working on the systems side of this, my post on productivity hacks for 2026 covers time blocking, eating the frog, and a few other approaches that have held up well alongside parenting. And if the home side is where things are falling apart, how I cut my chores time by 60% is about exactly that.