The Old Recession Playbook Is Wrong. Stop Cutting People First.
It’s eleven o’clock. Do you know how your business operates?
The real version. The one where someone in accounting spends half their week copying numbers between two systems that have never talked to each other because the integration got deprioritized in favor of a dashboard nobody uses. The one where a dispatcher schedules trucks with a spreadsheet and two phone calls because the project to fix it got killed three budgets ago.
Every previous recession was a test of financial resilience. How much cash do you have. How fast can you cut. How long can you hold your breath.
The next one will be a test of operational intelligence. Whether you can restructure before the board forces you to cut.
For decades, restructuring meant headcount reduction, because nothing else worked fast enough. Revenue drops, the board panics, someone hires a consulting firm that charges more per hour than anyone they are about to recommend firing, people get cut, and months later you are hiring contractors at twice the rate to rebuild what you lost. We have all watched this movie. Some of us have been extras in it.
That playbook is over. For the first time, something else works fast enough. AI can automate intake, stand up support agents, eliminate hours of daily paperwork. Is it clean? No. But the gap between “possible” and “deployed” is closing faster than any previous technology cycle. And unlike process redesign or outsourcing, AI can start at the edges without a steering committee and a Gantt chart.
The CEO who reaches for layoffs instead is choosing last decade’s playbook in a world that has moved on. It will feel decisive. It will look like leadership on the earnings call. It will be the most expensive decision they make.
Talk to Your People
Your people already know where the fat is. They have known for years. You just never asked.
The customer service rep who copy-pastes between systems all day has thought about what should be automated more than anyone in IT has. Nobody invited her to that meeting. The accounts payable clerk who reconciles invoices against POs because the ERP was configured by someone who left years ago can draw the broken workflow on a napkin in thirty seconds. Nobody asked him either.
The problem was never diagnosis. Fixing it required headcount nobody could justify, capital nobody could allocate, or political courage nobody wanted to spend. The VP who owns the process does not want to admit it is broken because they built it. So everyone works around it and pretends it is fine. If that surprises you, you might be the VP.
AI breaks that logjam. It gives people the tools to fix the things they have been complaining about for years. “We are bringing in AI to optimize headcount” gets sabotage. “We are going to fix the thing that makes your job miserable” gets cooperation.
The Death Grip
But only if they want to.
Here is what actually happens when people feel threatened. I have watched it. You probably have too. Pretending otherwise is how consultants stay employed.
The CFO says “doing more with less” at an all-hands and everyone’s stomach drops. The moment that fear lands, every person in the organization shifts from “how do I make this company better” to “how do I make myself irreplaceable.” They hoard knowledge. They obscure processes. They make themselves the single point of failure for as many critical workflows as possible.
Congratulations. You have just turned your entire workforce adversarial to the efficiency project.
That billing reconciliation that takes dozens of hours a month because of a workaround that was never supposed to become permanent? The person who owns it is going to grab that tree with a death grip and hold on. Every AI pilot will mysteriously fail. Every timeline will slip. The people made sure it didn’t work.
And honestly? Good for them. Self-preservation. Completely rational.
The New Playbook
So what do you actually do on Monday morning?
Pick three workflows your team hates and touches every day. The repetitive, soul-crushing work everyone complains about and nobody owns. Skip the strategic projects. Skip whatever the CTO is excited about. Ask the people who do the work. They have been waiting for someone to ask.
Map them in plain language. Where does the work start. Where does it stall. Where does a human copy data between systems because nobody ever built the integration.
Then remove one step. Remove, not optimize. Sometimes that means an AI agent handles intake, a script moves data, a tool generates the first draft so a human reviews instead of creates. Sometimes it means killing the step entirely. A lot of “fat” workflows are artifacts of bad systems design, regulatory theater, or someone’s empire from three reorgs ago. The best outcome is making a broken process visible enough to kill.
Do this in weeks, not quarters. Announce it publicly. Show the before and after. Show that nobody lost their job. Then do it again.
The goal is momentum. Once your team sees that the worst parts of their day can actually disappear, and that nobody got fired for pointing it out, they will tell you where to go next.
The Rules
These are load-bearing.
No job losses tied to AI initiatives. The moment one person gets cut because of an automation win, every other person stops cooperating. Trust is not renewable.
Every automation must eliminate a step. If the new process has more steps than the old one, you have added complexity with a better user interface. The world has enough of those.
Every change must be visible to the organization. No quiet rollouts. No stealth pilots. Visibility builds trust. Secrecy kills it.
Time saved must be measured and published. Measured. If you cannot show the before and after in plain language, the win did not happen.
Teams propose the work. Leadership funds the removal. The people closest to the process decide what gets automated. Leadership’s job is to fund it, protect it, and stay out of the way. This is the hardest rule because it requires executives to admit they do not know where the problems are. Most of them would rather hire a consultant.
The Real Unlock
This is about safety, not AI.
AI is the tool. Safety is what makes people use it. People will never hand you the map to their own redundancy. They will hand you the map to their own relief, if they believe the destination is a better version of their job.
Every failed AI transformation you have ever read about died here. The executives bought the platform, hired the consultants, announced the strategy with a slide that said “AI-First Organization,” and wondered why nobody cooperated. People did not feel safe. Everything else was a symptom.
The companies that figure this out will be unrecognizable on the other side of the next downturn. Because of what happens when you stop making people afraid and start letting them fix things.
One Warning
Not every company can keep headcount intact through a downturn. If that is your situation, be honest about it. Promising safety and then cutting anyway is worse than cutting cleanly. Trust evaporation is permanent. And everyone talks.
But if your operation can absorb the shift, start now. The leaders who bet on their people over their spreadsheets will build organizations their competitors cannot replicate. Because they found better courage.
boring (adj.): a recession where nobody gets fired because the AI handles the work that should never have required a human in the first place.