REALITYWIPE

OLD SCRIPT DETECTED

My piece got fewer clicks than theirs — I misjudged the story

Try this response:

The dashboard shows distribution, not the reason the story deserved to run.

Take the 60-second self-check

SEE THE PRACTICE

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

THE THOUGHT

My piece got fewer clicks than theirs — I misjudged the story

YOUR RECORDED RESPONSE

The dashboard shows distribution, not the reason the story deserved to run.

ONE PRIVATE MOVE

Open the analytics for the piece once, then write two short notes in a private file: “what this number can show” and “what it cannot show.” Close the file and leave it there for later.

When the dashboard makes the call

The refresh after publish

You’ve barely had time to close the tab before the analytics start pulling at you. The byline is live, the Slack thread has moved on, and your eyes go straight to the numbers beside your piece. Then a colleague’s story rises above yours, and the thought arrives fully formed: my piece got fewer clicks than theirs — I misjudged the story.

Choosing safer stories

After that, the day gets narrower. You reread your pitch notes and start trimming anything that feels uncertain, expensive, or slow to explain. You find yourself steering toward familiar angles because they look easier to defend in a report. The cost is quiet: you spend more time trying to predict the reaction than deciding what actually deserves coverage.

A number you can test

Before you treat the gap as a verdict, look at the piece the way a desk editor would: topic, placement, headline, timing, audience, all the things that shape distribution without changing whether the story mattered. Then write one line on paper or in notes: what the clicks measured, and what they did not. Keep it visible for the next refresh.

TRACE · 01/04

How this script runs you

  • You check the analytics soon after publication, then let a colleague’s higher number sit in your head like a correction.
  • A lower-performing piece starts to feel like evidence that your judgment was off, not just that the audience moved differently.
  • You begin choosing pitches for their clickability, even when your first instinct was to cover something less obvious.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Metrics Verdict

The private rule is: if your story gets fewer clicks than someone else’s, your editorial judgment failed. That turns distribution into a verdict on taste, timing, and worth, so every refresh feels like a review of you.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • The dashboard shows distribution, not the reason the story deserved to run.
  • Their higher number is about audience behavior, not a ranking of my judgment.
  • I can note what the clicks reflect without letting them decide the story’s value.

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 piece got fewer clicks than theirs — I misjudged the story

I say

The dashboard shows distribution, not the reason the story deserved to run.

Then I do one thing

Open the analytics for the piece once, then write two short notes in a private file: “what this number can show” and “what it cannot show.” Close the file and leave it there for later.

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 piece got fewer clicks than theirs — I misjudged the story". 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

If my colleague’s piece did better, isn’t that still useful feedback?

It can be useful feedback about framing, timing, or audience fit. The trap is turning it into a statement that you misjudged the story itself. Those are different questions, and they lead to different next steps.

What if I keep wanting to rewrite my pitch after seeing the numbers?

That urge makes sense when the dashboard feels final. Try separating the pitch question from the performance question. A story can be worth assigning even if its first round of clicks is lower than another piece on the same day.

Do I have to ignore analytics to stop feeling this way?

No. The point is to stop using them as the only proof of editorial judgment. Looking once, naming what the metric does and doesn’t say, and then returning to the work is enough to create a little distance.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script