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 “If I don't touch it, it will break”, including the private rule underneath it: If my hands leave the controls—the work, the decisions, the verification—the system breaks. My absence is the failure mode. The only way to guarantee it doesn't break is to never stop touching it. Stepping back isn't trust; it's…
QUIET
“If I don't touch it, it will break” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “If it breaks without me watching, I didn't build it right. That's a design problem to fix, not a reason to never leave.”
PRESENT
“If I don't touch it, it will break” wins some small decisions before you catch it. Your useful interruption is: “My fried judgment during a sleepless week costs more than a system that works without me monitoring it.”
ACTIVE
“If I don't touch it, it will break” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: Write down, in plain language, exactly what you check when you review delegated work. Then spend ten minutes asking: which of these checks could live in a test, a document, or a runbook instead of in your hands?
DOMINANT
Right now, “If I don't touch it, it will break” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: Write down, in plain language, exactly what you check when you review delegated work. Then spend ten minutes asking: which of these checks could live in a test, a document, or a runbook instead of in your hands?