---
url: https://www.adoptionlab.ai/pdsa/
title: "Change management mapped to PDSA | AdoptionLab.AI"
description: "Change management tools mapped to each step of the PDSA cycle, written for teams that test, learn, and adjust. Built for hospitals, FQHCs, and CMHCs."
generated: 2026-09-23T16:08:02.097Z
---Change management, mapped to PDSA
# 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 improvement stick. PDSA already works in small, repeated experiments: test, learn, adjust, test again. Change management fits that rhythm. Each cycle is a chance to test the people side too, through sponsorship, communication, training, resistance management, and reinforcement, and to learn what it takes for the new way to become simply how work is done. This page shows where those tools fit in each step.
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.
[Plan](#plan)[Do](#do)[Study](#study)[Act](#act)
[Part of the Quality Improvement modules. See how they work →](/quality-improvement) [Using Six Sigma? Open the DMAIC map →](/dmaic)
## 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 step 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)
## Plan
Design a small test of change. Decide what you will try, who it touches, what you predict will happen, and what adoption will look like.
### Questions to ask
- Who does this test touch, and what do they need to hear and learn before it starts?
- What do we predict adoption will look like by the end of the test, in numbers?
- Who is the sponsor for this test, and what will they visibly do while it runs?
### Case for Change
The plain-language "why now" and cost of doing nothing, written for staff. Keep it short enough to repeat in one breath, and refine it as each cycle teaches you what lands.
### Sponsor Identification and Role Definition
Who removes barriers, and what they must visibly say and do during the test. Sponsors who only approve the aim statement are not sponsoring.
### Stakeholder Analysis
Who is affected by the test, who has influence, who could block, and how each group feels today. Update it every cycle, because positions shift as people see the change.
### People-Side Success Definition
What "adopted" looks like in observable, countable terms. Write it as a prediction next to your outcome measure, so Study can check both.
### 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 each test so it does not collide with survey prep or a system upgrade.
### Change Impact Assessment
What this test changes by role, unit, process, and tool, and how much. Start small: the first cycle should touch the fewest people who can still teach you something.
### Change Readiness Assessment
Baseline awareness, willingness, and capability by group before the first test. Repeat it as cycles progress to show movement.
### Baseline Adherence Measurement
How consistently the current process is actually followed before you test anything. Low adherence now usually means adoption, not design, is the real problem.
### Co-Design with Affected Staff
The people who do the work help design each test. They will spot what to try next faster than the improvement team will.
### Pilot Design with Adoption Measures
Every cycle tests two things: whether the change works and whether people will use it. Predict both before you start, then check both.
## Do
Run the experiment with the people who do the work, and watch how the change actually lands.
### Questions to ask
- Are people hearing about this from their own leader, or from the project team?
- Are we watching what actually happens, or waiting for the data?
- What surprised us, and are we treating it as information or as resistance?
### Communication Plan
Who hears what, from whom, when, and through which channel while the test runs. Keep it proportional: a one-unit, one-week test needs a huddle, not a campaign.
### Training Plan
Just enough skill-building right before the test starts. Include practice time, and note what people struggled with for the next cycle.
### Sponsor Action Plan
What leaders say and do during the test, with dates. Visible, repeated leader actions matter more than a kickoff announcement.
### Workflow Observation
What people really do during the test versus what the plan says. The gaps you see are next cycle's material.
### Manager Reinforcement Routines
Leader rounding, huddle check-ins, and coaching while the test runs. Small, frequent touches catch problems while there is still time to adjust.
### Resistance Management Plan
Expected pushback by group and the planned response, ready before day one. Treat surprises as data: resistance usually signals an unmet need, not a bad attitude.
## Study
Compare what happened with what you predicted, for the process and for the people: who used the change, who did not, and why.
### Questions to ask
- How did adoption compare with our prediction, and why the difference?
- Who used the change, who didn't, and what was different about them?
- When people didn't use it, was that skill, belief, workload, or timing?
### Adoption and Utilization Metrics
Did people use the change, how often, and how well, compared with what you predicted. Read these alongside the outcome measure, not after it.
### Proficiency Assessment
Could people do it correctly, not just did they attend. A skills check or observation beats a completion report.
### Stakeholder Sentiment Recheck
Repeat the pulse survey from Plan, asked the same way. The change in answers is the finding.
### Barrier Root Cause Analysis
Why people did not follow the change: awareness, skill, belief, workload, or tools. Each cause points to a different adjustment to try next cycle.
### Resistance Source Analysis
Which few causes explained most of the pushback. Aim the next experiment there.
### Force Field Analysis
Driving and restraining forces the test revealed, and which restraining forces are movable. Weakening one restraint is often the next test.
### Personal Value Analysis
What each group gained, lost, or feared once the change was real. Shapes the message, and the design, for the next cycle.
## Act
Adopt, adapt, or abandon. Carry what you learned into the next cycle, and make what worked standard practice.
### Questions to ask
- If we adopt, who owns the new way by name, and what routine keeps it visible?
- If we abandon, have we told the people who tried it why, so they'll try the next one?
- What did we learn about adoption this cycle that we'll carry into the next?
### Change Management Plan
The integrated people-side plan for adopting or spreading what worked: sponsorship, communication, training, coaching, and resistance. It grows with each cycle rather than arriving finished.
### Rollout Sequencing
Which units or clinics test next, and why. Spread to the ready ones first and let their results carry the case.
### Reinforcement Plan
How the new behavior is recognized, corrected, and kept visible after the test ends. Without it, drift back starts quickly.
### Sustainment Ownership Transfer
Who owns the people side after the improvement team steps back. Name a person, not a committee.
### Closing the Loop with Staff
Telling people what happened with their input and what the test showed, even when the answer is "abandon." It builds trust for the next cycle.
### People-Side Lessons Learned
What helped and hurt adoption this cycle, captured before the next one starts. Small lessons compound over many cycles.
## Bring this into your improvement program
We build self-paced change management modules that sit alongside the PDSA cycles and Lean Six Sigma belt programs 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/pdsa