Deep work dies in the doorway. You stand up for water, answer one ping, and come back blank. Write a return line before you leave a deep work block so the next sitting starts mid-thought instead of from zero.
A return line is one unfinished sentence on paper or in a sticky note. Not a summary. Not a todo. The exact next clause you would have typed if you had stayed. That scrap is a memory cue for working context, not a second plan.
Park the next clause, not a status update
Before you leave the chair, finish half a sentence you still believe. Example: “Next I cut the third paragraph because it repeats the claim about…” Stop mid-reason. The incompleteness pulls you back harder than a neat bullet.
If you only write “continue report,” you gave yourself a title, not a hold. Pair this with park one worry on paper before deep work so worries and return lines do not compete for the same sticky.
Leave for a named reason with a clock
Say why you are leaving: water, bathroom, stretch, one message. Set a two to five minute cap out loud. Unnamed exits become open browsing. Named exits stay short.
When the urge is a Slack ping, run a tiny delay first with count ceiling tiles before you answer the Slack ping, then write the return line if you still must leave the block.
Read the return line before any inbox
Sit. Read the scrap once. Type the next ten words from it. Only after that first typed burst may you check mail or chat. Inbox-first destroys the cue you just protected.
If the line feels wrong after the break, rewrite it in place, then type. Do not abandon it for a fresh outline. Rewriting keeps continuity; restarting invites drift.
Keep one sticky per active block
Reuse the same note for the session. Cross out the old return line when you write the new one. Stacked notes become a second backlog. One visible line beats a pile of half cues.
Cap side research the same way you cap tabs: when curiosity spikes mid-block, park it and return, using the spirit of cap research tabs at five before any rabbit hole.
Use the line after meetings too
Hard blocks often die after a calendar hit. Before you open the meeting room, write the return line for the work you are pausing. After the meeting, read it before you “just check” anything else.
If the meeting produced a new priority, write a second return line for that new task on a different note. Do not overwrite the paused project until you decide which block resumes first.
Train the habit on short exits
Practice on coffee and bathroom breaks for a week. Do not wait for a four-hour deep work fantasy. Short exits are where the skill sticks because they happen every day.
When you catch yourself returning blank with no scrap, mark a tally. The tally is feedback, not guilt. Raise the scrap rate before you raise the block length. For a related attention check, see teach one idea aloud in ninety seconds, no notes.
End the day by clearing leftover return lines that no longer matter. Stale cues create fake urgency tomorrow morning. Keep only the line for the first block you will actually open.
FAQ
What is a return line?
One unfinished next-clause you would type if you stayed seated.
Paper or digital?
Either. Prefer whatever you will see before the inbox. A sticky on the keyboard wins for many people.
How long should it be?
One sentence fragment. If it needs a paragraph, you are planning, not cueing.
What if I forget to write it?
Sit, reconstruct the last clear thought in one line, then type ten words from that. Rebuild once; do not punish with a full reread.
Does this replace a task list?
No. Task lists hold work. Return lines hold working memory across a short exit.
Can I use it for coding?
Yes. Leave the next failing test name or the next function call you meant to write.
