“Build agility.” “Treat change as normal.” “Be resilient.” On paper, this all sounds wise. In real life, it’s often the language people use when they want everyone else to absorb the shock while leadership keeps its options open.
That’s why I’m torn on this World Economic Forum-style message about organizations transforming how they approach change. The headline idea—stop treating change like an emergency and start treating it like operations—can be genuinely smart. But it can also be a polite way of saying: “Expect more chaos, with fewer promises, and please keep performing.”
From what’s been shared publicly, the report is basically arguing that geopolitical and economic shifts are making the world less predictable, so companies need to build agility and resilience into how they work. Not as a special project. As the default setting. And it points straight at people leaders: chief people officers are struggling to match talent supply with the critical skills companies say they need, with a growing focus on execution and deploying AI.
That part is real. Most organizations don’t have a skills problem in the abstract. They have a follow-through problem. They make big plans. Then the plan runs into the calendar, the budget, the manager who hates uncertainty, and the team that’s already stretched. The result is “change theater”: new org charts, new words, new training modules, and the same bottlenecks.
So yes, treating change as normal could help. If you make it normal to move people internally, normal to retrain, normal to update priorities, you might actually reduce the panic. People can handle a lot if they trust the rules won’t change in secret.
But here’s my judgment: most companies don’t want “change as normal.” They want “adaptability from employees” while keeping decision-making slow, political, and centralized. They want everyone to be flexible except the parts that make leaders uncomfortable—headcount promises, clear career paths, consistent pay, and honest timelines.
The report mentions priorities like internal mobility, cybersecurity, and scenario planning. Those are fine words. They also reveal what’s really happening: companies are trying to protect themselves from shocks by making the workforce more fluid and the org more prepared for sudden pivots.
Internal mobility, for example, can be a win. Imagine you’re on a team that’s shrinking, but you can move to a growing team without quitting, without starting from zero, without begging for a referral. That’s a better deal than a layoff announcement and a “good luck out there.” Done well, it keeps knowledge inside, lowers hiring pressure, and gives people a reason to stay.
Done badly, it becomes a quiet churn machine. People get “moved” because it’s convenient for leadership, not because it fits their skills or goals. You end up with teams full of reluctant transfers, managers who didn’t ask for them, and employees who feel like spare parts. The company still calls it “agility,” but employees call it “I have no control over my career.”
The same tension shows up with AI deployment. The report points to a shift toward execution and AI. That can mean genuinely upgrading how work gets done—less busywork, faster drafts, better decisions. It can also mean a new kind of pressure: “Do more, faster, with fewer people, because the tools exist.”
Say you’re in customer support. If AI can handle a chunk of simple tickets, great. Unless the company uses that as an excuse to cut staff and leave the remaining people with only the hardest, most emotional cases—then measures them with the same old speed targets. That’s not resilience. That’s burnout with new branding.
Cybersecurity is another one. Everyone nods at it, and then someone pastes sensitive data into a tool they don’t understand because they’re rushing. If companies want adaptability, they can’t treat security like a once-a-year training. They have to design systems where the safest option is also the easiest option. Otherwise “agility” becomes a constant stream of small risks that add up.
Scenario planning sounds mature, too. But it’s only useful if leaders are willing to act on scenarios before the crisis hits. Most aren’t. They wait until the threat is obvious, then demand “urgent change,” then blame teams for not moving faster. If you want change to be normal, leadership has to be normal about trade-offs. You can’t ask for speed and also punish every mistake.
There is a fair counterpoint: the world really is messy right now, and rigid companies break. If you lock roles, lock budgets, and lock plans, you might protect today’s comfort at the cost of tomorrow’s survival. A company that can’t shift skills internally will shift people externally. That’s not kinder. It’s just quieter until it isn’t.
Still, the big stake here is trust. If “agility” becomes code for “permanent uncertainty,” you’ll lose your best people first—the ones who can leave. If “agility” means the company invests in mobility, clear skill paths, and honest communication, you’ll keep them and get stronger.
So the real question isn’t whether change is coming. It is. The question is who carries the cost when it arrives—and whether leaders will finally build systems that share that cost fairly.
If you were an employee, would you rather work somewhere that promises stability and breaks that promise in a crisis, or somewhere that promises constant change and expects you to live with it?