OLD SCRIPT DETECTED
“My manager praises the team and all I hear is my old incident report”
Try this response:
“The team win and my incident report are two different documents measuring two different weeks.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“My manager praises the team and all I hear is my old incident report”
YOUR RECORDED RESPONSE
“The team win and my incident report are two different documents measuring two different weeks.”
ONE PRIVATE MOVE
Open the old incident report privately, reread only the contributing-factors list, and note in your own doc how many names are on it besides yours.
The Kudos Slide That Skips the Name Attached to INC-114
- What 'The Team Crushed It' Sounds Like With the Old Ticket Still OpenMonday stand-up, and your manager's on a roll: 'Zero P1s this sprint, best uptime all year, huge credit to the team.' Everyone nods. You're nodding too, but your second monitor still has INC-114 pinned in a tab — the incident report with your name in the root-cause section from three sprints back. The praise sounds like it's talking around you, carving 'the team' into a shape that quietly excludes whoever caused the last outage. You stay quiet and let the kudos pass by like it wasn't meant for you.
- A Postmortem Names What Broke, Not Who's Excused From PraiseHere's what the doc actually says, if you reread it without flinching: contributing factors, a timeline, three names on the response, no verdict. It doesn't say you're disqualified from 'the team' the next time something goes right. Group praise and an old incident report are unrelated documents. One measures a sprint. The other measures a Tuesday in March. Neither one decides whether today's applause includes you — you're the one making that call, silently, every time you decide not to take the win.
The Decision: Let the Applause Land Before You Reopen the Old Tab
So the choice in front of you isn't whether the incident happened — it did — it's whether you keep translating every 'great job, team' into 'except him.' Next time praise lands in the channel, close the incident tab first. Not to forget it. To stop letting it referee whether you're allowed to feel good about this Monday.
TRACE · 01/04
How this script runs you
- You keep a tab or bookmark to the old incident report open during team meetings, like it needs a witness.
- When the manager thanks 'the team' in the group chat, you scroll up to check whether your name got a separate mention, good or bad.
- You decline the next demo slot even when it's unrelated to the old incident, because being visible again feels like inviting comparison.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Incident Ledger
If the team gets praised as a whole, the incident report proves I was quietly excluded from that whole, so any collective win has to be checked against my private record before I'm allowed to feel it applies to me.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- The team win and my incident report are two different documents measuring two different weeks.
- Praise for the group doesn't come with a footnote listing who's exempt; I invented that footnote, not my manager.
- I'm allowed to hear 'great job, team' as including me, old ticket and all.
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
“My manager praises the team and all I hear is my old incident report”
I say
“The team win and my incident report are two different documents measuring two different weeks.”
Then I do one thing
Open the old incident report privately, reread only the contributing-factors list, and note in your own doc how many names are on it besides yours.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "My manager praises the team and all I hear is my old incident report". 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
The kudos message never used my name, does that silence mean something specific about me?
It usually means exactly what the words say: the manager credited the sprint's results to the group, not to any single name. The absence of a name is default phrasing for group recognition, not a coded reference to your incident report.
Why does hearing 'the team' get praised make the old incident report feel louder than it did the week the incident happened?
Praise creates a contrast the incident itself didn't: hearing the team succeed puts a spotlight on the moment you didn't, and your mind fills that gap with the most detailed memory available, the old report, not the most relevant one.
If I stay quiet during every round of praise so nobody connects me to the old report, does that keep the report from resurfacing?
No, staying quiet doesn't erase the report or stop it from resurfacing; it just trains you to treat every future win as unsafe to claim, which costs you visibility without changing anything already written down.
Related old scripts
Related self-checks
Related science
Researchers to explore
Related mechanisms
The research behind this script
- Postmortem Culture: Learning from Failure — Google SRE, Google SRE Book, 2016
- Invisible Labor in Open Source Software Ecosystems — Champion et al., arXiv, 2024
- Stack Overflow 2025 Developer Survey: Trust in AI at an All-Time Low — Stack Overflow, 2025
- A Mosaic of Perspectives: Understanding Ownership in Software Engineering — arXiv, 2025