QUIET
Quiet signal
“My calendar looks too empty to be working” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “A quiet grid can still hold a full day of real work — it isn't the entire record.”
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 “My calendar looks too empty to be working”, including the private rule underneath it: If my calendar grid isn't visually as packed as my teammates', the day I actually had doesn't count as work — so the grid itself has to look busy, not just the work have gotten done.
QUIET
“My calendar looks too empty to be working” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “A quiet grid can still hold a full day of real work — it isn't the entire record.”
PRESENT
“My calendar looks too empty to be working” wins some small decisions before you catch it. Your useful interruption is: “I don't need to invent blocks to prove hours happened.”
ACTIVE
“My calendar looks too empty to be working” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: Before checking how full today's calendar looks, write on paper the tasks you actually finished — then compare the list to the grid privately, no edits or sends.
DOMINANT
Right now, “My calendar looks too empty to be working” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: Before checking how full today's calendar looks, write on paper the tasks you actually finished — then compare the list to the grid privately, no edits or sends.