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 editor only brings up a story when the numbers are good”, including the private rule underneath it: The rule underneath this thought: an editor's attention is the only proof a story counted, so if the message doesn't come, the reporting itself must have missed the mark.
QUIET
“My editor only brings up a story when the numbers are good” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “My editor's silence is a gap in the workflow, not a verdict on the story.”
PRESENT
“My editor only brings up a story when the numbers are good” wins some small decisions before you catch it. Your useful interruption is: “A message about numbers is about numbers. My reporting call is a separate question.”
ACTIVE
“My editor only brings up a story when the numbers are good” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: Open your last three published pieces and write one sentence under each naming the actual reason you reported it, independent of any reaction it got.
DOMINANT
Right now, “My editor only brings up a story when the numbers are good” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: Open your last three published pieces and write one sentence under each naming the actual reason you reported it, independent of any reaction it got.