You’ve been reading the layoff headlines for two years now, and at some point they stopped meaning anything: a company, a number, a line about “efficiency.” You’ve gotten good at scrolling past them, and that’s exactly the problem. The headline that matters never gets written: the slow, unglamorous story of what’s happening at your company, on your team, to your work.
In “You’re Not Unemployed Because of AI,” we established that the market is sorting, not collapsing, and the aggregate demand for design has never really gone away. That’s the market. NN/g’s State of UX 2026 adds the piece that matters here: senior and generalist roles are recovering faster than entry-level ones. This letter is about something smaller and harder to see: your desk. Whether the place you work is investing in you or managing you out, one deprioritized project at a time. And whether you should stay and fight for it, or leave.
Reading your own company
I’ve sat in enough of these companies to recognize the pattern before the slide deck gets to the AI slide. Outward-facing, the company talks about innovation, chasing whatever technology is trending, looking high-tech to whoever is listening, investors especially. Inside, a much smaller number of people are holding legacy systems together with string, patching one collapsing piece after another, on unpaid overtime, because telling the truth (”we drifted technologically for years and now we need to fix it”) would cost someone their stock price or their seat at the table. AI just gave an old pattern a better cover story.
Every company in 2026 has learned to talk about AI. Some of them are telling the truth when they say AI changed their headcount needs. Most of them are using AI as a story that’s easier to tell than the real one, which is that the money ran out, the strategy didn’t work, or someone above you made a bet that failed and needs a headline that isn’t “we misjudged the market.”
Challenger, Gray & Christmas, the outplacement firm that tracks announced job cuts, counted AI as the top cited reason for the second month running in April 2026 - 21,490 cuts, over a quarter of that month’s total. Andy Challenger, who has watched company layoff announcements for a living, put it plainly: whether or not your actual job is being replaced by AI, he said, “the money for those roles is.” It means the AI story and the budget story are often the same thing, wearing different clothes.
Gartner analyst Kathy Ross has gone further, predicting that half the companies now blaming AI for headcount cuts will be quietly rehiring for the same work under new job titles by 2027. Orgvue, a workforce-planning software firm, found something similar already happening: nearly a third of companies that cut staff to chase AI savings have had to hire the work back. Three-quarters of the reasons behind these cuts, when you look past the press release, are economic conditions and restructuring. Not automation. (Not that this should comfort you. A company doesn’t need to be right about AI to be wrong for you.)
So don’t read the AI announcement. Read the desk. The signals that tell you something about your specific situation look like this:
- Your projects have shifted from long-horizon work to two-week tactical asks, with nobody able to tell you what comes after.
- You’ve been moved off the roadmap conversations you used to be in, and nobody explained why.
- Work that used to be yours is now split between a PM, an AI tool, and whoever’s left on the team, with no one owning the outcome.
- Design’s reporting line has moved further from the business decisions that shape what gets built.
- Your manager has stopped fighting for headcount, or budget, or your next project, and started talking mostly about “efficiency.”
I’ve watched people get written out of the planning meetings they used to run, without a word, and I’ve watched their work get split three ways before they noticed it had happened. Neither one comes with an announcement. That’s the whole design of it.
One of these, on its own, might be a bad quarter. Nielsen Norman Group’s read on 2026 is that many organizations are compressing responsibilities that used to be spread across several specialists, which is a polite way of saying: you’re being asked to do more, with less clarity about why. If that’s happening to your whole team, it might be strategy. If it’s happening only to you, that’s a different conversation, and probably one you should be having with your manager directly, not with this letter.
The math on staying and leaving
2026 is different from 2021 in one specific way. Back then, leaving was the smart financial move almost by default. You jumped, got a 20 percent raise, and barely had to negotiate. ADP’s data on the wage premium for switching jobs - what you earn by leaving versus staying put - has fallen to 1.9 percentage points, the lowest since they started tracking it in 2020. People are quitting at a rate down by about a third from the 2022 peak. Nela Richardson, ADP’s chief economist, said it best: “No one ever promised a 50-year cycle for white-collar work.” The market that made leaving easy isn’t the market you’re in now.
This doesn’t mean stay no matter what. It means the arithmetic changed, and you have to do it honestly instead of running on 2022 muscle memory. Start with the unglamorous version: what do you give up by leaving. Unvested equity, a manager who’d fight for you elsewhere, a severance package that companies are now offering less generously than they were three years ago (industry estimates put the shrinkage at 15 to 20 percent, alongside shorter health coverage bridges). None of that is a reason to stay in a company that’s managing you out, but know the number before you decide, instead of discovering it the week after you resign.
Then do the other half of the arithmetic, the part people skip because it’s less comfortable: what does staying cost you if you’re right about the decline. Every month inside a shrinking role costs you three things: skills that stop compounding, a resume that gets harder to explain, and one more month spent telling yourself the next reorg will be the one that fixes it. Stanford’s Nick Bloom has one piece of advice for this exact moment, and it isn’t complicated: line up the next thing before you leave the current one. In a low-hire, low-fire market, quitting on faith that something better will show up is a bet, not optimism, and a worse bet than it used to be.
This is why the diagnosis matters more than the instinct. A company managing its people through disinvestment doesn’t announce it. It just slowly stops asking you the questions that used to define your job (will this be good for the user, will this work) and starts asking you a smaller, safer one (does this support the roadmap we already committed to). You’ll feel it before you can prove it. The job is to prove it anyway, because “I have a bad feeling” isn’t a plan, and neither is “the market is scary, so I’ll wait it out.”
Voice before exit
There’s an old idea, older than any of this year’s data, that applies here better than most current thinking does. In 1970, the economist Albert Hirschman wrote about what happens when something you belong to starts to decline - a company, a party, a country. You have three moves: leave (exit), speak up (voice), or stay quiet and hope it fixes itself (loyalty, in its more passive form). Hirschman noticed something uncomfortable about the mechanics of it. The people most capable of noticing decline early, and most equipped to leave because they have options, tend to be the first ones out the door. That sounds like good instincts, until you realize what it does to the organization they left behind. Every time your most talented colleague quits without a word, the room gets a little worse at hearing anyone else. The people best positioned to fix things are the ones with the least incentive to stay and try.
So before you leave, use your voice. Not as a formality you perform on the way out, and not as naive faith that speaking up always works. As a real test, with a real answer, that you’re willing to believe even when it’s not the answer you wanted. Ask for the four things that matter, ideally in one direct conversation rather than scattered across six passive-aggressive Slack messages: the shape of the work (what you’ll be doing, not what the job title implies you’re doing), whether there’s a real path to grow new skills here, whether the people around you are the ones you’d choose to keep working with, and yes, the money, said out loud, not implied. If your manager can move on even one of these in a dated, concrete way, you have a data point worth weighing. If every answer gets deflected into “let’s revisit this next quarter” - the same quarter that was also going to fix things last quarter - you have a different data point, and it’s the more honest one.
I’ve had that conversation more times than I can count, on the asking end of it. I’ve asked directly for clarity on where things were heading, what the plan was, whether the roadmap I was building against still existed anywhere outside a slide. More than once, the answer was a verdict on me, not a plan: too conflictual, too many questions, not adapting well enough to the environment the company was giving me. We don’t have time for that kind of analysis, someone would say. We don’t have all the tools yet, just work with what we have. The answers dodged my question and confirmed a different one: whether asking it at all was welcome.
This is also where you run the test that separates a bad stretch from a managed decline. A bad stretch has a cause you can name: a client left, a reorg is mid-flight, a launch got delayed. It’s contained to one story, and the story has an ending. A managed decline doesn’t have one cause. It has a pattern - the same signal, showing up again in a different form, quarter after quarter, with no single explanation that accounts for all of it. One canceled project is a decision. Three canceled projects, a manager who’s stopped fighting for headcount, and a reporting line that keeps drifting further from the roadmap conversations aren’t three unrelated decisions. That’s a direction.
One designer, Twisha Shah-Brandenburg, wrote about the moment the language in her org started to shift, from asking whether the work would help anyone to asking whether it served the quarter’s targets. She noticed it the way you notice these things, which is to say months after it had already been happening. She stayed anyway, for a while, because leaving wasn’t simple for her either - a mortgage doesn’t care how honest your read on company decline is. Her advice was to “stop waiting for permission to care,” not to quit - to keep pushing the work she believed in, inside the room she was still standing in, instead of performing acceptance of a version of the job she never signed up for.
Another designer, Elizabeth Eagle-Simbeye, took a different lesson from a similar moment: her CEO announced an AI pivot after one too many thought-leadership posts on LinkedIn, and instead of arguing about it in the all-hands, she started keeping a paper trail. Every agreement. Every scoped decision. Every promise made in a meeting that has a habit of getting forgotten by everyone except the person it was made to. Whatever happened next, she wanted a record of what was said, and she wasn’t going to be the only one in the room without one. Her framing is the one worth keeping: “resilience, not resignation.”
Neither of them is wrong, and neither one is the model answer. They were answering different questions, because they were standing in different companies, at different distances from the edge. That’s the real test here, not a scorecard, not a checklist you fill in alone at midnight and mistake for a decision. Talk to your manager. Ask the four questions, plainly, and write down the answers somewhere you’ll reread them. Then watch what happens to those answers over the next month, not the next conversation, because one good meeting proves nothing and one bad one doesn’t either.
This isn’t theoretical for me. Seven people asked me some version of this exact question this year, stay or leave. Five times, I advised them to leave.
And if the pattern keeps repeating - if the work keeps shrinking, if the roadmap conversations keep happening without you, if voice keeps getting the same polite non-answer - then you already know what all of this was for. The data was never going to make the decision for you. It was only ever going to tell you when to stop pretending you hadn’t made it already.