The interruption is not the expensive part

A doorbell takes ninety seconds. What costs you half an hour is coming back to a screen and not knowing what you were about to do, so you open your inbox to warm up, and the inbox has opinions.

You cannot delete interruptions from a home workday, and a plan that assumes silence will make ordinary life feel like a personal failing. What you can control is the handover: sixty seconds before you leave, and two minutes when you get back.

The 60-second park

Do these in order, before standing up. The timings are deliberate, because the whole point is that this is short enough to actually do.

Seconds 0 to 15: write the next physical action. One line, with a verb and a location in it. This is the single most valuable thing you will do, so it goes first in case the interruption escalates and you get no further.

Seconds 15 to 30: make the work safe. Save the file, commit or stash the code, take the screenshot of the state you cannot 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 what you will not think to write down and will definitely need.

Seconds 45 to 60: end the block honestly and go. Pause or complete the timer. Do not leave it running while you are away, because a record that says you worked when you did not makes the whole record useless to you.

Worked example. You are reconciling two exports in a spreadsheet when the doorbell goes:

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

Twelve seconds of typing. It reduces the return from twenty minutes to about two.

A block that ends cleanly instead of being abandoned mid-thought

Make the park line startable

Vague park lines are the reason people conclude that parking does not work. "Continue bug" is a topic. Include the verb, the object, and where it lives:

  • "Open ticket 441 and paste the failing request log"
  • "Resume the paragraph under Pricing Risks in proposal.md"
  • "Call the supplier on the number in the delivery note and confirm the Friday slot"

The test is whether someone else could execute the line. If yes, then tired-you can too. For more on writing actions this way, see why remote workers need a clear next action.

The return protocol

Coming back has its own two minutes, and the order matters as much as the park did.

  1. Read the park line before looking at anything else on the screen.
  2. Close the tabs and windows the interruption opened. They are the seeds of the next drift.
  3. Restore the volatile state you noted.
  4. Start a fresh block, with a smaller goal if there is less time left.
  5. Do the written action before opening messages.

Step five is the one people break, and it is the expensive one. Checking chat as a warm-up feels like easing back in. What it actually does is hand the rest of your block to whoever messaged you most recently.

Sort your interruptions into two piles

Predictable ones belong on the schedule. School pickup, the daily delivery window, the dog at 13:00, a partner's recurring call that makes the flat loud. These do not need a recovery protocol, they need to stop being placed against your hardest work. If deliveries usually land around noon, put review, triage, or admin there and keep the 50-minute block for 09:30. The structure a remote workday is for exactly this matching.

Random ones need the park protocol. The unexpected doorbell, the neighbour drilling, the pipe. There is no scheduling answer, only a cheaper return.

Spending a week noting which pile each interruption belonged to beats redesigning the whole day after one bad afternoon. Most of them turn out to be predictable and simply never planned for.

Agree the signals out loud

Shared homes run on assumptions until someone writes them down. Four things worth agreeing explicitly:

  • What the signal is. A closed door, a sign, headphones on. Everyone knows which one.
  • What can interrupt anyway. Illness, safety, a child who needs help, a package that needs a signature.
  • What waits. Routine questions go on a note or a shared list for the next break.
  • When the current block ends, so waiting has a visible finish line.

That last point does most of the work. People interrupt partly because they do not know how long the alternative is. "I am free at 11:20" resolves it far better than a closed door does. There is more on the environment side in protecting focus at home.

When the day keeps breaking

After three interruptions, stop trying to run the plan you made this morning. 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. Caregiving days need a different shrink system than doorbells: a remote workday that survives caregiving interrupts.

If the primary genuinely needs a long quiet stretch, move it to a reliably quiet hour or plan one block somewhere else, such as a library or a coworking desk. When leaving is not an option, switch to work that tolerates interruption: review, triage, documentation, small fixes. Changing the schedule is a real solution. Blaming yourself is not. For the cost of a broken deep session mid-debug, see interruptions during debugging.

Use the named current task on your shutdown note as the park line, and keep Up Next short so an interrupted day does not turn into a queue of competing restarts. ## Restart after interruption is a skill, not willpower

After a legitimate interrupt, read one parked line and touch the artifact within two minutes. Do not reopen chat "just to catch up."

Example: Doorbell at 10:20. Park "open InvoicePdfTest, run with --filter=eur," handle delivery, return at 10:28 to that command.

Family versus coworker interrupts

Household interrupts need agreed signals; coworker interrupts need tiers. Mixing them without rules makes every ping feel equally urgent.

See a remote workday with caregiving interrupts and available all day is a bad system.

Evening bleed after a fragmented day

A day of interrupts tempts "I'll finish tonight." That trade often borrows from tomorrow. Prefer shrinking the primary and stopping on schedule via shutdown routine.

The park note is non-negotiable

Every interrupt longer than thirty seconds gets a park line before you stand up: next command, failing test, ticket link. Without it, domestic and workplace interrupts cost the same twenty-minute rebuild.

Keep park notes in the ticket so partners do not need access to your private scratchpad.

Visible status beats constant availability

"Deep work until 11:30, async OK" on your status reduces pings without pretending you are offline. Pair with tier-one channel for true emergencies.

Example: Team agrees emoji or phrase for fragile debug so nobody has to guess from silence.

Batch household questions

Partners and kids accumulate "quick questions" because you are visible. Offer a fixed check-in at lunch and after shutdown for non-urgent needs.

Urgent stays urgent. Everything else waits for the edge, same as work chat batching.

Recover the block after a long interrupt

When an interrupt eats more than fifteen minutes, treat the return as a mini morning: read park note, rerun last command, start a shorter block with a smaller goal.

See recover a workday after losing focus when the whole morning fragments.

Example: delivery at the door mid-debug

Example: Doorbell during reproduction of a billing bug. Park: branch name, failing assertion, seed order id. Answer door. Return, rerun test, continue.

Skipping the park line means guessing which seed you used and losing the repro.

Home interrupts are normal. Unplanned reload tax is optional when parking is habit.