REALITYWIPE

OLD SCRIPT DETECTED

If it's not perfect, it's worthless

Try this response:

Done is data. Perfect is a hiding place.

Take the 60-second self-check

SEE THE PRACTICE

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

THE THOUGHT

If it's not perfect, it's worthless

YOUR RECORDED RESPONSE

Done is data. Perfect is a hiding place.

ONE PRIVATE MOVE

Open one unfinished project, circle or highlight a single imperfection, and then write a one-sentence note at the top that says what makes it usable as-is. Stop there and close it without further editing.

The Margin Where It Never Gets Released

  1. 01 / The tiny flaw you can’t stop seeing

    It starts when you notice one uneven line, one awkward sentence, one corner that feels a little off. The rest of the work may be solid, but that small imperfection becomes the only thing you can see. In that moment, “If it's not perfect, it's worthless” turns the whole piece into a test you’re about to fail.

  2. 02 / Why the unfinished version feels safer

    So you keep adjusting. You rename, reshuffle, re-read, reformat, and convince yourself that one more pass will make it safe to show. The relief is real: as long as it stays unfinished, no one can judge the work as a whole. But the cost is that projects sit at 90% while the last stretch quietly becomes the part that feels most exposed.

  3. 03 / The pause before the next revision

    Next time you catch yourself hunting for the flaw, pause before you edit. Put a small mark in the margin, close the file, and write one line: “This is usable even if it is not flawless.” Then choose the smallest version that could exist without more polishing. The interruption is not approval; it is the moment you stop treating imperfection as proof of worthlessness.

TRACE · 01/04

How this script runs you

  • A draft can look nearly finished and still feel unusable because one detail is out of place.
  • You may keep polishing long after the useful part is done, because a visible flaw feels like a verdict.
  • Feedback can feel less like notes and more like a record of failure, which makes it easier to hide the work than revise it in front of anyone.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Perfection Prison

If the result has any visible flaw, it cannot count as real work. It has to be flawless to deserve being seen, kept, or shared, so anything less becomes evidence against you.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • Done is data. Perfect is a hiding place.
  • I can leave this at usable and let it be imperfect.
  • This draft can be enough for now, even if it is not my final standard.

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

If it's not perfect, it's worthless

I say

Done is data. Perfect is a hiding place.

Then I do one thing

Open one unfinished project, circle or highlight a single imperfection, and then write a one-sentence note at the top that says what makes it usable as-is. Stop there and close it without further editing.

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: "If it's not perfect, it's worthless". 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

Why does a small mistake make the whole thing feel ruined?

Because the hidden rule turns one flaw into a total judgment. The work stops being a draft with a rough spot and starts feeling like evidence that the whole effort was never good enough.

Why do I keep polishing instead of finishing?

Polishing delays exposure. While the work is still in progress, it stays private and open-ended, which can feel safer than letting it become something fixed that could be evaluated.

What if I really can see obvious problems?

Noticing problems does not mean the work is worthless. It means the piece has a next step. The interruption is to separate “needs revision” from “has no value,” so usable work is not buried under the demand for perfection.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script