Explore the Levels of Change Management

Latest Posts Individuals Projects and Initiatives Enterprise Archives

The Role of the Change Management PMO

9 Mins

Published: April 15, 2026

When change doesn’t take hold, the reason usually isn’t found in tighter schedules, additional controls, or more detailed reporting. It shows up in moments that rarely make it into status decks: when people hesitate to use a new system, revert to old habits, or quietly work around a process that doesn’t feel usable. Adoption, confidence, and sustained behavior change are what ultimately determine whether a project delivers real value, and those outcomes don’t happen automatically once a solution goes live.

This tension has fueled long-running debates about whether change management belongs inside the Project Management Office (PMO) at all. Some argue the disciplines are incompatible. Others attempt to bolt change activities onto existing governance and hope for the best. Neither approach is reliable, but a change management PMO is.

What Is a Change Management PMO?

A Project Management Office is a function within an organization that brings structure and consistency to how projects are planned, governed, and delivered. Traditionally, PMOs focus on managing timelines, budgets, scope, standards, and reporting so leaders can see progress and make informed decisions across a portfolio of initiatives.

A change management PMO builds on this foundation by expanding the focus beyond delivery to enabling adoption and sustaining outcomes. Its purpose is to ensure the people side of change is addressed with the same discipline and visibility as technical execution, creating greater project consistency, reducing adoption hurdles, and providing a clearer line of sight between delivery and realized value.

Understanding Change Management

Change management focuses on how individuals move from a current state to a future state. Projects deliver solutions, such as new systems, processes, structures, or ways of working, and change management is the people-focused science that ensures those solutions are actually adopted, used correctly, and sustained over time.

This distinction is critical. Projects can be completed successfully from a technical standpoint and still fail to deliver value if people do not understand the change, support it, or feel equipped to work in the new way. Change management addresses this gap by focusing on readiness, engagement, capability, and reinforcement, all of which determine whether change becomes part of day-to-day work.

The Role of ADKAR in a Change Management PMO

To manage change effectively, organizations need a way to understand how individuals experience it. Prosci’s ADKAR Model describes the five building blocks individuals must achieve for successful change:

Awareness of the need for change
Desire to support and participate in the change
Knowledge of how to change
Ability to apply new skills and behaviors
Reinforcement to sustain the change over time

In a change management PMO, ADKAR serves as a diagnostic lens helping leaders and project teams understand where and why people aren’t adapting and adopting. For example, resistance may stem from a lack of awareness regarding a new process rather than a lack of skill, or adoption may stall as employees drift back to old habits once training ends and no reinforcement follows. ADKAR insights allow a change management PMO to guide targeted interventions and better support sponsors and managers amidst the change process.

The Prosci ADKAR Model

ADKAR model outlining five stages: Awareness, Desire, Knowledge, Ability, and Reinforcement to support and sustain change

The Role of the PMO in Change Management

Traditionally, a PMO establishes frameworks, standards, and governance to bring order to complex portfolios of work. In a change-heavy environment, the PMO’s role expands from governing projects to enabling successful change. This includes:

Identifying Change-Related Risks Early

One of the PMO’s most valuable contributions to change management is risk visibility. While project risks often focus on scope, schedule, or technical dependencies, change-related risks are rooted in people. Common risks that negate change include:

Low awareness or understanding of the change
Weak sponsorship or inconsistent leadership messaging
Change saturation across teams
Insufficient capability or capacity to adopt new ways of working

A change management PMO incorporates these risks into standard assessment and review processes, so they can be identified and addressed before they become long-term issues.

Stakeholder and Communication Management

A change management PMO helps reduce the noise and confusion that often accompany multiple, overlapping changes. It establishes feedback loops that surface questions, concerns, and resistance early, so leaders have the opportunity to respond before issues harden.

Just as importantly, the change PMO reinforces consistent messaging about both what is changing and why it matters, so people can connect their daily work to the broader intent of the change. It’s the PMO’s job to support ongoing dialogue that keeps leaders, managers, and impacted employees aligned throughout the change journey.

Upskilling Internal Teams for Change

Sustainable change does not depend on a small group of specialists. It depends on leaders, managers, and project teams who understand their role in driving adoption. The change management PMO supports this by embedding change capability into project roles, providing training and tools for sponsors and people managers, amd reinforcing consistent expectations across initiatives.

Tracking KPIs and Adoption Metrics

A change management PMO looks beyond delivery milestones to incorporate metrics that reflect:

Employee adoption and usage trends
Stakeholder engagement and sentiment
Progress through key change milestones

These insights are not used to police teams, but to guide leadership so they know where to reinforce, where to intervene, and where change is at risk.

Resource Allocation and Support

In change-heavy environments, teams are often expected to absorb new systems, processes, and behaviors on top of their existing workloads. Without intentional coordination, even well-designed changes can fail simply because people do not have the time, energy, or support required to adopt them. A change-focused PMO helps leaders account for a change’s impact when sequencing initiatives, not just technical dependencies or funding availability.

Integrating Change Management into PMO Processes

For organizations with an established PMO, integrating change management does not require starting from scratch. Most PMOs already oversee activities that directly influence whether change succeeds – portfolio reviews, governance checkpoints, risk assessments, and status reporting – even if those activities are not explicitly labeled as “change management.”

The opportunity is more about expanding the lens through which existing processes are used. Instead of focusing solely on delivery feasibility and progress, a change-enabled PMO begins to ask how people will experience, adopt, and sustain what is being delivered. Readiness, sponsorship, and adoption risk become part of the same conversations as scope, schedule, and cost.

This shift requires two things: a clear lifecycle framework that keeps change visible from initiation through sustainment, and a set of integration principles that ensure project management and change management are working together, not in isolation.

Using the Prosci 3-Phase Process as a Unifying Framework

The Prosci 3-Phase Process gives PMOs a practical way to align governance and delivery activities with how people move through change over time. Rather than treating change management as a one-time effort or a late-stage add-on, the process ensures that adoption considerations are addressed early, managed intentionally, and reinforced after go-live.

The Prosci 3-Phase Process

Three-phase change management process showing Prepare Approach, Manage Change, and Sustain Outcomes

In Phase 1 – Prepare Approach, the PMO helps set initiatives up for success by expanding early-stage governance to include readiness and adoption risk. This means assessing change characteristics and organizational readiness alongside technical feasibility, clarifying sponsorship and leadership roles early, and aligning project objectives with the outcomes the change is meant to achieve.

As initiatives move into execution in Phase 2 – Manage Change, the PMO reinforces consistency across projects by keeping integrated project and change plans aligned. Existing reporting and review mechanisms are used to track delivery progress and to monitor stakeholder engagement, communication effectiveness, and emerging adoption risks. This allows people-related issues to surface alongside schedule and budget data, rather than after problems have already taken hold.

In Phase 3 – Sustain Outcomes, the PMO helps address a problem many organizations know well: once a solution goes live, attention shifts elsewhere. A change-enabled PMO treats this moment differently. It plans for reinforcement, continues to review adoption after implementation, and pays attention to whether new ways of working are actually sticking. What’s learned during this phase is then carried forward to future initiatives, helping the organization improve how it manages change over time.

The Five Dimensions of Integration

While the 3-Phase Process provides a lifecycle view, Prosci’s research shows that integrating change management and project management requires alignment across five dimensions.

The first dimension is people. This dimension focuses on who executes project management and change management work and how those roles are structured and governed. Organizations may embed a dedicated change practitioner on a team alongside a project manager, rely on a centralized change function that supports multiple initiatives, combine internal and external resources, or, in some cases, assign both responsibilities to the same individuals. A change PMO brings consistency to these models by clarifying roles, relationships, and accountability across initiatives, regardless of how teams are structured.

The second dimension is process. This area addresses how the phases, activities, and milestones of project management and change management come together across the project lifecycle. Integration at the process level enables better information exchange, more intentional sequencing of work, and alignment around milestone timing and desired outcomes. A change-focused PMO reinforces this alignment by ensuring change management activities begin early – ideally at project initiation – so readiness and adoption considerations shape delivery decisions from the start.

The third dimension is tools. Project management and change management frequently use similar tools and deliverables, such as communication plans, risk assessments, training plans, and schedules. When these tools are developed separately, teams often duplicate effort or miss critical insights. A change management PMO helps integrate shared tools so they reflect both technical execution needs and people-related risks, promoting collaboration and a common understanding of progress.

The fourth dimension is methodologies. While integrating people, process, and tools happens primarily at the project level, methodology integration occurs at the organizational level. This dimension focuses on creating a standard approach to project delivery by intentionally combining project management and change management methodologies. The change management PMO supports this effort by reinforcing a single change management methodology, which gives leaders, project teams, and front-line employees a common language during periods of change.

The fifth dimension is results and outcomes. This dimension brings integration into focus by establishing a shared definition of success. Project management and change management are complementary disciplines that contribute to improved organizational performance. Under a change management PMO, success is defined not only by delivery milestones but by adoption, usage, and sustained performance.

Integrating Change Management into the Project Management Office

For organizations establishing a new PMO, there is a great opportunity to design change capability from the outset. Here’s how organizations can set up a change management project management office as an operating model:

Step 1: Assess Organizational Readiness

Start by evaluating how much change the organization can realistically absorb. This means looking ahead at the volume and impact of upcoming initiatives, understanding cultural and operational capacity, and learning from past change efforts that struggled or succeeded.

Step 2: Define the PMO’s Structure and Roles

Next, clarify how change management will be owned and executed within the PMO. This includes defining where change responsibilities sit, how sponsors and people managers are expected to contribute, and who has decision rights related to readiness, prioritization, and sustainment.

Step 3: Develop a Change Management Strategy

With roles established, define how the organization will approach change at a portfolio level. This strategy sets consistent expectations for sponsorship, communication, and enablement across initiatives while providing a shared lens for evaluating adoption risk.

Step 4: Implement Change Management Processes

Then, embed change management into how work actually gets done. This means integrating readiness and adoption considerations into governance checkpoints, aligning stakeholder engagement and communication practices, and using shared planning and reporting mechanisms to surface people-side risks.

Step 5: Train and Equip Teams

A change management PMO succeeds by building capability, not dependency. Equip sponsors to lead visibly, managers to support their teams through transition, and project teams to anticipate and address adoption challenges.

Step 6: Monitor and Adjust

Finally, treat change as a dynamic process. Continuously track adoption, engagement, and emerging resistance, and adjust strategies as conditions evolve. Monitoring progress and responding in real time helps sustain momentum and ensures changes translate into lasting outcomes rather than short-term compliance.

Man-Speaking-group-discussion

Measuring the Impact of Change Management in PMOs

To understand whether change management efforts are working, a PMO has to track a focused set of metrics that show how well change is being adopted and sustained:

Employee adoption rates: Measures the percentage of impacted employees who have adopted the new processes, tools, or ways of working. Adoption rates are a primary indicator of whether change efforts are translating into real behavior change.
Usage metrics: Tracks how frequently and effectively new systems or processes are being used. These metrics help distinguish between surface-level compliance and meaningful adoption, and often reveal where additional training or support is needed.
End-user satisfaction and engagement: Gathers feedback on how employees are experiencing the change. Surveys and qualitative input help surface friction points, sentiment, and areas where communication or enablement needs to be adjusted.
ADKAR-based progress indicators: Uses the ADKAR Model to assess where individuals are progressing or getting stuck so targeted interventions can help them overcome their resistance.
Project success metrics: Includes traditional delivery measures such as schedule, budget, and scope performance. When viewed alongside adoption data, these metrics help leaders understand how effectively change management is contributing to overall project outcomes.

Together, these measures create a continuous feedback loop that allows the PMO to monitor progress, identify risks early, and refine its approach.

Frequently Asked Questions

Why is it important to integrate Change Management into a PMO?

Integrating change management into a PMO increases the likelihood that projects deliver real, lasting value. While project management focuses on delivering solutions, change management ensures those solutions are adopted, used correctly, and sustained. When change is integrated into the PMO, organizations align project goals with business outcomes, address resistance earlier, and provide leaders with better visibility into adoption risks across the portfolio.

What are the key components of a Change Management PMO?

A change management PMO is defined by capability, not structure alone. Core components include a shared change framework (such as the Prosci 3-Phase Process) to create consistency, clearly defined roles and responsibilities for leading and supporting change, intentional approaches to sponsorship and communication, and processes for monitoring adoption and outcomes.

How can organizations assess their readiness for a Change Management PMO?

Organizations assess readiness by conducting a Change Characteristics Assessment and an Organizational Attributes Assessment. These evaluations examine the scope and impact of upcoming changes alongside the organization’s culture, capacity for change, and track record with adoption. Together, they help leaders identify where additional structure, sponsorship, or change capability is needed before establishing a change management PMO.

What best practices should be followed when building a Change Management PMO?

Best practices begin with clearly defining the PMO’s structure and roles so that responsibility for driving change is clear and consistent. A well-defined change management strategy then provides direction for how initiatives are approached, aligned, and prioritized across the portfolio. Just as importantly, organizations invest in training and resources that equip leaders, managers, and teams to successfully adopt new changes. Ongoing communication keeps stakeholders informed and engaged, while regular monitoring and feedback help the PMO adapt its approach based on what is actually happening on the ground.

The Change-Enabled PMO

A change management PMO does not replace traditional project discipline. It builds on it. By intentionally integrating the people side of change into how work is prioritized, governed, and measured, organizations gain clearer visibility into adoption risks, stronger alignment between delivery and outcomes, and greater confidence that change will take root.

Most importantly, a change-enabled PMO treats change management as an organizational capability, not a one-time activity tied to individual projects. In a world where transformation is constant, the most effective PMOs help organizations turn strategy into action, and action into lasting results.

Change Done Right Starts Here Accelerate adoption, minimize disruption, and maximize ROI on your must-win projects while building lasting organizational change capability.

Prosci

As the global leader in change management, Prosci helps organizations turn complex change into something people understand—so they can act with confidence and deliver results. Built on more than 30 years of research, Prosci partners with enterprises to scale change, enable adoption, and realize outcomes across complex transformations, including ERP and AI. Our work brings clarity and structure to change, helping leaders move from strategy to action and ensure results endure. That’s what change done right looks like.

See all posts from Prosci

5 Levels of Change Management Maturity

Organizations are facing larger and more frequent changes in the current economic climate. A changing marketplace, empowered workforce and technological advancements have created an environment where change is now a part of everyday business. In this environment, organizations are beginning to recognize the importance of building the competency to rapidly and successfully change. Prosci’s Change Management Maturity Model, based on benchmarking research, describes the varying levels of change management capabilities across organizations. The maturity model has five levels, ranging from no change management to organizational competency. Each level involves more attention and management of the people side of change. Below is a detailed explanation of each level as well as the action steps your organization can take to move to the next level of the model. The article concludes with research data on Maturity Model levels from Prosci's Best Practices in Change Management – 11th Edition. Level 1: Ad Hoc or Absent Change Management At Level 1 of the organizational change management maturity model, project teams are not aware of change management and do not consider it as a formal approach for managing the people side of change. Use at the Project Level: Change management is applied on a project only as a last resort when employee resistance jeopardizes the success of the project. Level 1 integration between project management and change management Change management is reactive and an add-on to the project. No integration with project management takes place at the beginning of the project. Projects at this level can have one or more of the following characteristics: Project leadership is focused only on the technical side of the project including funding, schedule, issue tracking and resource management Communications from the project are infrequent and delivered on a need-to-know basis Employees find out about the change first through rumors and gossip rather than structured presentations Executive support is only evident through funding authorization and resource allocation; there is no active and visible sponsorship People managers have little or no information about the change and have no change management skills to coach their employees through the change process Employees react to change with surprise and can be very resistant Productivity slows and turnover increases as the change nears full implementation Steps for moving to Level 2 Attend change management training, purchase change management tools and resources, or engage change management consultants Apply change management to isolated projects and use change management techniques to help projects that are currently experiencing resistance to change Level 2: Change Management on Isolated Projects In Level 2, elements of change management begin to emerge in isolated parts of the organization. The effort to manage the people side of change is infrequent and is not centralized. Characteristics of this level are: A large variation of change management practices exists between projects with many different change management approaches applied sporadically throughout the organization; some projects may be effectively managing change while others are still in Level 1 There are elements of communication planning, but there is little sponsorship or coaching People managers have no formal change management training to coach their employees through the change process Change management is typically used in response to a negative event Little interaction occurs between the isolated project teams using change management; each new project “re-learns” the basic change management skills Level 2 change management and project management integration In Level 2, projects apply change management when resistance emerges or when the project nears implementation. Only isolated projects use change management at the beginning of their project. Some elements of communication planning occur early in the lifecycle. At this stage, change management is not fully integrated into project management. On projects that use change management, the project team is aware and knowledgeable of change management. In certain instances, a change management advocate can encourage the integration of change management and project management. Steps for moving to Level 3 maturity Create knowledge about the different change management initiatives used in the organization and begin research in change management best practices Create clusters of project teams applying change management principles Begin collection of knowledge and tools across the organization and celebrate change management successes Begin building support for using change management with executives and senior leaders who oversee multiple projects Level 3: Change Management on Multiple Projects At Level 3, groups emerge that begin using a structured change management process. Change management is still localized to particular teams or areas in the organization. Organizations at this level can have one or more of the following characteristics: Multiple projects are using structured change management processes, although these approaches and methodologies may be different Some elements of knowledge sharing emerge between teams in the organization; teams in some departments are sharing experiences and lessons learned While change management is applied more frequently, no organizational standards or requirements exist; pockets of excellence in change management co-exist with projects that use no change management Senior leadership takes on a more active role in sponsoring change and consider this role part of their responsibilities, but no formal company-wide program exists to train project leaders, people managers or coaches on change management Training and tools become available to project leaders and team members; people managers now have the training and tools to coach frontline employees Level 3 project management and change management integration Change management is initiated at the start of some projects, with a large fraction still applying change management as a reaction to employee resistance during implementation. Teams who are successful at change management integrate change management with their overall project management methodology at the inception of the project, including communication and other change management plans. Steps for moving to Level 4 maturity Enlist executive support for applying change management on every project and for building change competencies at every level in the organization Select a common methodology that can be used throughout the organization and begin acquiring the tools and training necessary to roll out the common methodology Level 4: Organizational Change Management Standards In Level 4 of the Change Management Maturity Model, the organization has selected a common approach and implemented standards for using change management on every new project or change. Note: a common methodology does not mean a one-size-fits-all recipe; effective methodologies use repeatable steps, but they work best when tailored to the specific needs of every project. Organizations at this level can have one or more of the following characteristics: There is an enterprise-wide acknowledgement of what change management is and why it is important to project success They have selected a common change management methodology and are developing plans for introducing the methodology into the organization Executives, project teams and change leaders have access to training and tools, and people managers have formal training on their roles in change management There are individuals, groups or administrative positions dedicated to supporting change management efforts and building change management skills Executives assume the role of change sponsors on every new project and are active and visible sponsors of change Teams expect resistance and non-compliance in isolated instances, although some project teams may still not understand why they are using change management Adoption is not yet at 100% and the organization is in the process of building change management skills throughout the organization Level 4 project management and change management integration At Level 4, teams regularly use a change management approach from the beginning of their project, with change management work included in the planning phase of the project. As the project progresses, project management and change management continue to integrate to the point where they are not separable. Project teams follow both project and change management milestones. Steps for moving to Level 5 Create a formal position or staff group that is responsible for the effective deployment, training and improvement of change management competencies Correct non-compliance and analyze gaps in the organization that are not applying the selected methodology Level 5: Organizational Competency In Level 5 change management maturity, change management competency is part of the skill set of the organization. Organizations at this level can have one or more of the following characteristics: Effective management of change is an explicitly stated strategic goal, and executives have made this a priority Employees across the enterprise understand change management, why it is important to project success, and how they play a role in making change successful Change management is second nature, so commonplace that it is nearly inseparable from initiatives People managers routinely use change management techniques to help support a broad range of initiatives, from strategy changes to individual employee improvement The organization gathers data to enable continuous improvements to the common change management methodology, tools and training Extensive training exists at all levels of the organization Higher ROI, lower productivity loss and less employee resistance to change across the organization Level 5 project management and change management integration When organizations have developed a high level of change management competency, change management steps are completely integrated into project management, and change management work begins before the project kicks off. Planning and design phases have both project and change management elements and are viewed as standard practice. Change Management Maturity Model Benchmarking Research In Prosci's Best Practices research, participants identified where they were on the Change Management Maturity Model. Over half of participants (54%) fell at Level 1 (ad hoc or absent change management) or Level 2 (change management on isolated projects). Only 11% were at Level 4 or Level 5, where the organization had truly begun adopting organizational standards and building organizational competencies. Next Steps to Reach Organizational Change Management Maturity Moving up the Change Management Maturity Model improves how an organization operates and performs during times of change. There is a growing body of knowledge that shows a direct correlation between how well an organization manages the people side of change and how successful projects and initiatives ultimately are. As an organization sees examples of failed changes due to poorly managed change and successes due to effectively managed change, there is a greater sense of urgency related to moving up the Maturity Model.

How Microsoft Transformed Customer Success with the ADKAR Model

When Microsoft shifted to subscription-based licensing models for its core technology solutions and transitioned to cloud services, everything changed. Suddenly, success wasn't just about delivering software—it was about ensuring customers actually adopted and used these solutions to drive business value. Without adoption, there's no renewal. Without renewal, there's no sustained revenue. This fundamental shift made change management essential to Microsoft's business model. But they needed more than DIY approaches. They needed a scalable, research-backed methodology that could work across thousands of customers and 250,000+ employees, partners, and stakeholders worldwide. The solution? Partnering with Prosci to increase customer adoption rates. Microsoft's approach represents a fundamental shift in how they think about technology adoption—moving from a focus on features and functionality to understanding the people side of change. ON DEMAND WEBINAR: How Prosci and Microsoft Are Redefining Change Success in the AI Era Microsoft’s Director of Business Programs, Steve Green, joined Prosci for a live discussion about building change capability at scale, managing continual change driven by AI, and how organizations should prepare to lead change in the future. Watch the on demand webinar above, or keep reading to hear more about Microsoft's win with building change capability in it's CSR group. Why Traditional Customer Success Approaches Fall Short At most Software-as-a-Service (SaaS) organizations, customer success teams rely on "lighter-weight" adoption frameworks as a benefit that comes with the purchase of the service. These can work well for straightforward implementations, but when adoption gets complicated—when resistance emerges, stakeholders become cautious, or projects stall—informal approaches often fail to move the needle. Microsoft's Customer Success Organization, which works with larger customers across Microsoft 365, Dynamics, and Azure, discovered that many customers underestimate what's truly needed to adopt and realize value from new technologies. The challenge isn't technical—it's human. It's about changing behaviors, shifting mindsets, and helping people see the value in new ways of working. This realization led Microsoft to embrace Prosci's research-backed methodology and the ADKAR Model as their foundation for customer success. The methodology provided both the framework and the credibility they needed to have meaningful conversations about change with enterprise customers. How Microsoft Uses ADKAR to Drive Customer Adoption The Microsoft 365 Customer Success organization applies the ADKAR Model in four primary ways to influence buy-in and overcome adoption barriers. 1. Building awareness of the need for change management The ADKAR Model's strength lies in its simplicity and universal applicability. Microsoft's customer success managers (CSMs) use practical exercises to help customers understand the change process. For example, they might ask someone to write their name with their non-dominant hand, then explore the questions that immediately come to mind: "Why should I change?" "What's wrong with how I've always done this?" This simple exercise reveals a profound truth: even minor changes feel awkward and require conscious effort. When customers experience this firsthand, they begin to understand that everyone impacted by a technology implementation must go through this same psychological process—or the project won't achieve the adoption and success they're aiming for. 2. Backing conversations with research and data Microsoft's partnership with Prosci provides access to extensive research that CSMs use to build compelling cases for structured change management. When customers see data on project failure rates without proper sponsorship, or understand the correlation between change management effectiveness and sponsor engagement, they're more likely to invest in doing change right. Correlation of Sponsor Access with Change Management Effectiveness This research-backed approach gives Microsoft's teams instant credibility. Customers recognize Prosci as the leader in change management research, so when Microsoft professionals show up with these insights and tools, they're seen as experts in driving adoption, not just technology vendors. 3. Diagnosing and addressing adoption barriers The ADKAR Model provides a diagnostic framework for understanding where adoption efforts get stuck. CSMs use it to identify common blockers: Lack of Sponsorship: When decisions aren't getting made and stakeholders seem cautious, it usually points to weak sponsorship. Effective sponsors actively and visibly participate in the change, build a coalition of sponsorship, and communicate support and promote the changes to impacted groups. The ADKAR Model helps CSMs communicate how customers can encourage their sponsors to adopt their role and actively participate in and promote the change. ADKAR Barrier Points: By mapping customer challenges against the ADKAR elements, CSMs can quickly identify whether adoption issues stem from lack of Awareness (people don't understand why change is needed), insufficient Desire (people aren't motivated to participate), missing Knowledge (people don't know how to change), limited Ability (people can't implement the change), or weak Reinforcement (people aren't supported in sustaining new behaviors). The Prosci ADKAR Model Anticipate and Prevent Resistance: Customer success teams frequently encounter resistance as they guide customers toward new, more people-centric approaches to technology adoption. Rather than waiting for resistance to emerge and then trying to overcome it, Microsoft's approach focuses heavily on prevention—identifying potential sources of resistance early and addressing root causes before they escalate. When resistance does emerge, CSMs apply techniques like "listen and understand objections" and "show benefits in real and tangible ways" to address concerns directly. For example, when someone resists a new system or process, it's typically because they lack Awareness of why the change is necessary, don't see personal benefits (Desire), feel unprepared to make the transition (Knowledge/Ability), or haven't received adequate support to sustain new behaviors (Reinforcement). 4. Creating a common language for change One of the most valuable aspects of Microsoft's approach is how the ADKAR Model creates a shared vocabulary for discussing change with customers. Rather than talking past each other about "user adoption" or "training needs," Microsoft teams and their customers can have precise conversations about awareness building, desire creation, knowledge transfer, ability development, and reinforcement planning. This common language helps break down barriers between technical teams and business stakeholders, between Microsoft consultants and customer project managers, and between leadership and end users. Everyone understands the process, everyone knows their role, and everyone can contribute to success. Building Enterprise Change Capability at Scale Microsoft's commitment to change management extends far beyond their Customer Success teams. They've built an enterprise-wide capability that includes: Certified instructors who can deliver Prosci training globally Customized resources tailored to Microsoft's culture and customer needs Self-serve tools that partners and customers can access independently Integration with existing Microsoft frameworks and methodologies This comprehensive approach ensures that change management isn't just something that happens during customer engagements—it's embedded in how Microsoft operates as an organization. The competitive advantage of change done right Microsoft's investment in change management creates differentiation in a crowded technology market. While competitors focus primarily on features and capabilities, Microsoft can demonstrate expertise in the most critical aspect of technology success: getting people to actually use the solutions they've purchased. As Steve Green, Director of Business Programs as Microsoft explains, "We weren't unsuccessful before—we were very successful. But we always wanted to accelerate how quickly we can achieve success. Having access to research, to people who are like-minded and want to achieve success, has made a big difference." This acceleration shows up in measurably better customer outcomes, stronger renewals, and deeper relationships that extend beyond individual technology purchases to strategic partnerships. Key Takeaways for Customer Success Teams Microsoft's approach offers valuable lessons for any organization focused on driving customer adoption: People-side challenges require people-side solutions: Technology adoption is fundamentally about behavior change, not just training. Research and data build credibility: Backing recommendations with proven methodologies and statistics helps customers see the value of investing in change management. Simple frameworks enable complex conversations: The ADKAR Model's straightforward structure makes it easy to discuss sophisticated change management concepts with diverse stakeholders. Diagnosis before prescription: Understanding where adoption efforts are stuck allows for targeted interventions rather than generic solutions. Common language accelerates progress: When everyone speaks the same change management language, collaboration improves and results come faster. Change as a Strategic Capability Microsoft's transformation demonstrates what becomes possible when organizations treat change management as a core competency rather than an afterthought. By embedding a structured change management methodology throughout their Customer Success organization and beyond, they've created a sustainable competitive advantage that drives both customer success and business growth. The lesson isn't just about using better tools or frameworks—it's about fundamentally changing how you approach the human side of technology adoption. When you get that right, everything else follows.