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 “The new senior makes me redundant”, including the private rule underneath it: Ship speed is the ranking, and every teammate is a row above me. The 10x-engineer myth came from studying toy tasks—most variance belongs to the task itself, not the person. But the scoreboard you're using measures neither the task…
QUIET
“The new senior makes me redundant” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “They built a new endpoint; I'm rebuilding infrastructure. Different tasks, different time signatures.”
PRESENT
“The new senior makes me redundant” wins some small decisions before you catch it. Your useful interruption is: “My refactor will save the team months of maintenance. Their merge was fast because the path was clear.”
ACTIVE
“The new senior makes me redundant” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: List three tasks you've shipped in the past month. For each one, note what constraints or dependencies made it take the time it took. Do not compare it to any other person's work. Just name the constraint.
DOMINANT
Right now, “The new senior makes me redundant” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: List three tasks you've shipped in the past month. For each one, note what constraints or dependencies made it take the time it took. Do not compare it to any other person's work. Just name the constraint.