Dad solopreneur

Working in the noise: what my kids taught me about focus

October 30, 2026 · 6 min read

focus dad solopreneur Image : mgiacomazza — Openverse (by)

In short — Working with kids at home doesn’t destroy your focus: it forces you to make it more robust. Structuring your blocks around your kids’ rhythm — not the other way around — is the only system that holds up long-term.

For years, I thought the problem was the noise. Shouting from the living room, a door slamming down the hall, someone suddenly hungry right when I’d finally hit a flow state. I chased silence like a prerequisite. And I frustrated myself every single time it wasn’t there.

What took me a long time to understand was that silence wasn’t the variable. My system was — or rather, the absence of one.

The myth of necessary silence: what I had to unlearn

Deep work literature assumes a controllable environment. Cal Newport writes in a closed room, with a door nobody crosses before noon. That’s a luxury, not a method.

When you work from home, solo, with a teenager and a young one, the environment isn’t controllable. It’s alive. And if you build your productivity on the hope of a quiet house, you’re building on sand.

The real lesson was learning to separate focus from silence. They’re two different things. Silence is an external condition. Focus is an internal skill — it can be trained, conditioned, and unlike silence, you can actually control it.

What the noise forced me to develop: the ability to enter a focused state despite the context. Not against it. Despite it. And paradoxically, that skill is far more useful in the long run than the ability to work in perfect silence.

How I restructured my work blocks around my kids’ rhythm — not mine

The first concrete thing I did: map out the predictable windows. Not the ideal ones. The real, recurring ones I could count on 80% of the time.

In our household, that roughly means: an early morning slot before things get moving, a slot during after-school activities, and sometimes an evening slot when everyone’s settled. Three blocks, rarely all three on the same day, but at least one is reliable every day.

What I stopped doing: trying to squeeze deep work into the gaps between predictable interruptions. That’s the worst possible setup. Twenty minutes between lunch and the school run produces nothing useful on a cognitively complex task — it just produces stress.

The rule I set: a deep work block = minimum 90 minutes. Below that, it’s processing work (emails, tickets, code reviews). Creation and strategic thinking only happen during guaranteed blocks.

Immediate corollary: I stopped complaining about days with no long block. On those days, I process. I don’t create. That’s planned, not suffered.

AI has shifted something here too. Since I started using agents to absorb the mechanical side — client follow-ups, summaries, monitoring, first passes on content — short blocks are enough to steer the work. Creation stays human, but it’s better insulated. I have fewer processing tasks bleeding into my deep work slots. If you want to understand how the time-to-output ratio has evolved for solopreneurs working with AI, the solopreneur & AI statistics 2026 report gives useful context.

The tools and rituals that get me into focus in under 5 minutes

Entering focus has become an engineering priority. Not a wish — a procedure.

Here’s what works for me, in order of execution:

  1. The list is prepared the evening before. Not the morning. The night before. When I sit down to work, I know exactly what the first task is — not the next list to check in order to choose. The task selection is removed from the work block itself.

  2. The same track to open. One instrumental piece, always the same one to start. The brain associates the sound with the state. After a few weeks, the association is conditioned. It’s Pavlovian, and it works.

  3. Close everything that notifies before opening the work file. Not during. Before. In that order. If you open the file first and close notifications after, you’ve already lost 30 seconds reading a notification in passing.

  4. A seed sentence written at the end of the previous block. The first line of the next piece, the next function to write, the idea left hanging. Something unfinished that pulls. The Zeigarnik effect: the brain naturally returns to incomplete tasks. I exploit it deliberately.

This protocol actually takes between 3 and 5 minutes. It doesn’t eliminate interruptions — my son can shout, someone can ring the doorbell. But it reduces the cost of recovery. After a 2-minute interruption, I get back into state in 3–4 minutes instead of 15. Across a fragmented day, that’s the difference between 2 hours of real work and 45 minutes.

For the technical unblocking side — when I’m stuck on a problem and risk burning the entire slot on a bug — I also changed my rule: 20 minutes maximum before putting the problem to an AI agent. No misplaced pride. The slot is too valuable.

What it’s cost me — and why I wouldn’t go back

Let’s be honest about the real price.

I have weeks where the blocks don’t materialise as planned. Illness, the unexpected, family rhythm thrown off. Those weeks, I produce less. That’s a fact. A developer with no kids at home objectively has more non-negotiable slots in a week.

I’ve also had to give up certain types of work. Projects that require several consecutive days of immersion — the kind of sprint where you sleep in the code — that’s no longer my reality. I’ve adapted what I build to what my constraints allow: products I can move forward in 90-minute blocks, not marathons.

And I stopped comparing myself to the timelines of child-free solopreneurs. Not out of resignation. Out of pragmatism. The benchmarks are different, the lives are different.

What I’ve gained in return: a focus system that doesn’t depend on ideal conditions. I can enter a focused state in a noisy café, in a waiting room, in any uncontrollable context. It’s a skill I would never have developed if silence had been available.

And there’s something else, harder to quantify. Working with family constraints as a framework has forced me to only pick projects that are truly worth the cost of limited blocks. When every 90-minute slot counts, you don’t scatter your energy. You decide fast. You ship or you cut. The theory of constraints applied to working time.

My teenager and my little one taught me to work better — not in spite of them, but because of them.


If you’re building your solo business around family constraints and want an outside perspective on what you’re building, Sébastien De Bollivier supports solopreneurs and freelance devs — concretely, not theoretically.

Frequently asked questions

How do you stay focused when you work with kids at home?

The key isn't to chase silence — it's to structure your work blocks around your kids' rhythm. Solid 90-minute slots aligned with their absences or independent activities are worth far more than whole days fragmented by unpredictable interruptions.

How long does it take to reach deep focus as a parent solopreneur?

A realistic target is 5 minutes maximum, if you have a coded entry ritual: same music, same session-opening gesture, task list already prepared the evening before. Without a ritual, you lose 20 to 30 minutes on every transition — and you don't have that much time to waste.

Is deep work compatible with family life for a solopreneur?

Yes, but in a different form from what productivity books written by child-free men describe. Parental deep work happens in short, dense blocks (90 min to 2h), with a fast-recovery system after interruptions, rather than in long uninterrupted sessions.

Got an idea to ship? A website, a SaaS, an AI automation — built with you.

Talk about your project
Behind the scenes of the studio ✦

New products, work in progress and useful resources — the SEK studio in your inbox.