Distraction Tracker

A senior software engineer recently promoted to tech lead who reports being pulled in multiple directions throughout the day. They're frustrated that they can't complete coding tasks like before and feel like they're failing at both individual contribution and leadership. They attribute this to poor time management skills.

Frame this as data collection before building systems. 'Before we design interruption boundaries, let's see what's actually pulling you away from code.' Many new tech leads resist tracking because they think they should just power through distractions. Name that upfront: 'This isn't about working harder - it's about seeing whether these interruptions are leadership work or just noise.'

Notice if they log only the interruptions that feel illegitimate (Slack pings, random questions) but skip the ones that feel like leadership duties (code reviews, helping junior developers). This selective logging means they're still trying to be an individual contributor who happens to lead, not a leader who codes.

Start with the internal versus external split. 'Read me three external triggers.' Then ask: 'Which of these interruptions were people coming to you because you're the tech lead?' This separates role-appropriate interruptions from boundary issues. The question that opens it up: 'What would happen if you scheduled the legitimate interruptions instead of letting them be random?'

A marketing director at a mid-size company who completed the tracker with detailed entries, accurate time estimates, and thoughtful avoidance strategies. When reviewing the data, they discuss it analytically but show no frustration, surprise, or concern about losing 2-3 hours daily to distractions. They want to 'optimize their workflow.'

Present as a reality check, not an optimization exercise. 'This tracker often shows people something they didn't expect about where their time actually goes.' Don't oversell the insights - this client will comply with any framing you give them. Instead, watch for whether the data creates any genuine reaction or just more analysis.

Perfect completion with no emotional response signals intellectual compliance rather than genuine engagement. Look for entries that are too clean - 'Email notification, 15 minutes, external trigger, batch email checking.' Real distraction tracking is messier. If every avoidance strategy is reasonable and actionable, they're performing competence.

Skip asking what they noticed - they'll give you a summary. Instead, start with: 'Show me the entry that surprised you most.' If nothing surprised them, that's the conversation. Ask: 'What would have to show up in this tracker for you to be concerned?' This moves from analysis to actual stakes.

An executive assistant to a C-suite leader who reports being constantly distracted and unable to complete important tasks. They're concerned about their performance review and want better focus strategies. They describe their role as 'putting out fires all day' and feel overwhelmed by competing priorities.

Frame as a diagnostic before building focus strategies. 'Before we work on concentration techniques, let's see what's actually competing for your attention.' Expect resistance to logging internal triggers - many EAs are trained to see all interruptions as legitimate parts of their job. Say: 'We're not judging the interruptions, just mapping them.'

Look for patterns where internal triggers correlate with specific types of tasks. If 'boredom' or 'anxiety' appears when they're supposed to be doing strategic planning or project management, but external triggers dominate during administrative tasks, they may be unconsciously avoiding the higher-level work their role requires.

Start with the internal trigger entries. 'Walk me through Tuesday afternoon when you logged anxiety as the trigger.' Don't ask what they were avoiding - ask what they were supposed to be working on. The question that opens this: 'What would your executive say is the most important part of your job that isn't getting done?'

An independent consultant with ADHD who struggles with project time estimates and client boundaries. They report losing entire afternoons to distractions but can't pinpoint where the time goes. They're concerned about missing deadlines and want to improve their time awareness for better client communication.

Present as a calibration tool for time awareness, not just distraction management. 'ADHD brains often experience time differently than neurotypical ones. This tracker helps calibrate your internal clock against actual time.' Acknowledge that time estimation will be hard initially: 'Most people with ADHD underestimate distraction time by 50-70% in the first week.'

Time estimates that are consistently too low (logging 10 minutes for what was likely 30) or entries where they can't estimate at all. Also watch for hyperfocus episodes logged as distractions - they may label a 2-hour deep dive into research as 'getting distracted' when it was actually productive, just unplanned.

Start with the time column, not the distraction column. 'Pick three entries where you wrote down a time estimate. How confident are you in those numbers?' Then: 'Which distractions felt like 10 minutes but were probably longer?' The opening question: 'What would change about your client communication if you knew your real distraction recovery time?'