OLD SCRIPT DETECTED
“The fires I prevent don't count — only the ones I fight”
Try this response:
“Prevented trouble still used my time, so I’m logging it too.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“The fires I prevent don't count — only the ones I fight”
YOUR RECORDED RESPONSE
“Prevented trouble still used my time, so I’m logging it too.”
ONE PRIVATE MOVE
Open a blank note or paper and write three lines: one quiet problem you stopped today, one minute it cost, and one reason it stayed invisible. Then close it and leave it where you can find it later.
Only the Blaze Makes the Review
- The alarms you disarmed before anyone saw themYou spent the day clearing the dry leaves before they could catch, then you looked up and found nothing smoking. The handoff was smooth, the typo was fixed, the confused request was answered before it spread. By evening, all that remains is the thing that never had time to become visible. Your private conclusion is blunt: the fires I prevent don't count — only the ones I fight.
- What the quiet day keeps getting mistaken forThat sounds convincing because visible trouble leaves a trace and prevented trouble leaves a gap. If no one saw the almost-mistake, no one can point to your rescue. But the absence of a disaster is still work you spent time on. The cost is that you start acting as if only the noisy moments matter, which makes you less likely to record, name, or protect the quiet labor that held the day together.
A note on the fridge, not a performance for anyone
So you make one small decision: put a private record where the unseen work can’t vanish. Jot down the prevented fire, the save, and the hour it took. Not to prove a point to anyone tonight, just to stop letting the same kind of work disappear from your own accounting. When the visible blaze finally gets all the credit, you still have the ledger that shows what kept it from starting.
TRACE · 01/04
How this script runs you
- You can list the problems you solved only after they got loud, but the near-misses you stopped never make it into the story of your day.
- A calm afternoon feels oddly empty, while a crisis feels like proof that your effort mattered because there was something dramatic to point at.
- When review time arrives, the work that mattered most is the work with the least obvious aftermath, so it is the first to disappear.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Invisible Load
Only work that ends in a visible emergency counts as real effort. If you prevented the emergency before it became dramatic, it was useful but not worth much, so you should treat it as background and save your attention for the moments that can be seen, named, and credited.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- Prevented trouble still used my time, so I’m logging it too.
- If it never became a fire, that doesn’t mean it was free.
- I’m counting the saves that stayed quiet, not just the ones that flared up.
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
“The fires I prevent don't count — only the ones I fight”
I say
“Prevented trouble still used my time, so I’m logging it too.”
Then I do one thing
Open a blank note or paper and write three lines: one quiet problem you stopped today, one minute it cost, and one reason it stayed invisible. Then close it and leave it where you can find it later.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "The fires I prevent don't count — only the ones I fight". 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
Why does the quiet work feel like it doesn’t count?
Because nothing dramatic happened afterward, there’s no aftermath for your mind to point to. The day looks smooth from the outside, even when you spent time keeping it that way. The problem is not that the work lacked value; it’s that its success erased the evidence.
Isn’t it just natural to pay attention to the big emergencies?
Yes, big emergencies are louder and easier to remember. But if that becomes the only kind of work you credit, you end up rewarding the moments that broke down and overlooking the steadier work that kept them from breaking down in the first place.
What am I supposed to do with the work nobody saw?
Don’t try to force recognition in the moment. Just give the work a record that matches its actual cost: what you prevented, how long it took, and what would have happened if you had ignored it. That keeps your own accounting from being erased by the lack of spectacle.
Related old scripts
Related self-checks
Related science
Researchers to explore
Related mechanisms
The research behind this script
- Why Organizations Don't Learn — Gino & Staats, Harvard Business Review, 2015
- The First 90 Days — Watkins, M., Harvard Business Review Press, 2003