Run the play
Field guide: what breaks focus, how it shows up, and where to start
Interruption-heavy work breaks into three visible causes: external demands (inbox pings, meetings, direct messages), role design (operator vs. maker tasks mixed in the same day), and handoffs with unclear urgency. Look for these signals: short, fragmented working periods; repeated restarts after meetings; long email threads that spawn new tasks; and rising time spent in reactive meetings. Map those signals to context: are interruptions coming from outside your team (clients, customers), inside (peers, managers), or from legacy process (manual escalations, unclear SLAs)? Use that map to choose the right next reading: if attention splits between high-value tasks and reactive work, read the Deep Work vs Shallow Work Psychology guide; if multitasking and leftover attention slow progress, read Attention Residue and Multitasking. This page assumes you want practical moves after you've identified the pattern.
List where interruptions originate (external, internal, process).
Track your longest uninterrupted block and average fragment length.
Pick a guide next: deep-work patterns or attention-residue fixes.
Part 2
Diagnostic: separate similar-looking problems so you fix the right thing
Not every loss of focus is the same. Three common patterns look similar but need different responses. Pattern A: high meeting load but predictable scheduling - the problem is poor meeting design and calendar hygiene. Pattern B: unpredictable external requests - the issue is intake and escalation rules. Pattern C: mixed-day role expectations - the solution is role partitioning or protected maker time. To identify your pattern, run two simple checks for a week: (1) log the source and urgency of each interruption, (2) mark whether work resumed in under 5 minutes or required a warm-up. If interruptions are frequent but low-urgency, team-level protocols will help. If interruptions are urgent and client-driven, redesign intake and set clear SLAs. Use this separation to pick targeted fixes rather than blanket focus hacks.
Log interruption source and perceived urgency for five workdays.
Measure how long it takes to resume productive work after each break.
Match pattern A/B/C to meeting, intake, or role solutions.
Part 3
Playbook: team-level moves and decision routines to protect blocks
Team systems change the environment so individuals don't have to rely on willpower. Start with a simple interrupt protocol: define three urgency tiers and required channels (e.g., urgent by phone, important by dedicated Slack channel, routine by task system). Block shared focus windows-two-hour maker blocks on team calendars-with a light "do not disturb" tag and a visible fallback contact for emergencies. Trim meeting load with a 4-question pre-meeting checklist: objective, required attendees, decision needed, and pre-read. Establish an intake SLA and a single intake point for requests to prevent reactive splintering. Use weekly retrospectives to adjust thresholds and track whether blocked hours actually became focused time. These are decision routines: choose the tier, commit calendar blocks, and enforce intake rules for at least one full sprint to test impact.
Create a 3-tier interruption protocol with explicit channels.
Reserve shared two-hour focus blocks and a single emergency contact.
Use a pre-meeting checklist to prune unnecessary meetings.
Part 4
Playbook: individual routines and re-entry tactics that reduce context switching
Individuals need concise decision rules that make returning to focus predictable. Use a three-part re-entry checklist: (1) capture what changed during the interruption, (2) set a 10-minute restart task, and (3) schedule the next uninterrupted block before doing small reactive items. Batch quick replies into two daily inbox sessions and set an auto-response for working blocks that tells senders when you'll reply. Adopt a default calendar pattern (e.g., 90/30: 90-minute deep blocks, 30-minute reactive windows) and guard the pattern with a visible signal on your status. For meeting-heavy days, use micro-blocking: made-up 25-45 minute focus sprints in gaps and log outcomes to reduce attention residue. These routines reduce the cognitive cost of switching and make deep work a predictable part of the week.
Use a 3-step re-entry checklist after any interruption.
Batch inbox time and set status auto-responses during focus blocks.
Adopt a repeatable block pattern (example: 90/30) and defend it visibly.