The doorbell took ninety seconds, the return took forty minutes
I was reconciling a client's invoice export against their payment records, the kind of job where you hold three numbers in your head and a filter on a spreadsheet, when a courier rang with something that needed a signature. Ninety seconds at the door. Easy.
I sat back down and could not remember which rows I had already checked. So I did what felt like easing back in: I opened my email to warm up. There was a message from another client with a small question. The small question needed me to look something up. Looking it up led to a second question. When I finally returned to the spreadsheet it was almost noon, the filter I had applied had been cleared at some point, and I started the reconciliation again from row one.
The courier cost me ninety seconds. Everything after that was my own doing. That is the pattern I see in nearly every interrupted home workday, mine and other people's: the interruption is short, and the expensive part is the return.
You cannot delete interruptions from working at home, and a plan that assumes silence will make ordinary life feel like a personal failing. What you can control is the handover. About sixty seconds before you leave the chair, and two minutes when you sit back down.
The interruption is short, and the expensive part is the return.
The sixty-second park
Do these in order, before you stand up. The timings are deliberately tight, because the whole point is that this is short enough to actually do when someone is waiting at the door.
Seconds 0 to 15: write the next physical action. One line, with a verb and a location in it. This goes first because it is the most valuable thing on the list, and if the interruption turns out to be longer than expected, at least this part got done.
Seconds 15 to 30: make the work safe. Save the file, commit or stash the code, take a screenshot of any state you cannot easily reproduce.
Seconds 30 to 45: note anything volatile. The filter you applied, the test account you were logged into, the half-written formula, the tab you were comparing against. Volatile state is exactly what you will not think to write down and will definitely need. In my reconciliation story, it was the filter.
Seconds 45 to 60: end the block honestly and go. Pause or stop the timer if you use one. Do not leave it running while you are at the door, because a record that says you worked when you did not makes the whole record useless to you later.
Here is what the reconciliation should have looked like:
Next: compare column K totals against the invoice export, rows 40 to 80
Saved: reconciliation-aug.xlsx
Volatile: filter is on Status = open; formula in K42 is unfinished
About twelve seconds of typing. It would have turned a forty-minute return into a two-minute one.
Write a park line you could hand to someone else
Vague park lines are the reason people try parking once and decide it does not work. "Continue bug" is a topic, not an action. When you sit back down, a topic makes you rebuild the whole situation before you can do anything. An action lets you start.
A good park line has a verb, an object, and where it lives:
- "Open ticket 441 and paste the failing request log"
- "Resume the paragraph under Pricing Risks in
proposal.md" - "Run
InvoicePdfTest with --filter=eur and check the rounding on line 3"
The test I use is whether someone else could do the line without asking me anything. If a stranger could, then tired, slightly irritated me coming back from the door can too. There is more on writing actions this way in why remote workers need a clear next action.
For code, the volatile details are often the ones that matter most. If you are halfway through reproducing a billing bug, the park line wants the branch name, the failing assertion and the ID of the test order you were using. Skip it, and you come back guessing which seed data you used, and the reproduction you spent twenty minutes building is gone.
The return matters as much as the park
Coming back has its own two minutes, and the order is the whole trick.
- Read the park line before looking at anything else on the screen.
- Close the tabs and windows the interruption opened. They are the seeds of the next drift.
- Restore the volatile state you noted.
- Start a fresh block, with a smaller goal if there is less time left.
- Do the written action before opening any messages.
Step five is the one everybody breaks, and it is the expensive one. Checking chat or email as a warm-up feels like a gentle way back in. What it actually does is hand the rest of your block to whoever messaged you most recently. That is exactly what happened with my reconciliation. My inbox was not more important than the spreadsheet. It was just easier to open.
If the interruption was long, say fifteen minutes or more, treat the return like a small version of starting the day. Read the note, rerun the last command or reapply the filter, and start a shorter block with a smaller target than the one you left. Trying to pick up at full speed after a long break usually means ten minutes of fumbling first.
Sort your interruptions into two piles
I kept a rough tally for a couple of weeks, just a mark on the back page of my notebook each time something pulled me out of a block, with a word next to it. What surprised me was how few were truly random.
Predictable interruptions belong on the schedule. The delivery window that is almost always around midday, the school run, a recurring call that makes the flat loud, the neighbour's dog that barks at the post. These do not need a recovery protocol at all. They need to stop being placed on top of your hardest work. If deliveries usually turn up around noon, that is when review, triage or admin should happen, and the fifty-minute deep block belongs at 09:00. Matching work to the shape of the day is what structure a remote workday is about.
Random interruptions need the park. The unexpected knock, a pipe making a strange noise, a phone call from a family member who needs a quick hand with something. There is no scheduling answer for these. There is only a cheaper return.
Most of my marks turned out to be the predictable kind, things I had simply never planned around. A couple of weeks of noting them was worth more than redesigning my whole day after one bad afternoon, which is the instinct when you are annoyed.
Household interruptions and work interruptions need different rules
People at home and people at work interrupt for different reasons, and treating them with one rule tends to fail both ways. At home, people interrupt because they cannot tell you are busy, or because they do not know when you will be free. At work, people interrupt because chat makes every message feel equally urgent.
For the household, the most useful thing is an end time. "I'm free at 11:20" works far better than a closed door, because it turns an indefinite wait into a short one. Agree what always interrupts anyway (safety, a pickup that has changed, something that needs a signature right now) and where everything else goes until then, such as a note on the fridge or a shared list. The full setup is in protecting focus at home.
For colleagues and clients, a status that says what you are doing and when you will be back reduces pings without pretending you are offline. Something like "Heads down until 11:30, will reply after". Pair it with one clearly defined route for real emergencies so nobody has to guess.
When the day keeps breaking
After three interruptions in a morning, I stop trying to run the plan I made at 08:30. That plan assumed a different morning. Instead I shrink the next block to fifteen or twenty-five minutes and pick a result small enough to finish inside it. Repeatedly attempting a deep session in a fragmented afternoon produces neither depth nor progress, only the feeling of losing, which then follows you into the evening.
If the main task genuinely needs a long quiet stretch, move it to a quieter time, or go somewhere else for one block, such as a library or a coworking desk for the morning. When leaving is not an option, switch to work that tolerates interruption: review, triage, documentation, small fixes. Changing the plan is a real solution. Blaming yourself is not. Days where the interruptions are someone who needs looking after, rather than doorbells, need a different approach again, covered in a remote workday that survives caregiving interrupts. And if you are mid-debug when something breaks in, interruptions during debugging explains why that particular kind of break costs more than most.
Do not pay it back in the evening
A day full of interruptions makes "I'll finish it tonight" sound reasonable. I have done it plenty of times. It nearly always borrows from tomorrow: you work tired, make choices you redo in the morning, and start the next day already behind on rest.
The better move is to stop at your normal time with a clean park line for tomorrow's first action. Interrupted days produce less, and that is fine. They produce far less if you also wreck the next morning trying to catch up.
Interruptions at home are normal. They will keep happening however carefully you plan. What you can make optional is the forty minutes after each one, and you do that with a sixty-second note, and by reading it before you read anything else.