The Rule That Survived the CutYou've noticed something: every piece of information from leadership now means something. A slide about headcount. A manager's sudden focus on 'efficiency metrics.' A 1:1 moved to Thursday instead of Wednesday. You don't decide this consciously. The rule just runs: Every signal is a clue about whether I'm next. It feels like you're reading the room. Actually, you're reading for survival. The organization already proved it could change in an afternoon. Your job was solid until it wasn't. So now you collect evidence—screenshots, calendar shifts, who got called into which meeting—not to be paranoid, but because you learned something true:…
OLD SCRIPT DETECTED
“I'm next — I can feel it”
Try this response:
“That alert system worked the day it started. It's not giving me new information anymore—it's just repeating.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“I'm next — I can feel it”
YOUR RECORDED RESPONSE
“That alert system worked the day it started. It's not giving me new information anymore—it's just repeating.”
ONE PRIVATE MOVE
For three days, note the exact moment you feel 'next' most strongly. Write down the trigger—meeting moved, Slack comment, Friday afternoon quiet—and whether anything actually changed. Look for the pattern between feeling the urge and having new information.
The Town Hall Slide You Saved
How Reasonable Vigilance Becomes a LoopHere's the mechanism: after a layoff round, survivors genuinely do face 12–18 months of organizational opacity. Leadership does communicate differently. Meetings do get rescheduled. Quiet periods do sometimes precede announcements. So your alert system isn't wrong—it's just not calibrated for normal anymore. A rescheduled 1:1 used to mean someone's calendar moved. Now it feels like a threat assessment. The problem isn't that you're reading signals; it's that you've stopped distinguishing signal from noise. Every ambiguous thing becomes evidence. And because you're looking for the pattern, you find it everywhere. The loop doesn't break…
Testing What 'Just In Case' Actually CostsFor one week, notice when you prepare that exit plan. Not whether you do it—when. Is it during quiet Fridays? After a meeting agenda shifts? After you hear someone else's name in a Slack thread? Write down three concrete moments, nothing more. This isn't about stopping the planning—staying employable is reasonable. It's about whether you're planning once a month out of genuine career wisdom, or three times a day because a calendar notification triggered the script. You'll probably find that the 'just in case' shows up most when ambiguity is highest, not when actual risk is highest. That gap—between when you feel the need to prepare and when…
TRACE · 01/04
How this script runs you
- You screenshot all-hands deck slides automatically, storing them as proof of what you saw.
- A rescheduled meeting with your manager sends you into a 30-minute threat assessment before you remember the last five reschedules meant nothing.
- You've kept a half-drafted resignation email in your notes for months, updating it with new skills in case it's needed.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Next Round Fear
Every signal from leadership is a clue about whether I'm next. The organization proved it could change suddenly, so reading ambiguous things as precursors makes sense—but the loop misfires when you treat normal calendar friction and routine business decisions as secret evidence of another round coming.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- That alert system worked the day it started. It's not giving me new information anymore—it's just repeating.
- A rescheduled 1:1 is usually someone's calendar conflict, not a signal I need to decode.
- Keeping my resume current is smart; checking it seventeen times a week because of a quiet Friday is the cost I'm paying, not the protection I'm building.
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
“I'm next — I can feel it”
I say
“That alert system worked the day it started. It's not giving me new information anymore—it's just repeating.”
Then I do one thing
For three days, note the exact moment you feel 'next' most strongly. Write down the trigger—meeting moved, Slack comment, Friday afternoon quiet—and whether anything actually changed. Look for the pattern between feeling the urge and having new information.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "I'm next — I can feel it". 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
If I stop reading every signal as a warning, won't I miss the actual next round?
The difference isn't between reading signals and ignoring them. It's between learning something new (an actual policy change, a real announcement, a genuine structural shift) and recycling the same fear through new objects. You'll catch real information because it will actually be new. The loop is when you're preparing for the same threat with the same evidence, just on repeat.
Why does a rescheduled 1:1 feel so threatening when logically I know it usually means nothing?
Because your system learned that normal-looking days can end with you out of a job. That's not irrational—that's what happened. But normal calendar movement is about as predictive of layoffs as cloud cover is. Your mind is treating it as a sign because signs could have mattered on the day they mattered. Now you're applying that same filter to everything, and most of it is just noise.
How do I keep my resume updated without it feeling like I'm always waiting to leave?
The difference is rhythm and outcome. Updating it monthly as part of career maintenance is one thing. Revising it three times a week because ambiguity spiked is your alert system running the loop. Notice which version you're actually doing. You can care about being employment-ready without making the update ritual a response to fear.
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