What we've learned from Microsoft's own AI transformation

AI is reshaping work faster than any organization has fully mastered. Across industries, the conversation has shifted from what AI can do to how companies can use AI to create business value and expand what people are able to achieve. At Microsoft, we believe the organizations that succeed will be what we call Frontier Firms: human-led, but increasingly AI-enabled. That responsibility begins with how AI is built and continues through how it is put to work: AI should expand human capability while people retain meaningful control, judgment and accountability. We committed to being Customer Zero, learning through our own transformation so we could help others navigate their own.

Our employees have experimented with AI, while leaders have set ambitious goals and challenged teams to reimagine how we work to achieve more than was possible before. We created cross-company councils spanning corporate functions, go-to-market and engineering to share best practices and learn together. We asked everyone to challenge their fixed mindsets and embrace the growth mindset we have cultivated for more than a decade. That work is producing measurable results: for a sales team deal close rates increased by 20%¹; selected supply-chain workflows cut cycle time by up to 75%²; and a nine-person engineering team shipped an initial product release in 35 days.³

As proven approaches emerged, we codified them into case studies so we could accelerate transformation, scale what worked and learn from what did not. Just as importantly, we knew that if we wanted to help customers realize the full value of AI, we had to do the work to transform ourselves first. Our own first-hand experience needed to be a source of learning we could share with others.

We have been sharing Microsoft’s Frontier Playbook with customers as a practical guide to our AI transformation journey, including what we’ve learned, what has worked so far and where we’ve grown from failures. Drawing on hundreds of AI transformation efforts across the company, the playbook captures what we are learning as we redesign work, build new capabilities, measure impact and help people grow alongside AI.

The playbook also reflects important truths: transformation is hard, and learning is the durable superpower. Among the many insights gained from our successes and our failures, five lessons consistently stand out.

1. Start with the business outcome, not the technology

We initially treated AI like a traditional technology rollout: deploy the tools, provide training, drive adoption. We learned that access and usage do not equal transformation: a tool licensed to over 200,000 people does not change how the work gets done.

Early sales usage made this clear. Despite broad deployment, usage plateaued and impact did not materialize. Rather than push adoption harder, the team started from the business goals — deliver more value to customers, win deals and improve employee experience. They mapped how account managers spent their week and identified the best tools for the moments that mattered most: an Analyst agent for pipeline, a Deal agent for deal packages and Researcher for deep customer understanding. Weekly peer-led huddles turned experimentation into habit and scaled best practices to everyone on the team. Within the group, adoption of priority use cases tripled, revenue per account manager rose 9.4% and close rates were 20% higher.⁴

Success still required investment in helping people build new skills, experiment with new ways of working and learn from one another. But when leaders focused on a clear business outcome and what mattered most to the person doing the job, rather than AI adoption itself, conversations shifted from using AI to creating value.

2. Redesign the entire workflow, not just individual tasks

One of our biggest lessons came from reimagining workflows end to end, not applying AI to existing steps. Early efforts helped people complete familiar tasks faster but rarely transformed outcomes. Adding agents to a broken process still leaves a broken process — speeding up one step just creates a longer queue at the next.

Our cloud supply chain team simplified its processes before reimagining them with agents. Supply chain experts and engineers worked side by side, first mapping and simplifying end-to-end workflows, then created a single source of truth so every agent reasoned from the same data. With that foundation in place, they deployed more than 100 purpose-built agents across planning, sourcing, fulfillment and logistics. Those agents investigate shifts in demand and model capacity while comparing transportation options across air, land and sea on cost, timing and carbon impact — complexity few teams could manage alone. Cycle time fell by up to 75% in selected workflows.

The shift isn’t only about speed, it’s about adding new value by improving what the team can see, anticipate and act on. Within defined permissions and approval thresholds, agents have progressed from answering questions to helping planners update or cancel purchase orders directly. Planners who once spent five to seven days tracing why a demand plan changed can now get an answer in hours, and sometimes in less than 20 minutes. That makes it possible to analyze changes as planning cycles unfold, model more scenarios, build better contingency plans and identify risks earlier — helping the team make better decisions and improve the performance of the supply chain.⁵

We are seeing the same shift in software engineering, where the opportunity extends beyond generating code faster to redesigning how teams plan, build, test and evaluate products with agents across the workflow.

We’ve found the largest gains come when teams step back and redesign how work should flow across people, process and technology from start to finish — including what agents can access and do, how their actions are monitored and where people must review, approve or intervene. AI is most powerful when all three advance together.

3. Put employees at the center of transformation

The people who do the work know where processes break down, where judgment matters and where AI could help — insights that no process map can fully capture. Their expertise needs to shape transformation from the start. Leaders are responsible for setting a clear ambition, helping employees build the skills to contribute and giving them a meaningful role in deciding how the work changes.

At Microsoft, we are creating hands-on ways for employees to build those skills. An early in career development program PRAISE pairs emerging engineers with experienced preceptors and AI-assisted learning, helping newer engineers contribute to complex work while developing their craft.

Camp AIR is a multi-week AI transformation accelerator that helps cross-functional teams learn new AI capabilities while redesigning how they work together around a real business challenge. An early pilot taught us that AI transformation is a team sport and that tools and training alone were not enough. While individuals could learn new technologies independently, meaningful and lasting change occurred when teams learned, experimented and adapted together. Teams needed candid conversations about how AI would reshape roles and workflows, along with the freedom to experiment safely and build confidence in new ways of working. We could not future-proof all jobs as they exist today, but we could help employees future-proof their careers by developing the skills, adaptability and mindset needed to succeed as work evolves.

That lesson became a core design principle of Camp AIR and has helped the program scale to more than 3,000 engineers across that organization.

The team behind Copilot Cowork shows what this can look like in practice. The nine-person team of engineers, designers and product managers was given the freedom to rethink how a product gets built, with AI embedded from day one. Working alongside agents, their roles expanded into what they called meta-engineers, meta-designers and meta-PMs. Together, they shipped an initial release in 35 days and documented what they learned so other teams could build on it.⁶

In our experience, leaders set outcomes and accountability, while the people closest to the work see where AI adds value and where human judgment must stay central. Managers connect the two, and their role-modeling and support has been one of the strongest predictors of success. Our research bears this out: when managers actively model AI use, reported value from agentic AI rises 17 points and trust in it rises 30 points — and employees on teams where managers create psychological safety are 1.4 times as likely to be high-frequency users of agentic AI. Where employees have context, capability and agency, they can become the engine of transformation.

4. Use AI to expand what people can do

We started where many companies start: automating tasks to increase efficiency. That value is real, but only the beginning. We realized over time the larger opportunity is “Capability Add”: combining human and AI strengths to achieve outcomes that were previously impractical or impossible. Think of it as an equation: CI + AI = CA. Continuous improvement takes waste out and AI adds capability in. Together, they produce Capability Add — output with higher strategic value. Continuous improvement alone results in a leaner version of the old company; Capability Add creates a different one. This equals transformation.

In our latest Work Trend Index, 58% of AI users said AI helps them do work they could not do before — it was 80% among advanced users. In our case examples, it looks like predicting a quality failure instead of catching it or exploring twenty options where a team had time for three.

This broader view shapes how we measure ROI. We like to say efficiency is the floor; capability is the ceiling. Usage and adoption, along with improvements in speed, quality and cost, are important signals. But the ultimate measure is whether AI improves customer and employee experiences, drives growth and innovation, reduces risk and expands what the organization can accomplish. Because those outcomes can take time to emerge, we also track leading indicators. For account managers, that might mean more time with customers, a stronger pipeline or better win rates before revenue gains fully materialize. For an engineer, it is not how much code AI produces, but whether the team is building better products faster.

We encourarmation recipes and lessons from Microsoft’s Customer Zero journey.

Kathleen Hogan is Executive Vice President and Chief Strategy and Transformation Officer at Microsoft, where she leads the company’s enterprise-wide strategy and transformation agenda, accelerating Microsoft’s evolution into a Frontier Firm. Previously, she served as Chief Human Resources Officer and Corporate Vice President of Microsoft Services.

NOTES

¹ Internal Microsoft sales team data based on 687 sellers of Microsoft 365 Copilot from Jan. – June 2024, as compared with sellers with low usage of Copilot. Regular usage of Copilot means sellers who use Copilot daily at least 50% of the time during the testing period.

² Based on Microsoft internal analysis of work led by a 150+ person cross-functional team between September 2025 and August 2026. As of September 2026, more than 111 agents had been deployed across cloud supply-chain workflows. Across 5 monthly planning cycles measured between April 2026 and August 2026, average cycle time declined from approximately 10 to less than 2.5 business days. Separately, across 20+ demand-plan investigations each month, average time to produce a human-validated explanation declined from five to seven days to less than a few hours, with some completed in less than 20 minutes. Results are specific to these workflows and measurement periods.

³ Based on internal project records. The 35-day period was measured from the team’s formal project kickoff to delivery of the initial release in Spring 2026. This result reflects one project undertaken by a dedicated cross-functional team and is not a companywide product-development benchmark.

⁴ Internal Microsoft sales team data based on 687 sellers of Microsoft 365 Copilot from Jan. – June 2024, as compared with sellers with low usage of Copilot. Regular usage of Copilot means sellers who use Copilot daily at least 50% of the time during the testing period.

 ⁵ Based on Microsoft internal analysis of work led by a 150+ person cross-functional team between September 2025 and August 2026. As of September 2026, more than 111 agents had been deployed across cloud supply-chain workflows. Across 5 monthly planning cycles measured between April 2026 and August 2026, average cycle time declined from approximately 10 to less than 2.5 business days. Separately, across 20+ demand-plan investigations each month, average time to produce a human-validated explanation declined from five to seven days to less than a few hours, with some completed in less than 20 minutes. Results are specific to these workflows and measurement periods.

⁶ Based on internal project records. The 35-day period was measured from the team’s formal project kickoff to delivery of the initial release in Spring 2026. This result reflects one project undertaken by a dedicated cross-functional team and is not a companywide product-development benchmark.