Distraction Management Plan

A senior analyst who works in an open-plan office three days a week and from home two days. She complains extensively about office noise and interruptions and believes remote work is where she does her best thinking - but her manager has noted that deadlines are missed equally on home days. She hasn't connected the pattern.

Frame this as an attention-mapping exercise rather than an environment critique. 'Before we talk about what to change, let's inventory what's actually pulling your attention - both in the office and at home.' The resistance here is attribution: she's certain the problem is the office. Don't contradict that yet. 'Let's see what the inventory shows for both environments.' The parallel distraction pattern will surface through the tool itself, which is more useful than you naming it.

Watch whether she populates the distraction inventory differently for each environment or uses the same categories. If the categories are identical (notifications, colleague interruptions, mental drift), the environment isn't the variable. Also watch the 'Pattern' column: if she can't identify patterns and writes 'whenever' for every entry, she hasn't yet distinguished between predictable and unpredictable distractions - which have completely different response strategies.

Start with the comparison. 'Looking at both environments, what do you notice about what the distractions have in common?' Let her find the pattern rather than naming it yourself. Then move to controllability: 'Which of these items are within your control to change, and which require someone else to change?' The question that creates movement: 'What's one thing you could test this week that doesn't require the office environment to change?'

A operations manager who has told his team, 'my door is always open,' both literally and as a cultural signal. He is proud of his accessibility and considers it a leadership strength. He also complains that he never has time for strategic thinking. These two facts coexist without tension in his mind.

Frame this as a data-collection step before any change conversation. 'Let's inventory what's actually interrupting you and when, before we decide whether anything needs to change.' Don't challenge his open-door policy directly - he's emotionally invested in it. The distraction log will surface the pattern. 'Knowing what's pulling your attention is different from deciding what to do about it.' That framing gives him permission to be honest without feeling defensive.

Watch the frequency and source columns. If team-initiated interruptions dominate his log and cluster around certain question types (status updates, approval requests, simple information), that's structural - his team hasn't been empowered to operate without him. If the interruptions are scattered and varied, the pattern may be different. Also watch whether he logs his own self-interruptions: clients with high accessibility often also self-interrupt frequently, which the open-door attribution obscures.

Start with the frequency. 'How many interruptions in a typical day? What percentage came from your team versus other sources?' Then move to type: 'Of the team interruptions, how many were things you could have anticipated and prevented versus genuinely unexpected?' The question that creates movement: 'If your team needed to operate without you for a full day, what would need to be true for that to work?' That question tends to surface both the team capability gaps and his own availability dependency.

A senior project manager who prides herself on handling multiple threads simultaneously. She considers multitasking a skill and cites her ability to context-switch as a competitive advantage. Her work quality has started showing minor but increasing errors, which she attributes to 'the volume,' not to the switching pattern.

Frame this as an attention audit, not a multitasking critique. 'We're going to log where your attention actually goes, not as an evaluation, but as data.' Clients who identify with high-performance multitasking are usually willing to engage with data they generate themselves. Avoid any suggestion that multitasking is inherently problematic - that triggers defensiveness. 'Let's see what your attention pattern looks like on paper before drawing any conclusions.'

Watch the switching frequency column specifically. If she's tracking 8-12 context switches per hour, the cost of that pattern becomes quantifiable. Watch also the 'Impact on Task' column: high-performing multitaskers often downgrade the impact of each switch ('minor interruption,' 'quick pivot') which cumulatively understates the real cost. Also watch whether she notices any correlation between task-switching days and the types of errors she's been producing.

Start with the data summary. 'What do you notice about the pattern?' Let her read her own numbers. Then move to cost: 'If each context switch costs you 10-15 minutes to re-orient - which is what the research shows for complex tasks - what does a 10-switch day actually cost?' The question that creates movement: 'Which of these switches were necessary versus ones that felt urgent but could have waited 90 minutes?'