QUIET
Quiet signal
“Meetings are killing my productivity” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “A meeting and a shipped feature aren't competing for the same scoreboard.”
SCRIPT CHECK · 60 SECONDS
“Meetings are killing my productivity”
See what this thought is changing.
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.
What this self-check measures
This is not a diagnosis and there is no pass or fail. It measures the current frequency, credibility, and behavioral cost of “Meetings are killing my productivity”, including the private rule underneath it: If a block on your calendar isn't spent producing code, it counts as a loss against your worth as an engineer, no matter what the meeting actually accomplished or unblocked for the team.
See all result bands
PRESENT
Present in the background
“Meetings are killing my productivity” wins some small decisions before you catch it. Your useful interruption is: “I plan for the slow twenty minutes after a meeting instead of expecting to snap back instantly.”
ACTIVE
Active pattern
“Meetings are killing my productivity” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: Tonight, look at tomorrow's calendar and write next to each meeting one thing it's actually deciding or unblocking.
DOMINANT
Getting the final word
Right now, “Meetings are killing my productivity” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: Tonight, look at tomorrow's calendar and write next to each meeting one thing it's actually deciding or unblocking.