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 “A good engineer doesn't need recovery time after switching contexts”, including the private rule underneath it: A capable engineer maintains perfect focus through interruptions and never needs time to reorient. If I require recovery time, I'm not operating at the level I should be.
QUIET
“A good engineer doesn't need recovery time after switching contexts” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “I block recovery time as if it's a meeting—because rebuilding context is real work, not downtime.”
PRESENT
“A good engineer doesn't need recovery time after switching contexts” wins some small decisions before you catch it. Your useful interruption is: “When the interrupt happens, I note the time it takes to get back to full focus; that data belongs in my calendar.”
ACTIVE
“A good engineer doesn't need recovery time after switching contexts” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: In your calendar for next week, add fifteen-minute 'context recovery' blocks after every meeting. Make them private. At the end of the week, notice whether blocking them changed your actual time on deep work.
DOMINANT
Right now, “A good engineer doesn't need recovery time after switching contexts” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: In your calendar for next week, add fifteen-minute 'context recovery' blocks after every meeting. Make them private. At the end of the week, notice whether blocking them changed your actual time on deep work.