REALITYWIPE

OLD SCRIPT DETECTED

My editor only brings up a story when the numbers are good

Try this response:

My editor's silence is a gap in the workflow, not a verdict on the story.

Take the 60-second self-check

SEE THE PRACTICE

Build a response for this thought—and one move to prove it.

THE THOUGHT

My editor only brings up a story when the numbers are good

YOUR RECORDED RESPONSE

My editor's silence is a gap in the workflow, not a verdict on the story.

ONE PRIVATE MOVE

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.

The Silence After the Jail-Intake Story

SCENE_01

The Three-Week File Nobody Mentioned

Tuesday, 9 a.m., you publish the county jail-intake piece you spent three weeks getting on the record. You refresh Slack. Nothing from your editor. By 11, a colleague's celebrity-divorce blurb is trending, and your editor DMs them a fire emoji and 'huge numbers today.' Your own thread stays quiet all afternoon.

SCENE_02

Reading the Silence as a Score

You start treating the DM as the real scoreboard: a message means the story counted, no message means it didn't. You keep half an eye on Slack after every push, and when you sketch next week's pitches, you catch yourself favoring the ones you think might earn a reaction over the intake-style story nobody will mention either way.

SCENE_03

What the DM Actually Tracks

The fire emoji comes from the traffic team's daily digest, which only flags same-day spikes — a three-week investigation with a slow, steady readership never triggers it, regardless of merit. Tonight, open your last three published pieces and write one line under each naming the actual reason you reported it. Read it back without opening Slack.

TRACE · 01/04

How this script runs you

  • You keep a mental tally of which stories got a Slack message from your editor and which got nothing.
  • A published piece met with silence starts to feel unfinished, like it's still waiting on a verdict.
  • When sketching next week's pitches, you catch yourself ranking ideas by whether they'd prompt a reaction.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Metrics Verdict

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.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • My editor's silence is a gap in the workflow, not a verdict on the story.
  • A message about numbers is about numbers. My reporting call is a separate question.
  • I can name why a story mattered without waiting for someone else to mention it first.

Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.

INSTALL · 04/04

The protocol, on one card

When I think

My editor only brings up a story when the numbers are good

I say

My editor's silence is a gap in the workflow, not a verdict on the story.

Then I do one thing

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.

STATUS: READY_TO_INSTALL

Wipe this thought

4 minutes. Your voice. Free.

Start this exact wipe in the app →

The wipe protocol
  1. Write the thought exactly as it plays: "My editor only brings up a story when the numbers are good". Word for word — the wipe targets the sentence, not the vibe.
  2. Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
  3. Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
  4. Run the loop: play it every morning and night, log one proof action a day for 7 days.

Straight answers

What if my editor genuinely only ever comments on the pieces that spike?

That would describe a communication habit, not an audit of your judgment. A pattern in what someone chooses to mention says more about their attention span for good news than about whether the quieter story was worth doing.

Should I track which stories get a Slack reaction and which don't?

You can notice you're doing it without turning it into evidence. The tally measures how often your editor happens to open a traffic dashboard that day, not how sound the reporting behind any single story was.

Is it wrong to still care whether a story performs well?

No — caring about reach is normal in the job. The distortion is letting one person's silence on a given day stand in as the only measurement of whether the story needed to exist in the first place.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script