Protocol
Keep a return list instead of switching now
Capture is cheaper than a context switch.
When it fits
- When ideas arrive during focused practice and feel too valuable to ignore.
When to avoid it
- If an idea signals an urgent safety, legal or production issue, switch appropriately. The return list is for deferrable opportunities.
Why it matters
Record the idea with the minimum context needed to evaluate it later, then return to the active task. Review the list at a scheduled boundary and either promote, schedule, merge or discard each item. The list is a bridge back to curiosity, not another infinite inbox.
Steps
- The active task resumes quickly, and captured ideas receive an explicit later decision rather than permanent accumulation.
An example
During German practice, an idea for a new MHC collection is captured in one line and reviewed after the current practice block rather than opening GitHub immediately.
Check your result
The active task resumes quickly, and captured ideas receive an explicit later decision rather than permanent accumulation.
Keep this limit in mind
- If an idea signals an urgent safety, legal or production issue, switch appropriately. The return list is for deferrable opportunities.
Evidence and sources
An integrative review reports decreased performance in many dual-task and task-switching conditions compared with appropriate single-task controls.
Switching can still be necessary and adaptive; the review does not imply that uninterrupted work is always optimal.
A review of cognitive control argues that adaptive behavior requires both cognitive stability for task focus and cognitive flexibility for switching when goals or circumstances change.
This is a conceptual synthesis rather than a trial of a personal goal-prioritization system.
Principles of cognitive control over task focus and task switching · Abstract, introduction and conclusion