QUIET
Quiet signal
“Who am I to question the staff engineer” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “Their title doesn’t make the diagram correct.”
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 “Who am I to question the staff engineer”, including the private rule underneath it: The hidden rule is that seniority settles correctness: if someone outranks you, their design is presumed right, and your own read only counts after you can prove you deserve a seat in the conversation. That rule also turns silence into…
QUIET
“Who am I to question the staff engineer” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “Their title doesn’t make the diagram correct.”
PRESENT
“Who am I to question the staff engineer” wins some small decisions before you catch it. Your useful interruption is: “I can question the design without pretending I outrank anyone.”
ACTIVE
“Who am I to question the staff engineer” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: Take the diagram or notes you were looking at, circle one dependency or arrow that feels unclear, and write one private sentence underneath it: “This part needs another look because ___.” Keep it to yourself.
DOMINANT
Right now, “Who am I to question the staff engineer” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: Take the diagram or notes you were looking at, circle one dependency or arrow that feels unclear, and write one private sentence underneath it: “This part needs another look because ___.” Keep it to yourself.