Executive Summary
Most MSPs approach transformation work as a technical exercise: design the solution, install the tool, train the users, close the project. In an AI-driven world, that model is breaking down. Technical readiness alone does not produce adoption, and without adoption, there is no business outcome.
During a research working session on Customer Success disciplines, contributors Luis Giraldo, Joe Markert, Denes Purnhauser, and Kevin Clune paused a hierarchy discussion to wrestle with a deeper question: where does “change leadership” fit, and how is it different from “change management”?
Joe referenced a Microsoft slide used at a recent AI event that framed the journey to becoming AI-powered across three lanes.
- Leadership: executive sponsorship, alignment to strategy, clarity and prioritization
- Human change: enablement programs, communications and community, skilling and training
- Technical readiness: secure infrastructure, policy review, business scenario expansion
His observation was that MSPs are very good at technical readiness and occasionally touch leadership, but the human change piece, the enablement and behavior change, is largely missing.
Luis pushed the group further. The industry talks a lot about change management, but in Customer Success work “what we are talking about is change leadership.” He argued that MSPs are being asked to lead customers through change, not just manage tasks around it.
This paper clarifies that distinction and explains why it matters more than ever in the age of AI.
Why This Distinction Matters
The group originally set out to clarify methodology structure. The conversation quickly shifted toward a deeper and more urgent topic. Even the most polished methodology will fail if the client’s users do not adopt the change.
AI is the clearest demonstration of this. As Luis has written elsewhere, deployment is technical and adoption is emotional. MSPs often focus on licensing, security, governance, and rollout plans. Meanwhile, users are asking a different question. They are not wondering how an LLM processes data. They are wondering if the tool will replace them. When that fear is ignored, adoption stops before it starts.
Luis summarized this during the session as well. “It is really important to actually lead the customer through it, especially now in this AI era, where there is a ton of ambiguity and confusion.” The MSP’s responsibility now extends beyond delivery into guiding people through disruption.
Joe reinforced that MSPs frequently conflate a completed installation with a completed transformation. “The technical readiness is what most MSPs focus on,” he shared, “but the part that is missing is the human change piece.” Without it, the tools sit unused and the promised outcomes never materialize.
The conclusion was clear. Adoption is not a technical challenge. It is a leadership challenge.
What Change Management Typically Covers
In most organizations, change management refers to the tactical activities used to support a transition. These include training, documentation, office hours, communication plans, and resource guides. These steps are not optional. They improve clarity and reduce friction, but they do not address motivation, alignment, or behavioral change.
Examples from the change management materials make this clear.
- “We will host a 30 minute training webinar on Day 1.”
- “Office hours will be available during Week 1.”
- “The implementation cheat sheet will be sent to the manager.”
In more complex rollouts, change management also includes physical presence and support on the ground. A technician might stand beside a team during the first few hours of an ERP migration. A simple laminated card might explain how to resolve the most common scanning errors. These touches help users get started, but they do not determine whether users stay engaged, feel confident, or understand the value of the change.
As Luis wrote in his reference article, a deployed license is worthless if the user is afraid to click the button. Change management can reduce friction. It cannot remove fear.
What Change Leadership Adds
Change leadership creates the conditions that make change possible. It aligns the project with business outcomes, secures visible sponsorship, and sets the expectations and behaviors that the organization must embrace.
The Microsoft model highlights this difference in a simple way. Leadership responsibilities include executive sponsorship, clarity, prioritization, and alignment to strategy. These items define the reason for the change and the level of organizational commitment behind it.
Luis explained the need for this shift directly. The industry may talk about change management, but in Customer Success “what we are talking about is change leadership.” MSPs cannot treat adoption as a training problem. They must treat it as a behavioral and emotional transition that requires guidance.
This aligns with one of the strongest points in Luis’s reference article. Adoption does not happen automatically. It requires breaking habits, addressing fear, and creating a safe path forward. MSPs need to shift from “Technology Installer” to “Change Leader.” This means validating concerns, framing the value, identifying champions, and tracking confidence, not just consumption.
Change management answers how users will be supported. Change leadership answers why the change matters and who must own it.
When Change Leadership Is Required
The Change Impact Scorecard provides a simple way to determine when leadership must be involved. It evaluates:
- Whether the change alters a daily habit
- Whether multiple departments are involved
- Whether resistance or fear is likely
- Whether an executive is watching the outcome
- Whether the change affects a significant portion of the staff
If the score is two or more, leadership alignment becomes mandatory. The instructions are clear. Do not proceed with technical delivery until a Change Brief has been co-authored with the client.
This moment in the process is also where the emotional side of adoption becomes visible. If the change disrupts habits, people will feel discomfort. If the change threatens identity or status, people will feel fear. If the change challenges long held processes, people will feel uncertainty. These emotions will not be resolved by documentation or training alone.
Luis’s article emphasizes this reality. Users are not evaluating AI based on the elegance of the model. They are asking if the tool will replace them or expose their weaknesses. Change leadership acknowledges these emotions so that the organization can pivot toward value.
The Four Components of Change Leadership
Across the discussion and materials, four recurring components of effective change leadership emerged.
1. Business Framing
Change leadership starts with a clear reason for the change and a compelling explanation of the cost of inaction. Statements such as “Competitors are delivering campaigns faster and our margins will erode” create urgency and meaning.
2. Behavioral Clarity
Leaders specify exactly what users will do differently. They describe observable behaviors such as “Use the handheld scanner immediately upon unloading.” This eliminates ambiguity and allows progress to be measured.
3. Safe Experimentation
A small pilot group is used to test the change before scaling it. This approach builds confidence and reduces disruption. As Luis often notes, early champions can influence culture faster than any slide deck.
4. Sponsorship and Governance
Formal acknowledgment that the organization must lead the change, not just experience it, establishes accountability. When leaders publicly own the reasoning and the path forward, fear decreases and participation increases.
These components map directly to the ideas in Luis’s reference article. Address the fear, identify excited champions, measure confidence, and guide the organization from uncertainty toward value.
Where Change Leadership Fits in the Customer Success Methodology
The group concluded that change leadership is not a separate discipline. Instead, it is a strategic capability that spans across disciplines and informs how they operate.
Denes described it as part of the fabric of Customer Success. It influences how goals are set, how assessments are conducted, how deliverables are interpreted, and how processes guide clients from current state to desired state.
- Change management lives inside the execution layers.
- Change leadership lives in the intent setting layers.
Both are necessary. Only one determines whether change will actually happen.
Conclusion: The Leadership Gap Is the Adoption Gap
AI has made one truth impossible to ignore. Deployment is technical. Adoption is emotional. The MSPs that succeed in this era will not be the ones who simply understand algorithms. They will be the ones who understand human anxiety, habit disruption, and organizational behavior.
Customer Success is not about installing tools. It is about leading clients through change. Change management helps people through the steps. Change leadership makes the change meaningful, possible, and durable.
The distinction marks the difference between delivering technology and delivering transformation. The MSPs that master change leadership will earn deeper trust, drive stronger outcomes, and unlock far more value for their clients in the years ahead.
