REALITYWIPE

OLD SCRIPT DETECTED

If I'm not running this team, nothing gets done

Try this response:

The ticket moved without me watching it. That's data, not a fluke.

Take the 60-second self-check

SEE THE PRACTICE

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

THE THOUGHT

If I'm not running this team, nothing gets done

YOUR RECORDED RESPONSE

The ticket moved without me watching it. That's data, not a fluke.

ONE PRIVATE MOVE

Privately write down one task you predicted would stall without you this week, then check later if it actually did.

The Tuesday standup you skipped on purpose

The empty chair experiment nobody asked forYou sat out the Tuesday standup on purpose, coffee in hand, phone face-down, telling yourself it was a test. By 9:40 you'd cracked and opened the shared doc anyway, scanning for the stalled ticket you were sure would be sitting untouched. It was moving. Someone had already picked it up. You felt relief, and right behind it, something closer to disappointment — as if the team running fine without you in the room quietly disproved the story that you're the one holding it together.

Why the doc always looks stalled from outsideYou built the assignment system, you remember every dependency, and you're the one who gets pulled in when something breaks — so your view of the team is skewed toward the moments it needed rescuing. That's the sample you have. What you don't see is the stretch of ordinary hours where people just do the work without incident, because those hours never generate a memory worth keeping. The record in your head is a highlight reel of near-misses, not a fair average, so it always tells you the team is one missed check-in from falling apart.

The forty-minute absence you can undo any timePick one recurring meeting this week you'd normally run and let someone else run it instead — same time, same room, you just don't steer. Afterward, write down privately what actually happened versus what you predicted would happen. One meeting won't tell you the team can run itself forever, but it will tell you whether your prediction and the outcome matched, which is the only thing the myth is actually claiming.

TRACE · 01/04

How this script runs you

  • You reopen the shared doc minutes after stepping back from a meeting, checking whether the ticket moved without you.
  • Handing off a recurring meeting to someone else feels less like delegating and more like leaving the room unlocked.
  • When a task goes smoothly without your input, it registers as luck rather than as evidence the system works.

SOURCE_LOCATED · 02/04

The hidden rule underneath

The Captain's Burden

The rule underneath this thought is that momentum only exists while you're personally supplying it — that the team isn't a system that runs, it's a weight you're holding up, and the instant your hands come off, it drops.

FORGING_REPLACEMENT · 03/04

Replacement lines (record these)

  • The ticket moved without me watching it. That's data, not a fluke.
  • I can hand off this meeting and still be the person who built the system.
  • One smooth stretch without me doesn't prove I'm dispensable, and it doesn't prove I'm essential either — it's just one stretch.

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 I'm not running this team, nothing gets done

I say

The ticket moved without me watching it. That's data, not a fluke.

Then I do one thing

Privately write down one task you predicted would stall without you this week, then check later if it actually did.

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 I'm not running this team, nothing gets done". 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 hand off the standup and something actually does go wrong?

Then you'll have one real data point instead of a prediction, and you can look at what specifically broke — a missing piece of information, not the absence of you personally. Most stalls trace to a gap that's fixable without you being in the room again.

Isn't checking the doc after a meeting just being conscientious?

Checking once is conscientious. Checking within minutes, before there's been time for anything to actually go wrong, is closer to confirming a fear than gathering information — the timing gives it away.

I built most of the team's process myself — doesn't that mean it really does depend on me?

Building a system and being required to operate it every day are different things. A process you designed can keep running on its own logic once it's in motion; testing that isn't the same as claiming the design didn't matter.

Related old scripts

Related self-checks

Related science

Researchers to explore

Related mechanisms

The research behind this script