External Triggers Tracker

A senior developer with ADHD who thrived during three years of remote work is now required to be in-office three days per week. They report their productivity has dropped significantly and they're struggling to complete tasks that were routine at home.

Frame this as environmental forensics, not self-improvement. 'Your home setup worked. The office doesn't. Let's figure out exactly what changed so we can address the specific problems, not just cope better.' Many developers resist tracking because they want technical solutions, not behavioral data. Acknowledge this: 'We're collecting requirements for your environment the same way you'd gather requirements for code.'

Completion patterns reveal adaptation strategies. If most entries are office-based with few home entries, they're unconsciously avoiding the comparison. If entries focus on obvious triggers (noise, interruptions) but skip subtle ones (lighting, air quality), they're working from assumptions rather than observation. Watch for technical language that distances them from the emotional impact.

Start with the contrast between environments, not the problems. 'Read me your home entries versus office entries.' Then focus on the 'What I Could Do Differently' column - this is where their problem-solving instincts engage. The question that typically opens this up: 'Which of these triggers could you solve with equipment, and which require negotiating with people?'

A marketing manager with undiagnosed ADHD believes their focus problems stem from weak discipline and time management skills. They've tried multiple productivity systems without success and are convinced they need better organizational tools, not environmental changes.

Present this as data collection for their productivity system optimization. 'Before we design your next time management approach, let's see what's actually interrupting the systems you already have.' Expect resistance to the ADHD framing. Don't lead with executive function language - let the data speak first. 'Track what breaks your focus, regardless of why you think it happens.'

Self-blame language in the 'How It Affected Me' column signals they're pathologizing normal ADHD responses. Entries like 'I let myself get distracted' or 'I should have ignored it' indicate they're fighting their neurology rather than working with it. If the 'What I Could Do Differently' column focuses on willpower solutions ('try harder to ignore'), they're not engaging with environmental modification.

Start with the patterns, not the individual incidents. 'You have seven entries about notification interruptions and five about noise. What do you notice about the timing?' Avoid ADHD language initially. The question that typically creates the shift: 'If someone else had these same triggers in this same environment, what would you recommend they change about their setup?'

An operations director reports constant interruptions are destroying their ability to focus on strategic work. They believe the solution is better time blocking and communication protocols, but their team continues to interrupt for urgent issues that seem to require their immediate input.

Frame this as operational diagnosis, not personal productivity. 'You're getting interrupted because your team needs something from you. Let's figure out what they actually need versus what they think they need.' Most senior leaders resist tracking interruptions because it feels like micromanaging their own day. Reframe: 'This is about designing systems, not monitoring behavior.'

The 'What I Did' column reveals their current boundary patterns. If they consistently respond immediately to all interruptions, they're training their team to interrupt. If entries show the same people interrupting for similar issues repeatedly, the problem is systemic, not environmental. Watch for language that positions them as indispensable - 'only I can handle this' indicates role boundary confusion.

Start with the repeat patterns, not the individual interruptions. 'Sarah interrupted you four times this week about client escalations. What does that tell you about how escalation decisions are currently structured?' Then move to the systemic view. The question that typically opens this: 'Which of these interruptions happened because someone didn't know the answer, and which happened because they weren't authorized to act on the answer they already knew?'

An independent consultant with ADHD works at different client locations each week and reports wildly inconsistent productivity. Some sites allow deep focus while others make concentration nearly impossible, but they can't identify why or predict which environments will work.

Position this as site assessment for professional performance. 'You're essentially A/B testing different work environments every week. Let's capture that data systematically so you can predict and prepare.' Most consultants resist detailed tracking because it feels like overhead. Emphasize the business case: 'This data helps you deliver consistent quality regardless of client environment.'

Location-specific patterns emerge quickly with this client type. If certain client sites generate multiple entries while others generate none, the contrast is the data. Watch for entries that blame the client environment without noting what they could control - this suggests learned helplessness about environmental factors. Completion consistency across different sites also indicates engagement level.

Start with the site comparison, not individual triggers. 'You have six entries from the downtown office and zero from the suburban site. Walk me through what's different about those environments.' Then focus on portable solutions. The question that opens this: 'Looking at your most productive sites, what elements could you recreate or request at the problematic locations?'