Three stories landed in my inbox this week. On the surface they have nothing to do with each other. One is about semiconductor manufacturing in Japan. One is about water. One is about Xbox. But read them together and there's a pattern underneath all three that I haven't been able to shake.
The pattern nobody's naming
Here's what connects them: the benefits of AI are being privatised. The costs are being socialised.
Micron's shareholders capture the upside of HBM demand. Nvidia captures the upside of GPU scarcity. Microsoft captures the upside of AI productivity gains across its enterprise customer base. The returns flow to investors, executives, and shareholders.
But the water goes to Phoenix communities who didn't vote for this and won't benefit from it. The job losses go to game studio employees who didn't design the Activision acquisition strategy. The ecological footprint goes unreported in sustainability disclosures. The costs land on people who had no seat at the table when the decision was made.
That's not a technology story. It's a distribution-of-consequence story. And it's the one that rarely gets told.
The same structure underlies all three stories: returns flow up to those who invested; costs land on those who didn't decide.
And nobody's managing the people in the middle
Here's what I keep coming back to. In each of these three stories, there are people who did nothing wrong, made no bad decisions, and are still absorbing the cost of someone else's strategy.
The Xbox studio employees who didn't design the Activision acquisition. The Phoenix residents whose water table is being quietly drawn down to cool servers they'll never use. The Hiroshima factory workers whose livelihoods now depend on a geopolitical chip war they can't influence.
None of them had a seat at the table. None of them were part of the decision. And in almost every case, no one is actively managing what this transition means for them. Not with communication. Not with support. Not with any kind of deliberate change process.
The technology arrives. The people side gets left behind. And six months later, everyone wonders why things feel broken.
This is the pattern I've been watching across every major technology shift for more than twenty years. It's not new. What's new is the speed and the scale. AI is moving fast enough that the gap between "decision made" and "people affected" is shrinking to almost nothing — and organisations are not set up to manage that.
What this means if you're leading through it
Most leaders I speak to are focused on the technology decisions: which AI tools to adopt, how to integrate them, what the ROI looks like. Those are legitimate questions. But they're the easy half.
The harder half is the people side. Who in your organisation is most exposed to what's coming? Which teams are already feeling the pressure of AI-driven change — even if nobody's named it as such? Where does your change risk actually sit, before the next wave lands?
The organisations that get ahead of this won't be the ones with the best AI stack. They'll be the ones who invested, early, in helping their people understand what the technology does, why it's being introduced, and what it means for them personally.
Microsoft's "company transformation" announcement will be studied for years as a case study in how not to communicate change at scale. The announcement was clinical, corporate, and came weeks after the decisions had already been made. The people affected — employees, studio teams, game development communities — found out the same way everyone else did. Via a press release.
You don't have to do it that way. But you do have to choose not to — before the moment arrives, not after.
The question worth sitting with
Three stories. One pattern. The benefits of AI are real. The investment numbers are staggering. The productivity gains are coming, and for many organisations they'll be genuinely transformative.
But transformation always has a human cost. The question isn't whether there will be one. The question is: who's managing it, and who's being left to absorb it alone?
That's not a technology question. It's a change management question. And it's the one that tends to get skipped.
