OLD SCRIPT DETECTED
“Why did they keep me and not them?”
Try this response:
“There is no answer that makes this feel clean. That's a feature of the situation, not evidence I'm missing something.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“Why did they keep me and not them?”
YOUR RECORDED RESPONSE
“There is no answer that makes this feel clean. That's a feature of the situation, not evidence I'm missing something.”
ONE PRIVATE MOVE
Write down three things that happened at work in the past week without adding 'but' or 'sorry' or 'I know I don't deserve this.' Read it back. Notice what you said without qualification.
The Email Arrives, Then You're Congratulated
Before the Names Get Circulated
Your manager schedules a call. During the fifteen minutes waiting for it to start, you refresh your email twice. You already know what's coming—reorganization, headcount reduction, a list of names. When it comes, you see three people from your pod gone. You weren't on it. You get an email two hours later thanking you for your continued commitment. That's when the feeling arrives: relief mixed with a question you can't stop asking. Why you and not Marcus, who shipped the same features? Not Chen, who wrote cleaner code? Not Sarah, who had been there longer. You replay their last Slack messages, their projects, trying to locate the reason.
Exactly Four Days Later, at Your Desk
Your coworker mentions the promotion cycle opening up next month. They say it's good timing, with less competition now. You nod and start typing a response, then stop. Congratulations feels wrong. You haven't earned anything. You just weren't removed. When you take the same promotion discussion to your one-on-one, the words come out defensive: 'I know I'm only here because someone else had to go.' Your manager looks confused, says that's not how it happened. But you know the numbers. Layoffs are cuts, not selections for excellence. So you stop bringing wins to the table. You keep your head down. You don't raise your hand for the…
The Day You Write Down One Reason That Doesn't Crumble
You sit with a blank page and list every possible answer: skill, timing, project, seniority, relationship, luck. By the third read, each one feels hollow. Layoffs aren't puzzles with a hidden answer. They're business decisions in conditions of incomplete information—team size, budget cycles, manager recommendations, reorganization timing. No single reason made you bulletproof. And that absence of a satisfying explanation isn't evidence that you missed something. It's evidence that the situation itself is arbitrary. You write that down. You don't feel fixed. But you notice you answered a Slack question about a technical problem without…
TRACE · 01/04
How this script runs you
- You keep running the logic to find the reason you stayed — and can't land one that holds.
- When someone asks how work is going, you feel uncomfortable saying fine.
- You find yourself mentally apologizing to colleagues every time something good happens at the office.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Why Me Loop
The decision that kept me was arbitrary — which means I can't fully own it. If I can't explain why I survived and they didn't, then I don't deserve to be here. Randomness in layoffs feels like a flaw I'm responsible for fixing by refusing to benefit from it.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- There is no answer that makes this feel clean. That's a feature of the situation, not evidence I'm missing something.
- I kept my job. I didn't take theirs. Those are two different sentences.
- Not having a satisfying explanation doesn't mean the outcome was wrong — it means layoffs are messy.
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
“Why did they keep me and not them?”
I say
“There is no answer that makes this feel clean. That's a feature of the situation, not evidence I'm missing something.”
Then I do one thing
Write down three things that happened at work in the past week without adding 'but' or 'sorry' or 'I know I don't deserve this.' Read it back. Notice what you said without qualification.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "Why did they keep me and not them?". 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
Isn't it true that the decision was random, which makes my guilt worse?
Layoffs do contain randomness, but randomness doesn't make the outcome wrong. Many outcomes in work are semi-arbitrary and still real. Your job is real. That doesn't erase the loss of others' jobs, but it does mean you don't need to refuse your own existence to honor theirs.
If I can't find the reason I was kept, doesn't that mean I'm lying to myself about why?
No. It means the reason is complex and didn't boil down to one clear signal. That's normal in downsizing. A reason existing doesn't require you to feel it or explain it to yourself perfectly. You were kept. That's the fact. The absence of a perfect narrative doesn't change it.
How do I stop feeling like I took someone else's spot?
By separating two things: your job still existing (true), and you having caused someone else's job to be cut (false). You didn't make that decision. You didn't bid against them. The company made a choice about headcount. You surviving it doesn't mean you stole it.
Related old scripts
Related self-checks
Related science
Researchers to explore
Related mechanisms
The research behind this script
- Healing the Wounds: Overcoming the Trauma of Layoffs and Revitalizing Downsized Organizations — Noer, D.M., Jossey-Bass, 1993
- Downsizing: What Do We Know? What Have We Learned? — Cascio, W.F., Academy of Management Executive, 2002