Do It · Growth Library

Leave a Ready-to-Resume Note Before You Switch Tasks

Reviewed protocol

Give unfinished work a restart point before your attention moves elsewhere

A person choosing one next action for focus and reliable follow-through
Protocol summary · reviewed

Try this

Use this only when unfinished work is about to be interrupted or deliberately parked. Before switching, capture three pieces of information in whatever format fits the task: your current state, the next concrete action, and one critical detail or open question that would otherwise have to be reconstructed. Then switch. When you return, read the note and start from the recorded next action rather than re-scanning the entire task.

Check-in: When I returned, could I identify the next action quickly, or did I still have to reconstruct the task from scratch?

Evidence: Reviewed · source · Leroy & Glomb (2018) — Ready-to-resume planning and attention residue after task interruption

Review note: Reviewed against Leroy & Glomb's interruption studies with convergent plan-making evidence from Masicampo & Baumeister. Public guidance is limited to creating a concrete resumption plan before leaving unfinished work. It does not claim that switching costs disappear, prescribe an exact note length, or promise a universal productivity effect.

An interruption does not necessarily end when you close the tab. Part of your attention can remain attached to the unfinished task while you are trying to work on the next one. In a series of studies, Leroy and Glomb found that anticipating a pressured return to unfinished work increased attention residue and hurt performance on the interrupting task; making a brief ready-to-resume plan mitigated those effects. A separate line of experiments by Masicampo and Baumeister found that making specific plans for unfinished goals reduced their cognitive interference. Brali turns that mechanism into a small handoff to your future self, without pretending that a note makes context switching free.

1. Use it before a real switch

This protocol is for unfinished work you are about to leave. If the switch is optional and the current task matters, finishing a sensible unit may still be better. If the interruption cannot wait, spend a moment preserving the state before your attention moves elsewhere.

2. Capture where you stopped

Write the current state, not a diary entry. Examples: comparison complete through row 420, draft has the argument but the evidence section is missing, or bug reproduced; failing path starts after validation. The note should let you recognize the exact frontier of the work.

3. Name the next concrete action

A vague instruction such as continue report forces you to decide again later. Prefer an executable restart: check the unmatched rows against source export, write the first paragraph of the evidence section, or inspect validation output for the failing request.

4. Save one piece of fragile context

Record the detail most likely to disappear from working memory: a file name, hypothesis, dependency, open question, relevant row, command, or decision. Add more only when the task genuinely needs it. The mechanism is resumption planning, not documentation theatre.

5. Resume from the note

When you return, read the note before reopening the whole context. Start with the recorded next action. If the note repeatedly fails to get you moving, improve the restart cue rather than making the template longer by default.

6. Keep the boundary honest

The studies do not establish a universal percentage improvement, an optimal note length, or a claim that all switching costs disappear. The useful evidence-backed idea is narrower: a concrete resumption plan can help the mind disengage from unfinished work and make the eventual return less reconstructive.

Questions to consider

Do I need exactly three lines?

No. The evidence supports making a resumption plan, not a validated three-line template. Brali uses three prompts because they are a compact way to preserve task state. Use less or more detail when the work requires it.

Does this remove the cost of context switching?

No. Interruptions can still be costly. The reviewed studies support a narrower claim: a ready-to-resume plan can reduce attention residue and protect performance in studied interruption contexts. Prevent avoidable switches first; use the note when a switch still has to happen.

When is this most useful?

When the current task is unfinished and you expect to return later: before a meeting, an urgent request, the end of a work block, or another deliberate switch. It adds little value when the task is already complete or trivial to reconstruct.

What should the note contain?

Prefer state over history. Record where the work currently stands, the next executable action, and the one dependency, decision, location, file, or question most likely to slow your restart.

Sources

Evidence state: reviewed. Sources are provided so the underlying material can be inspected directly.

Maintenance record

Review history

Current status: Reviewed. An editorial or evidence review is recorded and no later event changes that conclusion.

  1. 2026-09-11 · reviewed · Brali Evidence Reviewer Source: review-registry-research-watch-2026-09-11-productivity-deep-run.json

    Publish the strongest new productivity mechanism from the 2026-09-11 deep run as a bounded interruption-recovery protocol, preserving the study's actual scope and avoiding invented timing or performance claims.

Browse the review ledger · Challenge or update this hack

Implementation observations can trigger a review, but they cannot change an evidence conclusion by themselves. Commercial relationships do not control review status or outcomes.

Reviewed evidence decisions

These source reviews are linked to this hack for provenance. They do not change lifecycle status automatically; any material status change still requires an explicit lifecycle event.

  1. 2026-09-11 · propose-protocol · ready-to-resume-interruption-boundary-2018

    Reviewed source. When unfinished work must be interrupted, a short resumption plan can reduce attention residue and protect performance in the studied interruption contexts.

Browse the machine-readable Evidence Decisions

Continue from here

Choose the next useful path.

Article versions

Brali keeps substantive article history visible. Later reviews may refresh wording, sources, examples, or boundaries without silently replacing the record.

Canonical source record · Evidence state: reviewed.