You turn it over for two hours — "why do I come across that way? I've told them repeatedly to come to me anytime" — and land on an explanation that feels good: "I'm probably just busy and they're being considerate." Ask "why" and you always get an explanation, never data.
Go to three people (a direct report, a peer, someone a level down). Use a fixed script: "I got a piece of feedback that I'm hard to approach. I don't want your overall assessment — I want one specific moment. The last time you meant to come to me and didn't: what was I doing, and what did you see that made you decide not to?"
What you may get back: "Last Tuesday you had headphones on. I stood in your doorway for two seconds, you glanced up and looked back down." That is actionable data. "You're a bit hard to approach" is not.
Name one person who cares enough about you to say the uncomfortable thing, and make the authorization explicit: "When you see me do X, tell me on the spot — no waiting for a good moment, no preamble. I won't hold it against you." The first time they actually do it, your reaction decides whether the mechanism survives a month.
Action: This week, ask three people for one specific moment each, using the fixed script. Record only — don't explain yourself.
Reflection: If your team had to give you a label you'd never give yourself, which one would it be?
Translate it into performance language: "He's too focused on performing, light on real delivery." Then take him down half a level in calibration. That sentence is unfalsifiable and requires no evidence — which is exactly why nothing stops it.
1. Rate the intensity: "My irritation is 8/10. The actual damage he causes is 2/10 — the extra 6 points are mine."
2. Find the mirror: "I was raised on 'do it first, talk later,' and filed 'visibility' under undignified. He is doing exactly what I don't allow myself to do."
3. Strip out the real issue: what's left is that his updates consume too much bandwidth in the main channel. So the sentence becomes: "Your progress updates are valuable, but the frequency in the main channel is too high — one weekly digest there, details in the project channel. Workable?" Actionable, contestable, no verdict on his character.
In a 1:1: "I overreact when requirements change on me mid-flight — that's not about you. If you see my speech speed jump, say it straight: 'your reaction is running hot right now.' I won't hold it against you. That's a permission I'm giving you."
Action: Run the intensity-gap check on the report who irritates you most, strip out the "extra points," then write the feedback.
Reflection: The character word that shows up most often in your assessments — could you produce behavioral evidence for it on demand?
Counterattack: "We've checked these numbers three times; if you don't believe them, look at the dashboard yourself." — the next 40 minutes go to litigating data integrity, and the resources you actually came for never get mentioned.
Capitulation: "Sorry, I'll go back and re-verify." — three months of your team's work, withdrawn by you in one sentence.
1. Label it (to yourself, 1 second): "This is shame triggered by being questioned in public — it isn't a data problem." Naming an emotion lowers its intensity (affect labeling; Lieberman et al., 2007, Psychological Science).
2. Buy time (3 seconds): take a sip of water. Its only function is to open those three seconds, and it's completely unremarkable in a meeting.
3. Deliver the pre-written line: "Which definition are you pointing at? If it's the dedup rule, we use X and we can open it right now; if it's the sample window, I'll grant that it only covers six weeks. Tell me which one and we don't have to guess." — that converts a personal suspicion into a two-option technical question, and both options are ones you know cold.
Action: Write three response lines for being challenged, and stick them on the edge of your monitor.
Reflection: The last thing you said in a meeting and regretted — at what second did the trigger appear?
"Make sure you rest — no email on weekends" / "Do you want to take a couple of days off?" — that converts an environment problem into a personal one and implies his coping is defective. He won't raise it again.
"Let's not jump to fixes. I want to separate which kind this is: too much work to finish, or finishable but you don't think it matters, or finished but nobody notices, or you have no say in how it's done?" (He answers: "the last two.")
"Then time off won't fix it. Here's what I can move: control — next quarter the technical approach for this module is yours; I'll comment at architecture review and won't pre-set the direction. Reward — I never publicly attributed last quarter's migration to you. That was my failure; I'll say it at next week's all-hands and write it into your perf packet. Workload I can't move this year — headcount is frozen until Q4, and I won't pretend otherwise."
Action: Redo your last "I'm exhausted" conversation: locate it in the six cells, and say plainly which ones you can't move.
Reflection: If burnout is a reading on the environment, whom is your team's reading measuring?