---
url: https://www.adoptionlab.ai/dmaic/
title: "Change management mapped to DMAIC | AdoptionLab.AI"
description: "Change management tools mapped to each DMAIC phase, with a note on what each does. Built for quality improvement teams in hospitals, FQHCs, and CMHCs."
generated: 2026-09-23T16:08:02.068Z
---Change management, mapped to DMAIC
# Why good Quality Improvement needs Change Management
A sound process fix can still fade within months when the care team drifts back to the old way. Change management is the discipline that helps make your project stick. Through effective sponsorship, communication, training, resistance management, and reinforcement, it supports your team until the new way is simply how work is done. Each phase of DMAIC has a natural place for that work. This page shows where.
Change management is the people side of improvement: who sponsors the change, what staff need to hear and learn, where resistance will come from, and what keeps the new way in place.
[Define](#define)[Measure](#measure)[Analyze](#analyze)[Improve](#improve)[Control](#control)
[Part of the Quality Improvement modules. See how they work →](/quality-improvement) [Prefer PDSA? Open the PDSA map →](/pdsa)
## Built for healthcare teams
### Small teams
The sponsor, the process owner, and the affected staff often overlap. These tools work when the same people fill several roles.
### Lots going on
Regulatory, EHR, and staffing changes land on the same teams at the same time. Timing and change load get their own tools here.
### Trusted voices
The charge nurse or lead clinician everyone listens to moves adoption more than a memo. Several tools are built around finding and equipping those people.
Each phase below lists the change management tools that fit it best. Tap a card to see more on that topic.
Print the questions
[New to these terms? Open the glossary →](/glossary)
## Define
Set the scope and name the people who matter before the work starts.
### Questions to ask
- Who has to change how they work for this to succeed, and have we named them?
- Who has the authority to remove barriers, and what will they visibly do in the first month?
- What does "adopted" look like in numbers, not intentions?
### Case for Change
The plain-language "why now" and cost of doing nothing, written for staff. If staff cannot repeat it in one breath, it is not finished.
### Sponsor Identification and Role Definition
Who removes barriers, and what they must visibly say and do. Sponsors who only sign the charter are not sponsoring.
### Stakeholder Analysis
Who is affected, who has influence, who could block, and how each group feels today. Revisit it after each phase, because positions shift.
### People-Side Success Definition
What "adopted" looks like in observable, countable terms. This becomes the target Control measures against.
### Voice of the Frontline
What staff know, need, and fear about the current process. Often surfaces workarounds the process map missed.
### Change Load Assessment
What else is landing on the same units in the same window. Helps you time the rollout so it does not collide with survey prep or a system upgrade.
## Measure
Baseline how people work today, not just how the process performs.
### Questions to ask
- How consistently is the current process actually followed, by shift and by role?
- Do we know how ready, willing, and able each affected group is, or are we guessing?
- Have we watched the work happen, or only read the process map?
### Change Readiness Assessment
Baseline awareness, willingness, and capability by group. Repeat it later to show movement.
### Current-State Role Impact Mapping
Who does what today, so you can see what shifts later. Feeds the impact assessment in Analyze.
### Baseline Adherence Measurement
How consistently the current process is actually followed. Low adherence now usually means adoption, not design, is the real problem.
### Stakeholder Sentiment Baseline
A short pulse survey you can repeat later. Three to five questions is enough if you ask them the same way each time.
### Workflow Observation
What people really do versus the documented process. Watch a shift or a clinic session rather than asking in a meeting.
## Analyze
Find out why current behavior persists and what the change will ask of people.
### Questions to ask
- When people don't follow the current process, is it awareness, skill, belief, workload, or tools?
- What does each group stand to gain, lose, or fear from this change?
- Who will people listen to about this, regardless of the org chart?
### Change Impact Assessment
What changes by role, unit, process, and tool, and how much. The groups facing the biggest shift get the most support.
### Barrier Root Cause Analysis
Why people do not follow the process: awareness, skill, belief, workload, or tools. Each cause calls for a different fix.
### Force Field Analysis
Driving and restraining forces, and which restraining forces are movable. Weakening a restraint often beats pushing harder.
### Resistance Source Analysis
Which few causes explain most of the pushback. Focus your response where it matters most.
### Personal Value Analysis
What each stakeholder group gains, loses, or fears. Shapes the message each group needs to hear.
## Improve
Design the fix and the adoption plan together.
### Questions to ask
- Did the people who do the work help design the fix, or will they meet it at go-live?
- Who hears about this, from whom, and when, and is it their own leader?
- Does the pilot measure whether people use the change, not only whether it works?
### Change Management Plan
The integrated people-side plan covering sponsorship, communication, training, coaching, and resistance. It sits alongside the implementation plan, not after it.
### Communication Plan
Who hears what, from whom, when, and through which channel. Frontline staff should hear it from their own leader, not only from the project team.
### Sponsor Action Plan
What leaders say and do, with dates. Visible, repeated leader actions matter more than a launch announcement.
### Training Plan
Building skills before go-live. Include practice time, not just information.
### Resistance Management Plan
Expected pushback by group and the planned response. Resistance usually signals an unmet need, not a bad attitude.
### Co-Design with Affected Staff
The people who do the work help design the fix. Ownership built here makes Control much easier.
### Pilot Design with Adoption Measures
Each cycle tests whether the process works and whether people will use it. A pilot that only works with volunteers is not proven.
## Control
Make the new way of working just how we do things by the time the project team steps back.
### Questions to ask
- Are we tracking adoption next to the outcome, so we see drift before the number moves?
- Who owns this by name after the project closes?
- Will the next new hire learn the new way, or the old one from whoever trains them?
### Adoption and Utilization Metrics
Are people using the new process, how often, and how well. Track these alongside the outcome KPIs.
### Proficiency Assessment
Can people do it correctly, not just did they attend. A skills check or observation beats a completion report.
### Reinforcement Plan
How the new behavior is recognized, corrected, and kept visible over time. Without it, drift back starts quickly.
### Manager Reinforcement Routines
Leader rounding, huddle check-ins, and audits framed as coaching. Small, frequent touches beat a quarterly review.
### Sustainment Ownership Transfer
Who owns the people side after the project team leaves. Name a person, not a committee.
### Closing the Loop with Staff
Telling people what happened with their input and the results. It builds trust for the next change.
## Bring this into your improvement program
We build self-paced change management modules that sit alongside the Lean Six Sigma belt programs and PDSA cycles your teams already run. If your organization runs one, let's talk about layering these in.
[Let's chat](mailto:mhumer@adoptionlab.ai?subject=Let%27s%20chat%20(AdoptionLab.AI))
adoptionlab.ai/dmaic