OLD SCRIPT DETECTED
“Everything that goes wrong ends up being my fault”
Try this response:
“Being there when it happened isn't the same as causing it.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“Everything that goes wrong ends up being my fault”
YOUR RECORDED RESPONSE
“Being there when it happened isn't the same as causing it.”
ONE PRIVATE MOVE
Write two columns on paper — Caused By Me and Just Happened Near Me — and sort today's mishaps between them before you say sorry to anyone.
The Bus Is Twenty Minutes Late
The Bus Is Twenty Minutes Late
The bus is twenty minutes late because of a road closure nobody could have predicted, half the kit bag got left behind at the school because the equipment manager forgot it, and standing on the wet grass before kickoff you're already running a tally: late bus, missing bibs, a teammate's ankle that rolled on slick turf in warm-ups. None of it is yours. All of it lands on your chest first, before the whistle even blows, as if you scheduled the roadworks and packed the bag yourself.
Apologizing for the Weather
By halftime you've spent more energy apologizing — to the coach for the late start, to the injured teammate for the wet pitch, to the ref for a call you didn't make — than you've spent playing. That night you lie awake rerunning the road closure like you could have rerouted it, and you draft a text taking the blame for the missing bibs before you've even checked whether packing them was ever your job.
The Two Columns
You take a sheet of paper and draw two columns: Caused By Me, and Just Happened Near Me. The road closure, the ankle roll on wet grass, the ref's call — none of them fit the left column. Seeing the short, specific list on paper outlasts the urge to send that half-drafted apology.
TRACE · 01/04
How this script runs you
- A late bus, bad weather, or a referee's call registers in your body as your failure before you've checked whether you had any part in it.
- You draft private apologies for things you didn't do, just in case someone blames you if you don't claim it first.
- You replay unrelated mishaps — a rolled ankle, a missing kit bag — searching for the moment you could have prevented them.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Captain's Burden
If something goes wrong while I'm present or in charge, I must have caused it or failed to prevent it — being near the problem is proof I own it, whether or not I had any actual part in it.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- Being there when it happened isn't the same as causing it.
- I can check what was actually mine before I apologize for it.
- A road closure and a rolled ankle aren't proof I failed anyone.
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
“Everything that goes wrong ends up being my fault”
I say
“Being there when it happened isn't the same as causing it.”
Then I do one thing
Write two columns on paper — Caused By Me and Just Happened Near Me — and sort today's mishaps between them before you say sorry to anyone.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "Everything that goes wrong ends up being my fault". Word for word — the wipe targets the sentence, not the vibe.
- Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
- Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
- Run the loop: play it every morning and night, log one proof action a day for 7 days.
Straight answers
What's different about blaming myself for the weather versus blaming myself for a bad play I actually made?
A bad play involves a decision you actually made. A canceled bus or a rained-out field involves nothing you decided, scheduled, or controlled — the two categories only feel identical because both happened while you were the one standing there.
Why do I feel responsible for a teammate's rolled ankle I had nothing to do with?
Presence gets mistaken for cause. You were on the same field when it happened, so your mind treats nearness as evidence, even though a rolled ankle on wet turf has nothing to do with anything you said, did, or decided beforehand.
If I stop taking blame for things like a late bus or bad weather, will people think I'm dodging responsibility?
Sorting what's actually yours from what merely happened near you isn't dodging — it's accuracy. Owning the two or three things you actually decided is more credible than a blanket apology for a bus schedule, and people notice the difference between accountability and reflexive guilt.
Related old scripts
Related self-checks
Related science
Researchers to explore
Related mechanisms
The research behind this script
- Motivational processes in the coach-athlete relationship: A multi-study self-determination theory investigation — Jowett, Adie, Bartholomew et al., Psychology of Sport and Exercise, 2017
- Social identity and cohesion, efficacy, and performance across a competitive rugby season — Fransen et al., IJSEP, 2023
- The Dynamics of Group Cohesion in Sport — Carron, Journal of Sport and Exercise Psychology, 1981
- Athlete Leadership Development Within Teams: Current Understanding and Future Directions — Frontiers in Psychology, 2022
- The myth of the team captain as principal leader: extending the athlete leadership classification within sport teams — Journal of Sports Sciences, 2013