Ready for Ready
Capture interrupted work so you can switch and return without residue
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 96%
Ready for Ready reframes interruptions as inputs to manage. First decide whether the input should reach you: some should be blocked, while others are legitimate parts of a role or commitment. If the new matter cannot be finished immediately, capture it in a trusted placeholder with enough clarity to return later. Do the same for the work being left so the brain does not have to keep either thread active. This makes task switching easier because unfinished work has a reliable return path. Maintain the capacity for surprises by processing inboxes and unclarified backlog toward zero. When an unexpected situation arrives, a low backlog allows you to judge whether to act, park it, delegate it, or ignore it from a clearer picture instead of reacting through accumulated anxiety.
Origin
Allen framed readiness as the ability to absorb inevitable surprises without losing control, drawing on GTD capture and clarification practices rather than trying to eliminate every interruption.
Core principles
- 01An interruption is an input that must be accepted or rejected
- 02A trusted placeholder lets attention release unfinished work
- 03Low backlog improves judgment when surprises arrive
- 04Readiness matters more than eliminating every switch
How to run it
- 1
Classify the input
Decide whether the new request is irrelevant, improperly routed, or part of a real commitment. Block what should not arrive and accept what belongs to the role.
Pro tip In reactive jobs, frequent incoming requests may be the work rather than a distraction from it.
Watch out Calling every legitimate input an interruption hides a role-design issue.
- 2
Choose now or later
Determine whether the input deserves immediate completion. If it does not, make a deliberate later commitment rather than leaving it mentally open.
Watch out Do not act immediately merely because you distrust your ability to remember it.
- 3
Place-hold both threads
Record the new request and the return point for the work you are leaving in a trusted system. Make each next step clear enough to resume without reconstructing context.
Pro tip Ask the requester to send a text or email when that is the most reliable capture path.
Watch out A vague note preserves the cognitive effort of figuring out what it means.
- 4
Switch cleanly
Release the parked thread and give the chosen task full attention. Trust that the placeholders will bring both matters back when needed.
Watch out Repeatedly checking the parked item defeats the purpose of trusted capture.
- 5
Restore readiness
Process inboxes and unclarified backlog toward zero when capacity returns. Preserve room to evaluate the next unexpected input clearly.
Pro tip Use quiet gaps to clarify backlog rather than merely scanning it.
Watch out A growing unprocessed backlog makes every new input feel more threatening.
In the wild
A colleague asks for a report while you are preparing a presentation. Decide that the request is legitimate but not immediate, ask them to email the details, and note the exact slide you will resume. Add the report's next action to the trusted system, finish the presentation block, then process the request at the promised time.
→ Both tasks retain a reliable return path and neither has to remain active in working memory.
Common mistakes
Trying to eliminate a reactive job
For customer service or internal support, responding to inputs may be the actual role rather than an avoidable interruption.
Switching without a placeholder
Without a trusted return point, part of the mind keeps rehearsing the unfinished task.
Letting backlog consume readiness
A large unclarified inventory makes it harder to evaluate new demands proportionately.
Is it for you?
Best for
It is best for roles where legitimate requests and surprises arrive throughout the day.
Not ideal for
It is not ideal when the real problem is an avoidable notification or request that should be blocked entirely.
From the transcript
“there are no interruptions there dismiss manage inputs”
“once you're actually in that state you can switch tasks much more easily because your brain is not wrapped around the thing once you leave…”
“when that hits I want as little backlog as possible in terms of uncaptured unclarified stuff”
From the episode
YAPClassic: David Allen on Getting More Sh*t Done
YAPClassic