REALITYWIPE

OLD SCRIPT DETECTED

I’ll just redo it myself instead of pointing it out

Try this response:

Rebuilding their deck teaches them nothing except that I'll always catch it before it ships.

Take the 60-second self-check

SEE THE PRACTICE

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

THE THOUGHT

I’ll just redo it myself instead of pointing it out

YOUR RECORDED RESPONSE

Rebuilding their deck teaches them nothing except that I'll always catch it before it ships.

ONE PRIVATE MOVE

Before you open their file to fix it, write the one sentence you'd say about what's wrong in a private note — don't send it, just see if it exists.

The Client Deck You Rebuilt at 11 PM Instead of Sending One Note

The Rewrite Feels Like MercyTheir draft lands in your inbox at 6pm — slide seven buries the client's actual ask under three tangents, and the numbers on slide nine don't match the appendix. You open the file instead of Slack. By 11pm you've quietly rebuilt four slides, save it back under the same filename, and tell yourself you did them a favor by not making a thing of it. Nobody had to feel corrected. The deck just got better overnight, as if on its own.

Why Silent Repair Outranks the SentenceNaming the fix out loud risks something a keystroke doesn't: their face when they hear it, the chance it lands wrong, the version of you that seems hard to work for. Redoing it yourself skips all of that — no reaction to manage, no relationship to repair afterward. But they never learn slide seven was the actual problem, so next week's draft has the same gap, and you've quietly signed up to keep rebuilding decks at 11pm indefinitely.

The Sentence You Write But Don't SendNext time you reach for their file, stop before you touch it. Open a private note and write the one sentence you'd say if you were going to say it — 'Slide seven needs the client's ask up top, not buried in paragraph three.' Don't send it. Just check whether that sentence exists in under a minute. If it does, the redo wasn't the only option available to you tonight — it was the one that felt safer.

TRACE · 01/04

How this script runs you

  • You retype someone else's slide or paragraph at your desk rather than tell them what to change in it.
  • Their file gets quietly 'fixed' overnight with no record they'll ever see what was actually wrong.
  • You've opened their draft three nights running to correct it yourself instead of sending one line about it.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Feedback Dodge

If I quietly redo the work myself, the outcome improves without anyone — including me — having to sit through the discomfort of a correction being said out loud.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • Rebuilding their deck teaches them nothing except that I'll always catch it before it ships.
  • One sentence about slide seven costs less than four hours of quiet rewriting.
  • I can name the fix without deciding I have to be the one who makes it.

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

I’ll just redo it myself instead of pointing it out

I say

Rebuilding their deck teaches them nothing except that I'll always catch it before it ships.

Then I do one thing

Before you open their file to fix it, write the one sentence you'd say about what's wrong in a private note — don't send it, just see if it exists.

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: "I’ll just redo it myself instead of pointing it out". 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 redoing it myself genuinely is faster than explaining what's wrong?

It's often faster this one time — that's not in question. What it doesn't do is change next week's draft, because the person never learns which specific thing to fix, so the same gap resurfaces and you redo it again.

What if I've already rewritten their work quietly several times without saying anything?

A pattern doesn't need to be undone all at once. The next file is a clean starting point — you can name what you'd change in the next one without addressing every earlier silent rewrite first.

Does quietly fixing their draft count as looking out for them?

It protects the document, not the person's ability to produce a better one next time. Looking out for them and rescuing the deliverable are two different acts, even though redoing it can feel like both at once.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script