I once ran a year-long mental health campaign for a startup. We did everything right: psychological safety workshops, vulnerability training, leadership modeling openness. People actually started talking about their struggles. It felt meaningful.
A month after the campaign wrapped, they laid off 10% of the company. Including me.
The two things weren't connected, at least not in the way you'd think. But I remember at the time someone on Glassdoor wrote: "Pretty cynical that they spent a year skilling up everyone's mental health just to fire them."
It broke my heart because they weren't wrong. Not about intent (the campaign was genuine) but about the underlying logic. We'd spent twelve months helping people build individual resilience to handle workplace stress while the organization was actively deciding which of those people it could afford to keep.
The Problem Isn't Resilience. It's Where We're Placing the Burden.
Organizations love resilience training. They love talking about adaptability, mental toughness, embracing change. What they don't love is examining why their people need to be so resilient in the first place.
When a company rolls out AI adoption alongside resilience workshops, that's not coincidence. When they emphasize "learning agility" while quietly evaluating which roles can be automated, that's not poor timing. It's the same logic: change is inevitable (because we're making it happen), so you better get good at handling it (because we're not slowing down).
The implicit message: if you struggle with this transition, that's a personal failing. You weren't adaptable enough. You didn't upskill fast enough. You weren't resilient enough to survive decisions made in meetings you weren't invited to.
This isn't about whether resilience is valuable (of course it is). This is about who bears the cost of organizational change and who benefits from framing that cost as individual responsibility.
What This Actually Looks Like
It's the leadership team emphasizing "psychological safety" while implementing surveillance software.
It's the L&D program teaching stress management techniques instead of questioning why everyone's so stressed.
It's the town hall about "thriving through change" delivered three weeks before restructuring announcements.
It's telling people to build their personal brand and stay employable while destabilizing the job market they're supposed to navigate.
The problem isn't that these programs are insincere. Most are delivered by people who genuinely care. The problem is structural: they're designed to help individuals adapt to conditions that organizations are actively creating and could choose to manage differently.
You're not being trained to bounce back from external market forces. You're being trained to bounce back from your employer's strategic decisions.
So What Do You Actually Do?
I'm not telling you resilience is worthless. I'm telling you that organizational resilience programs shift responsibility without shifting power.
What you need isn't more adaptability training. You need to reduce your exposure to decisions made by people who don't have your interests at heart. Not because they're malicious, but because their job is to optimize the organization, not optimize you.
Here's what that actually looks like:
Map Your Dependencies
You can't control what your organization automates, restructures, or eliminates. But you can control how dependent you are on any single version of your job continuing to exist.
This week, document your dependencies:
Tools and platforms: What software, systems, or AI tools are you completely reliant on? What happens if access disappears (budget cuts, vendor changes, IT restrictions)?
Processes and workflows: Which parts of your job only work because of specific organizational processes? If that process changes or gets automated, what breaks?
People and relationships: Whose continued employment is your role dependent on? Which stakeholders protect your function? What happens if they leave?
Assumptions about stability: What are you assuming will stay constant? Your team structure? Your reporting line? Your budget? The organization's AI strategy?
Write it down. All of it. Not to panic yourself, but to see clearly.
Then Build One Backup Plan This Week
Pick your biggest single point of failure (the one thing that, if it changed, would destabilize your position most) and create redundancy.
- If you're dependent on one tool: learn the alternatives now, while you don't need them.
- If you're dependent on one process: document how to achieve the same outcome a different way.
- If you're dependent on one relationship: expand your stakeholder network deliberately.
- If you're dependent on one assumption: test it. Ask questions. Prepare for the version where it's wrong.
This isn't catastrophizing. It's the same risk management logic organizations use when they build contingency plans and diversify vendors. You're just applying it to your own work.
Why This Matters More Than Another Resilience Workshop
Resilience training teaches you to absorb shock. Dependency mapping teaches you to reduce exposure.
One makes you tougher. The other makes you less vulnerable.
Most organizational resilience programs are designed to help you survive decisions you don't control. This is designed to help you maintain agency when those decisions happen anyway.
The goal isn't paranoia. The goal is clear-eyed assessment of what you're actually exposed to and deliberate action to reduce that exposure.
Because here's what I learned from that mental health campaign: you can be as resilient as humanly possible and still get laid off. You can be adaptable, mentally tough, emotionally intelligent, and still lose your job to an automation decision or a restructuring plan.
Individual resilience doesn't protect you from structural decisions.
But reducing your dependency on any single version of work continuing to exist? That actually helps.
This week: Pick one dependency. Build one backup plan. You're not being paranoid. You're being realistic.