REALITYWIPE

OLD SCRIPT DETECTED

It's faster to do it myself than to teach them

Try this response:

Doing it myself is faster once. Teaching it is faster every week after.

Take the 60-second self-check

SEE THE PRACTICE

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

THE THOUGHT

It's faster to do it myself than to teach them

YOUR RECORDED RESPONSE

Doing it myself is faster once. Teaching it is faster every week after.

ONE PRIVATE MOVE

Open your calendar from the past three weeks. Count how many evenings or weekends you spent finishing someone else's work. Compare that to how many conversations you had about why they sent it that way.

The 11pm Edit

You notice the first draft at 8pm

Priya has sent you the analysis—the one she spent three days on. You scan it. The logic is sound but she buried the insight in paragraph four. The formatting is loose. A client who moves fast will read the title and the first chart and miss what matters. You could send feedback and schedule a call for tomorrow, but the client needs it before their 10am board meeting. It's one hour of your time, maybe two. You pull it into your own editor.

By next month, the pattern owns your evenings

Priya has learned that the edits appear overnight. She stops workshopping her own drafts. Marcus, seeing what works, starts sending rougher code—he knows you'll polish it. Your calendar shows blocks labeled 'Review' but your 11pm is spent remaking. You tell yourself this is quality control. What you don't measure is the five people on your team who never learned what 'finished' looks like, and the three conversations you didn't have this week about their actual gaps. One of them gets passed over for the promotion you thought they'd get. You're not surprised—they're not ready. Somehow they stay not ready.

You let someone finish something badly and watch

Pick one piece of work—something with a deadline but not a crisis. Sit with the discomfort of imperfect output leaving your team's desk. Note what actually happens: does the work fail, or does it succeed differently? Did the person learn something from the unedited attempt, or did they wait for rescue? Document one fact about the gap between 'they finished it' and 'I would have done it better.'

TRACE · 01/04

How this script runs you

  • You "help" by redoing the work at 11pm, then wonder why nobody on the team grows.
  • A day spent unblocking five people feels wasted because nothing has your name on it.
  • Former peers get extra apologies and extra slack—you manage their comfort instead of the team.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Player Reflex

My value is what I personally produce—the team's output doesn't count as mine. The player reflex tells you that doing something yourself is a 1x time cost, but teaching takes infinite time. It doesn't count the cost of maintaining that imbalance: permanent dependence, atrophied capability in others, and your own ceiling staying exactly where it was.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • Doing it myself is faster once. Teaching it is faster every week after.
  • My output changed shape: it's the team's output now. Different unit, same work.
  • Their discomfort with my new role is theirs to process. Mine is to be fair, not invisible.

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

It's faster to do it myself than to teach them

I say

Doing it myself is faster once. Teaching it is faster every week after.

Then I do one thing

Open your calendar from the past three weeks. Count how many evenings or weekends you spent finishing someone else's work. Compare that to how many conversations you had about why they sent it that way.

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: "It's faster to do it myself than to teach them". 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 I don't redo their work, won't the client see that we're not excellent?

The client sees output, not effort. A person who finishes their own work—messily at first—learns faster than a person who learns to expect rescue. One month of imperfect work often produces better long-term output than permanent dependence on your 11pm edit.

Doesn't teaching take way more time than just doing it myself right now?

Teaching takes more time in that one moment. It takes less time every subsequent time that task appears. If the work recurs more than twice, you're already losing the speed argument. If it recurs weekly, you've lost by a factor of weeks.

What if they truly aren't ready—won't this set us up for failure?

There's a difference between 'they'll do it differently' and 'we'll miss the deadline.' Test the difference by picking low-stakes work first. What often feels like readiness isn't; it's your comfort level with their process. Their discomfort with starting is how learning begins.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script