SCRIPT CHECK · 60 SECONDS
Five quick questions show how often it appears, how believable it feels, and what it makes you avoid. You’ll get one private next step.
This is not a diagnosis and there is no pass or fail. It measures the current frequency, credibility, and behavioral cost of “I still flinch when someone says 'can we talk about last Tuesday's deploy'”, including the private rule underneath it: If someone wants to 'talk about' a specific deploy by name, the conversation is already a verdict on me, so I have to be fully rehearsed before it starts or I'll be caught unprepared for blame that hasn't actually been assigned.
QUIET
“I still flinch when someone says 'can we talk about last Tuesday's deploy'” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “Someone wanting to talk about Tuesday's deploy is a question, not a verdict I have to pre-answer.”
PRESENT
“I still flinch when someone says 'can we talk about last Tuesday's deploy'” wins some small decisions before you catch it. Your useful interruption is: “I can reply 'sure, what's up' without drafting a defense first.”
ACTIVE
“I still flinch when someone says 'can we talk about last Tuesday's deploy'” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: Privately reopen last Tuesday's deploy ticket and count how many names are on the approval list besides yours.
DOMINANT
Right now, “I still flinch when someone says 'can we talk about last Tuesday's deploy'” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: Privately reopen last Tuesday's deploy ticket and count how many names are on the approval list besides yours.