News Analysis
Research Report
The State of the Digital Workplace
In 2014, Microsoft CEO Satya Nadella inherited a company infamous for internal warfare. Stack rankings had managers competing against each other instead of building anything. The culture was toxic, and it’s not like the performance system was driving innovation.
Nadella abolished it and brought in Kathleen Hogan to build something different: a culture grounded in what psychologist Carol Dweck calls the growth mindset, the idea that ability isn't fixed, that learning matters more than knowing and that curiosity beats defensiveness.
Over a decade, it became one of the most cited cultural turnarounds in corporate history. What followed was a period of innovation and growth.
Late last month, Nadella's new chief people officer dismantled the organizational architecture that the turnaround built. Microsoft needed a shake-up.
Whether that's evolution or disruption depends on what you think went wrong, and when.
What Microsoft's HR Restructuring Actually Did
Amy Coleman, who replaced Hogan as Microsoft's chief people officer in March 2025, sent an internal memo on March 25 announcing a full restructuring of the HR function.
The departure of their Chief Diversity Officer got the most attention, of course. Lindsay-Rae McIntyre, who held the role for eight years, is leaving to become Alaska Airlines' Chief People Officer. Microsoft is eliminating her position entirely.
But the more consequential changes are structural.
A new People & Culture team under Leslie Lawson Sims absorbs the former Culture & Inclusion function. A Workforce Acceleration team, led by Justin Thenutai, takes on skilling, redeployment, workforce planning and what Coleman calls "human-agent collaboration," a function with no direct precedent at Microsoft or its peers.
People analytics, a function Dawn Klinghoffer built up over more than 20 years into one of the most respected operations of its kind in corporate HR, gets folded into Employee Experience.
Three other long-tenured HR leaders are retiring at fiscal year end: Kristen Roby Dimlow, nearly 30 years leading talent acquisition and total rewards; Chuck Edward, 22 years in HR business partnerships; and Klinghoffer herself. Combined with McIntyre's departure, that's more than 150 years of institutional knowledge leaving in a matter of months.
You can redraw an org chart in an afternoon. Replacing that takes longer.
"The pace of change is exceeding what our current operating model and decision rhythms were built for," wrote Coleman in her memo. "We're no longer being asked to scale for stability; we need to scale for adaptability."
That framing works, but at a cost.
Each Move Might Make Sense. Together, They're a Gamble.
Integrating culture and inclusion into a broader people team embeds that work rather than siloing it. Consolidating people analytics into employee experience creates tighter feedback loops between insight and decision. Standing up a dedicated Workforce Acceleration team signals that AI-era workforce transition needs dedicated infrastructure, not just goodwill from existing teams.
The risk is running all of them at once, during significant leadership turnover, inside a workforce still absorbing layoffs, a new performance culture and a return-to-office mandate.
SHRM's 2025 survey found that organizations following change management best practices were 2.6 times more likely to report successful AI implementation. That ratio applies to any transformation where humans have to change how they work. Gartner found 88% of HR leaders haven't realized significant business value from AI tools. McKinsey puts large-scale transformation failure rates at roughly 70%.
The one move I question is people analytics being moved under EX. Independent analytics functions earn their credibility by not reporting to the people whose programs they're evaluating. You want objective measures, not something that looks good because it makes their boss look good.
Klinghoffer spent two decades building something that worked, in part because of that independence. Embedding analytics inside employee experience creates tighter loops, but it also puts data interpretation inside a team with its own delivery agenda. Once that independence is gone, it's hard to get back.
Slow Transformation Has Its Own Problems
Moving too fast can cause adoption and change management problems. But being too slow can mean the change never takes the way you hoped.
You know how this goes. One business unit launches a pilot. Leadership declares it a success. The steering committee moves on to the next initiative. Two years later, an internal study into why adoption stalled finds the organization never changed anything. It just added new language on top of old behavior.
Deloitte's 2026 Global Human Capital Trends report found 85% of organizations say developing workforce adaptability is critical. Yet only 7% say they're leading in that area, and just 6% report making real progress on designing human-agent interactions at work.
Conference
Apr
22
HR Tech Europe Amsterdam 2026
Register
Conference
Apr
27
Gartner Digital Workplace Summit London 2026
Register
Conference
Jun
2
Gartner Application Innovation & Business Solutions Summit Las Vegas 2026
Register
Webinar
On demand
Do Learning Programs Really Work? How to Turn Education Into Engagement In Healthcare
See how leaders are using learning programs to build trust with healthcare professionals and create measurable engagement.
Watch Now
Coleman can’t afford to risk that inaction and lack of progress. Microsoft’s choice to prioritize adaptability over stability is a response to exactly that.
You can potentially argue with her execution choices or the decision to try to dogpile years of changes into a short period of time, but the logic behind the choice is harder to dismiss. And if you know Microsoft's history, the logic makes even more sense.
Coleman Knows Microsoft's History Better Than Anyone
Microsoft didn't miss mobile because it lacked smart people. It had plenty. It missed mobile because the organization was too full of its own assumptions and too slow to move at the speed necessary to compete.
The cloud pivot required a CEO to execute at the pace the market demanded. The growth mindset era under Nadella and Hogan, for all its genuine success, still took years to embed across 200,000 people. Microsoft has a specific relationship with big moments: It tends to understand them intellectually before it moves organizationally.
Coleman spent years watching that pattern from inside the people function.
The Workforce Acceleration team is the most apparent response to that historical hesitancy. If Coleman believed the existing HR structure would drive human-agent collaboration at the pace the business now requires, she would have handed the mandate to an existing team.
Instead, she built something with no precedent at Microsoft or at any peer company. You build that kind of team when you've watched an organization move too short or too slow in the past.
Whether she's pushing harder than the moment requires, or exactly as hard as Microsoft's own track record demands, is a question only the next two years will answer. While moving fast and breaking things has never been part of the Redmond ethos, a focus on adaptability might make things feel as if they are breaking.
Before you draw conclusions about what this means for your own organization, it's worth noting what Microsoft can absorb that most can't.
Before You Copy, Can You Afford to Fail Like Microsoft?
Microsoft has the capital, the internal AI infrastructure and the scale to absorb a failed experiment in ways most HR organizations can't. If the analytics merger costs them rigor, they can rebuild. If Workforce Acceleration under-delivers, they restructure. Most organizations watching this don't have that room.
IBM's internal AI transformation took six years to reach its headline numbers: 2.1 million employee conversations handled annually, HR operational costs down 40%, employee net promoter scores climbing from -35 to +74. Six years of sustained work — not a memo.
Microsoft is announcing a comparable destination alongside a dozen other structural changes all at once.
The question for anyone contemplating a similar move is what your organization can actually absorb, and whether your transformation plan is built around that ceiling, or borrowed from a company that isn’t a true peer.
IBM might have run things too slowly. Microsoft may be trying to run it too fast. They both could afford to make that mistake in the short-term. What they couldn’t afford to do was stand still. That should be the lesson as organizations take on AI-driven changes with boldness or trepidation.