Deep work in a fragmented day

Externalize your context

Rebuilding context after an interruption can take time. A two-line handoff note—what you were doing and the next step—makes the restart point visible. No time saving is measured here; evaluate its usefulness in your own workflow.

The same principle scales up: a project with a written current-state note can survive a week of neglect; one kept entirely in your head cannot.

Example scenario: a side project

Example scenario: you work on a side project in 45-minute evening blocks. Without a handoff note, each session starts with re-reading yesterday's diff. With a three-line note at the top of the working file — goal, current step, known blocker — each session starts with actual work.

This is an illustrative scenario, not a measured productivity claim.

Rituals versus flexibility

Rigid time-blocking systems break the first time real life intervenes, and the guilt of breaking them becomes its own distraction. A lighter approach — protect one block per day, keep notes so other blocks stay useful — trades theoretical maximum focus for a system that actually survives contact with a real week.

A short focus checklist

End every work session with a two-line handoff note; keep one protected block per day, even a short one; batch messages instead of monitoring them; define 'done' for each session before starting; and treat a broken routine as data, not failure.