Change management has long covered two familiar kinds of change: the rollout of new tools and technologies, and broader human-led transformations such as leadership changes and restructuring.
But that distinction starts to blur as artificial intelligence becomes woven into the fabric of organizations. Although AI is software, it has a unique capacity for open-ended, context-dependent work that involves collaborating with people. This raises the question: Should we simply treat AI like software to be deployed, or should we think of it as an active participant in our workflows whose role needs to be defined?
The instinctive answer is just to treat it like software. Organizations often try to retrofit AI into existing infrastructure and processes, assuming it can slot into the same guardrails, integrations, and workflows that support CRM systems, ERP platforms, and other enterprise software.
But maybe this isn’t the right approach. Maybe AI isn’t just a tool to be installed; it’s a participant to be onboarded. And when we force it into software-shaped boxes, we miss the opportunity to leverage its unique strengths — pattern recognition, scalability, and adaptability — in ways that complement human judgment rather than compete with it.
AI isn’t just a tool to be installed; it’s a participant to be onboarded.
In this post, we’ll look at what AI change management involves and the key considerations for enterprises as AI becomes a more integral part of day-to-day work.
What is AI change management?
AI change management is the work of guiding an enterprise through the organizational changes required to adopt AI at scale, from preparation through to day-to-day use. It includes understanding how AI changes roles and responsibilities, helping employees develop new ways of working, communicating new expectations, and adapting workflows and oversight as adoption progresses.
Those changes may mean employees spend less time producing work themselves and more time directing AI, working with its outputs, or focusing on tasks that depend on human expertise.
Why does AI require a distinct approach to change management?
Consider the difference between the launch of a new sales platform and the appointment of a new CEO. A new sales platform usually involves training sessions, a phased rollout, and minor process adjustments around a system whose role and behavior are relatively well understood. Meanwhile, a new CEO can have much broader and less predictable implications for an organization’s culture, priorities, division of responsibilities, and ways of working.
AI presents a distinct change-management challenge because it combines elements of both kinds of change. It represents both the adoption of a new technology and a broader shift in how work is distributed across an organization.
AI can reshape roles, workflows, and decision-making
For AI to function as a collaborator, enterprises need to design workflows that accommodate both human and artificial intelligence.
On the AI side, that might mean providing AI with the relevant organizational and task context much as you would when onboarding a new employee. It can also mean building human-in-the-loop mechanisms that allow AI to ask for missing information or escalate cases that require human judgment or approval.
On the human side, it might mean creating workflows where AI can act as a thinking partner rather than simply a tool for executing delegated tasks. For example, AI might help a person analyze information, explore different options, or identify relevant patterns as the work progresses. For judgment-heavy tasks, AI can synthesize evidence and surface options and trade-offs while leaving the final decision to a person. The point isn’t to pretend AI is human, but to recognize that its effectiveness can depend on how well it’s integrated into human-led workflows.
In these new human-AI workflows, employees start to act like managers of AI-assisted work, setting direction, assessing quality, and deciding when human input is needed. However, this shift introduces a risk: mistaking the speed and volume of AI-generated outputs for quality. This can result in “AI slop”: superficial or low-impact work. Employees therefore need to adopt a manager mindset, prioritizing the quality and impact of AI-assisted work, not sheer volume.
Those who actively build internal AI solutions take on an additional role, becoming something like mini product managers. Beyond building the solution itself, they may need to think about who will use it, what business outcome it serves, and how it should be maintained and governed across its lifecycle. This shift carries a different risk: employees can move beyond their traditional role boundaries without seeing all the dependencies around what they’re building. “Vibe coding,” for example, makes it possible to build a useful solution without accounting for its legal, business, operational, or technical implications.
Employees need to adopt a manager mindset, prioritizing the quality and impact of AI-assisted work, not sheer volume.
Effective human-AI collaboration depends on understanding which parts of a workflow can be delegated to AI and which still require human judgment. One way to think about that division is to separate work into three categories:
- Verifiable: Tasks AI can perform and verify against objective criteria, such as writing code that must pass predefined tests
- Judgment-based: Subjective problems where AI can help frame choices but a person still needs to make the call, such as choosing between competing business strategies
- Hybrid: Complex problems that combine verifiable subtasks with elements that require judgment, such as market research or preparing a business proposal
A key skill for effective AI adoption is to continually reassess that division as work unfolds: what AI can execute and what still requires a human decision.
These human-AI workflows also depend on a combination of domain expertise and broader capabilities. A data scientist who understands healthcare regulations, or a marketer who grasps AI’s creative limitations, can bridge the gap between technical possibility and real-world viability. Employees may therefore need development in technical AI skills, as well as management, communication, strategy, ethics, and collaboration.
AI introduces new requirements for governance, oversight, and accountability
AI governance needs to be more adaptive than traditional software governance. Since conventional software typically operates according to predefined logic, permissions, and expected behaviors, oversight is mostly focused on ensuring it functions as intended within those boundaries. Meanwhile, AI systems are probabilistic, producing more variable and context-sensitive outputs. That makes ongoing monitoring more important after deployment. Organizations need to watch for changes in performance and behavior over time, including drift, emerging bias, and departures from organizational expectations and human values.
Access controls help illustrate why AI needs a distinct governance approach. Conventional software operates under fixed, preauthorized permissions, while people typically have role-based access but can request additional permissions as needed. As AI takes on a more active role in workflows, enterprises may need to borrow more from the human model: give AI least-privilege access while allowing it to request additional access when a task requires it. Of course, any additional access should remain subject to appropriate approval and oversight.
The analogy between AI governance and managing people extends beyond access controls. When organizations onboard a new team member, they define their role, set boundaries around what they can do, establish how work will be reviewed, and explain the standards they’re expected to meet. The same should go for AI. For example, when a human employee presents their work to a manager, they’re expected to explain their thinking and decisions. AI should be no different. It too should be able to demonstrate how it arrived at specific outputs.
The general point is that we should apply the same rigor to governing AI that we do to managing people, including regular check-ins, context reviews, and course corrections. But that doesn’t mean every AI system should be governed in the same way. AI solutions can vary drastically in their level of autonomy, from human-operated tools to fully autonomous, always-on systems. These differences mean governance should be defined at the use-case level, rather than through a one-size-fits-all approach. A fully autonomous system will require rigorous, real-time monitoring and human-in-the-loop mechanisms for high-risk decisions, whereas a human-operated tool may only require controls like input validation and output review.
We should apply the same rigor to governing AI that we do to managing people.
Most importantly, humans must be held accountable for what they use AI for and the outcomes it produces. If an AI system exhibits bias or generates incorrect outputs, the buck stops with the humans overseeing it, just as a manager is accountable for their team’s output and performance.
Managing AI adoption across the enterprise
At rollout, enterprises are unlikely to know exactly how AI will fit into day-to-day work as they progress in AI maturity. Capabilities evolve rapidly, and teams often discover through experience which tasks AI handles well and where else it can add value. As that understanding grows, organizations may need to revise role expectations, controls, and guidance to reflect how AI is actually being used.
Here are some key considerations for managing that evolution:
Define a clear, inspiring goal
A clear, achievable AI goal tied to business impact can give teams a shared sense of direction as adoption evolves. That goal also needs visible leadership sponsorship. A senior leader can help keep the effort on the leadership agenda, resolve obstacles that require coordination across teams, and reinforce the priorities and expectations around AI adoption as it becomes more embedded in everyday work.
Communicate transparently
Employees need to understand why AI is being introduced, how it may affect their work, and what benefits and risks come with it. Leaders and managers can encourage buy-in by proactively explaining how AI can augment roles and create new opportunities for the organization, rather than presenting it purely as a cost-optimization tool. That communication should also be realistic about AI’s limitations and give employees clear ways to ask questions, raise concerns, and share what they’re seeing as use expands.
Measure frequently
Regular measurement can show whether AI adoption is actually taking hold. Usage data can show where and how often AI is being used, but a fuller picture comes from combining that data with employee feedback, manager observations, measures of AI proficiency, and evidence that expectations around AI use and oversight are being followed.
Those signals can show where the change effort needs to adapt, whether through further training, clearer guidance, changes to communication, or adjustments to how AI is being integrated into particular roles and workflows.
Final thoughts
AI represents more than a way to automate existing work or reduce costs. The goal of AI adoption should be to integrate AI into the organization’s operating model in ways that transform how the business works and creates value. That transformation depends on AI capabilities evolving alongside the organizational capabilities that support them, from data foundations and technology to workforce skills, governance, and strategy.
The picture is still developing, of course. What we’ve covered here reflects only what we’re observing in our work with customers: the conditions that help AI adoption succeed, the challenges that persist, and how enterprises are responding to them. As we gain more experience supporting organizations through their AI transformation journeys, we expect that our understanding of what effective adoption requires will continue to change.
