REALITYWIPE

OLD SCRIPT DETECTED

One more revision won't hurt — I don't want to seem difficult

Try this response:

This revision is already doing what was asked.

Take the 60-second self-check

SEE THE PRACTICE

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

THE THOUGHT

One more revision won't hurt — I don't want to seem difficult

YOUR RECORDED RESPONSE

This revision is already doing what was asked.

ONE PRIVATE MOVE

On a scrap note or in a private document, list the last three revisions on a project and put a box beside each one that says either 'original ask' or 'extra.' Do not send it; just see how often 'one more' was actually another request.

The last small tweak that never feels small

The polite person who never asks for moreYou tell yourself this is just the courteous thing to do. One more revision, a tiny color shift, a softer headline, a little rearranging of the sections — nothing dramatic. If you keep the tone easy and agreeable, the project stays smooth and you stay easy to work with. The hidden myth is simple: being flexible proves you are the kind of person clients want.

Why the small ask keeps getting biggerThe trouble is that the work already comes with a script. In spec work and scope creep, free extra effort gets treated like a preview of what you’ll always do. The more you absorb without naming it, the more the request feels normal — not because it is, but because you made it look painless. That makes the next 'tiny' revision arrive dressed as common sense.

A ten-minute test with no audienceOpen the current project notes or a blank document and write three lines only: what was asked for, what has already been revised, and what would count as a new request. Then mark one item as 'outside the original ask' without sending it anywhere. You are not proving a theory; you are checking whether the word difficult is doing more work than the actual scope.

TRACE · 01/04

How this script runs you

  • You keep adjusting a deliverable after the agreed version is already usable, because stopping feels like making a scene.
  • A client’s hesitation about your rate makes you offer an extra change before they even ask, just to stay agreeable.
  • You call the next added detail 'small' even when it takes real time, because naming it as extra feels uncomfortable.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Spec Work Trap

If you stay easy, flexible, and available for just a little more, nobody will label you difficult, and the project will keep moving without friction. The private cost is that your unpaid extras become the proof of your value instead of the work you agreed to do.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • This revision is already doing what was asked.
  • If this is new work, I can name it as new work.
  • I don't have to absorb every extra detail to stay pleasant.

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

One more revision won't hurt — I don't want to seem difficult

I say

This revision is already doing what was asked.

Then I do one thing

On a scrap note or in a private document, list the last three revisions on a project and put a box beside each one that says either 'original ask' or 'extra.' Do not send it; just see how often 'one more' was actually another request.

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: "One more revision won't hurt — I don't want to seem difficult". 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 I really do want the relationship to stay easy?

You can keep the relationship easy without making every added request invisible. Quietly naming what is extra is different from arguing. The point is not to become rigid; it is to stop treating unlimited flexibility as the price of being decent.

But some revisions are normal, aren’t they?

Yes — and that is exactly why this thought slips in so easily. Normal revisions become a problem when 'normal' starts covering work that was never part of the original agreement. The distinction is not whether a change exists, but whether you keep folding it in for free just to avoid discomfort.

Why does 'difficult' feel so charged here?

Because in this thought, difficult is not about behavior; it is about being seen as inconvenient. The fear is that naming scope will make you sound demanding, even when you are only describing what changed. That fear makes silence feel polite and extra labor feel safer than clarity.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script