People and parenting
Parents: the 10-minute window nobody tells you about.
You'll never get a free afternoon. You do get ten minutes, several times a day. Why interruptions wreck big tasks, and how to build on small windows.
By The StartKick team · October 3, 2026 · 3 min read

Before kids, you had evenings. You could sit down at eight and work until it was done.
Now the evening is bath, stories, one more glass of water, and by the time it's quiet you're asleep on the sofa with your laptop still closed.
So the thing you wanted for yourself, the course, the side project, the book, waits for a free afternoon. And the free afternoon never comes.
Here's what parents who still get things done have figured out. They stopped waiting for the afternoon. They learned to use the ten minutes.
Why it happens
Interruptions cost more than the interruption
Gloria Mark and colleagues studied what happens when people are interrupted during work. The interrupted people finished their tasks in about the same time, but they worked faster to do it, and reported more stress and more pressure (Mark, Gudith & Klocke, 2008).
If you're a parent, that's your whole day. You pay the stress cost on every task, even the ones you finish. No wonder a big project feels impossible: it's a task that would be interrupted twenty times.
Half-finished work follows you around
Sophie Leroy found something she called attention residue. When people switch from a task they haven't finished to a new one, part of their attention stays with the first task, and they do worse on the second (Leroy, 2009).
A parent switches all day. Project, child, project, dinner, project. Each switch leaves residue, and the project, the only thing with no deadline, is what gets dropped.
A task sized for an afternoon can't fit a window
This is the fixable part. "Work on the course" is an afternoon-sized task. It can't start in ten minutes, so it never starts. "Watch lesson three" fits. "Write the first exercise" fits.
Peter Gollwitzer's research on "if-then" plans shows that linking a specific action to a specific moment makes people far more likely to act (Gollwitzer, 1999). For parents, the moments already exist. Nap time. The twenty minutes after drop-off. The one episode of the cartoon. The missing piece is an action sized to fit.
Small ways in
Cut the project into ten-minute pieces, in advance
Sit down once, when it's quiet, and break the project into pieces that take ten minutes each. Write them in a list. From now on you never decide what to do in a window. You take the top piece.
Name your windows
Most days have the same gaps: after drop-off, nap, the cartoon, the first ten minutes after bedtime. Pick two. Write "if nap, then the next piece on the list." Don't add more until these two are working.
Leave the work open
Residue works both ways. If you stop mid-sentence and leave the file open on the screen, the next window starts in the middle. No warm-up, no "where was I".
Accept the piece as the whole win
Ten minutes a day is over an hour a week and five hours a month. It doesn't feel like it from inside one window. Count the pieces, not the hours, and look at the count on Sunday.
Let the afternoon go
Stop planning for it. If a free afternoon shows up, great, use it. But the project should run on windows. Then the afternoon is a bonus instead of a condition.
Try this now: Take your project. Write down the next ten-minute piece. Put the note where you'll see it at the next quiet moment.
If you want a first move that fits your kind of stuck, take the StartKick check.
Sources
- Gollwitzer, P. M. (1999). Implementation intentions: Strong effects of simple plans. American Psychologist, 54(7), 493-503. https://doi.org/10.1037/0003-066X.54.7.493
- Leroy, S. (2009). Why is it so hard to do my work? The challenge of attention residue when switching between work tasks. Organizational Behavior and Human Decision Processes, 109(2), 168-181. https://doi.org/10.1016/j.obhdp.2009.04.002
- Mark, G., Gudith, D., & Klocke, U. (2008). The cost of interrupted work: More speed and stress. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI '08), 107-110. https://doi.org/10.1145/1357054.1357072

