Log every context switch for one day: time, from-task, to-task — measure switching costs before attempting reduction
Log every context switch during a baseline measurement day by recording time, source task, and destination task without attempting reduction, because accurate switching-cost assessment requires measurement that precedes intervention to establish true baseline against habituated behavior.
Why This Is a Rule
Context switching is habituated — you do it dozens of times per hour without noticing. Each switch has a cost (Calculate activity cost as disruption footprint: ramp-down + activity + ramp-up — the true cost includes attention residue attention residue, Multiply direct correction time by 3x for true cost — context-switching, opportunity cost, and verification overhead are invisible 3x multiplier), but because the switching is invisible to the switcher, the total cost is invisible too. You believe "I switch tasks a few times per hour" when the actual count is often 30-50+ switches per day, each with a recovery cost.
The baseline measurement — logging every switch without attempting reduction — makes the invisible visible. Like Don't optimize during an energy audit — maintain unmodified behavior for the full measurement period to preserve diagnostic validity (maintain unmodified baseline during energy audits), the "without attempting reduction" constraint is essential: if you try to reduce switching during the measurement day, you're measuring your optimized behavior rather than your habitual behavior. The habitual behavior IS the diagnostic target because that's what you'll default to on every non-measurement day.
Three fields per switch — time, source task, destination task — capture the minimum data for pattern detection: when do you switch most (time patterns), what do you switch away from (avoidance patterns), and what do you switch to (attraction patterns). "Switches away from writing toward email at 10:15, 10:28, 10:41, 10:53" reveals both the frequency and the avoidance pattern.
When This Fires
- Before implementing any attention management or deep work system — measure first
- When you suspect context switching is draining productivity but can't quantify it
- When you want to identify your primary switching triggers and patterns
- Complements Log every task AND its trigger for one full day — then calculate your external-to-deliberate ratio to quantify reactivity (task trigger audit) with the switching-specific measurement
Common Failure Mode
Reducing switches during the measurement day: "I notice I'm switching a lot — I'll try to focus." This produces a flattering but inaccurate baseline. The measurement day should feel like a normal day where you simply log what happens, not a day where you perform better because you're watching yourself.
The Protocol
(1) Choose one representative workday for baseline measurement. (2) Keep a log accessible (notepad, open document). Every time you switch from one task to another, record: Time: when the switch occurred. From: what you were doing. To: what you switched to. (3) Include ALL switches: email checks, phone glances, browser tab changes, conversation interruptions, internal "I wonder..." digressions. (4) Do NOT attempt to reduce switching during measurement. Behave normally. The data's value comes from its accuracy about your habitual behavior. (5) At end of day: count total switches. Identify the top 3 switching patterns (what-to-what transitions occur most?). Calculate average time between switches. This is your baseline for evaluating any attention management intervention.