Introduction: why this action matters for adoption
A change is not “adopted” because a system went live, a policy was announced, or training attendance reached 95%. Adoption happens when impacted people understand the change, can work in the new way, actually use it, and sustain the behavior. Prosci recommends defining success beyond technical implementation and measuring adoption and use by impacted individuals and groups [Prosci, 2024]. (prosci.com)
Measuring the change status of impacted groups is therefore an adoption measurement and reporting intervention. Its value is practical: it helps the change manager and leaders see where the change is taking hold, where friction remains, and where support, reinforcement, or corrective action is needed. PMI similarly emphasizes measuring change factors before, during, and after deployment so leaders can identify barriers to benefits realization [PMI, 2015]. (pmi.org)
What this action is and when to use it
This action creates a simple evidence routine for each impacted group. The routine defines what adoption should look like, selects a small number of indicators, gathers feedback and performance data, and reports status at a regular cadence. It is especially useful during readiness assessment, pilot preparation, go-live, hypercare, and sustainment.
Use it when a group must change behavior, process, system use, decision rights, customer interactions, compliance steps, or performance routines. It is less useful when measures are collected only to “prove success” after the fact. The purpose is not surveillance or blame; it is to make adoption visible early enough to help people succeed.
Preparation: inputs, stakeholders, materials, timing, and decisions needed
Start with the business outcome and the specific “from–to” behavior for each impacted group. Prosci’s adoption measures of speed, utilization, and proficiency are a useful starting point: how quickly people adopt, how many use the change, and how well they apply it [Prosci, 2024]. (prosci.com)
The change manager needs the impacted group map, process impacts, target behaviors, training plan, go-live dates, system or process data sources, support channels, and manager feedback routes. Stakeholders include the sponsor, project or product owner, people managers, frontline supervisors, HR/L&D, data owners, support teams, and employee representatives or champions.
Prepare a one-page adoption scorecard, a group heatmap, short pulse questions, and a decision log. For readiness questions, use group-referenced wording such as “Our team is ready to…” rather than only “I am ready to…,” because group-level readiness requires collective commitment and efficacy [Shea et al., 2014]. (pubmed.ncbi.nlm.nih.gov)
Step-by-step facilitation guide
Define “adopted” in observable terms. In a working session with the sponsor, product owner, and managers, ask: “What must this group do differently for the change to create value?” Reduce the answer to one or two observable behaviors.
Segment impacted groups. Avoid one enterprise-wide average. Separate groups by role, location, workflow, manager, system access, customer exposure, and degree of disruption. Readiness research shows measures often need tailoring to the implementation scenario [Miake-Lye et al., 2020]. (bmchealthservres.biomedcentral.com)
Choose a balanced set of indicators. Combine leading indicators, such as awareness, confidence, training completion, and manager readiness, with adoption indicators, such as utilization, quality, cycle time, error rate, support tickets, and observed behavior. Training evaluation practice also distinguishes reaction and learning from on-the-job behavior and business results [OPM, 2011]. (opm.gov)
Set thresholds before reporting starts. Agree what green, amber, and red mean. For example, green may mean at least 85% of users are using the new workflow and error rates are within tolerance. Keep the thresholds visible and review them only when the change scope shifts.
Collect employee voice, not just system data. Use short pulses, listening sessions, supervisor huddles, and representative forums. CIPD recommends multiple employee voice channels and transparent follow-up so people can see how feedback influences change [CIPD Employee Voice]. (cipd.org)
Run a recurring adoption review. Facilitate a 30-minute review weekly during go-live and hypercare, then biweekly or monthly in sustainment. Discuss what the data shows, what people are experiencing, which barriers are controllable, and what action will be taken before the next review.
Report status as a decision tool. Show group-level status, trend, top barriers, owner, next action, and date due. Do not report red status as failure. Report it as a prompt for targeted coaching, reinforcement, process fixes, sponsor action, or policy clarification.
Example: CRM adoption in a sales change
A sales organization implements a new CRM process. The target behavior is: “All sales representatives create and update opportunities in the CRM within 48 hours, using the new qualification fields.” The change manager segments impacted groups by region and role.
The scorecard uses five indicators: CRM login and opportunity update rates, field completion accuracy, manager coaching completion, support tickets, and a three-question pulse on confidence and barriers. In week two, the Western region is amber: utilization is high, but field accuracy is low and support tickets show confusion about qualification criteria. The action is not another generic email. The regional manager runs a 20-minute coaching huddle, the product owner simplifies field guidance, and the change manager checks accuracy again after one week.
Roles and responsibilities
Role | Responsibility |
Sponsor | Owns the business outcome, removes cross-functional barriers, and reinforces why adoption matters. |
Change manager | Designs the measurement approach, facilitates reviews, interprets signals, and recommends interventions. |
People managers/frontline supervisors | Observe behavior, coach teams, validate barriers, and reinforce new routines. Managers are critical because they strongly influence the local team environment [Gallup, 2015]. (news.gallup.com) |
Project/product owner | Provides system, process, defect, and release data; fixes design issues that block adoption. |
HR/L&D/support teams | Provide training, capability, help-desk, and knowledge-base evidence. |
Employees/champions | Provide lived-experience feedback and test whether support is practical. |
Common mistakes to avoid
The first mistake is measuring activity instead of adoption: attendance, communication opens, or town-hall participation may be useful, but they do not prove behavior change. The second is reporting only averages, which can hide a struggling site or role. The third is collecting feedback without closing the loop, which weakens trust and reduces future participation [CIPD Employee Voice]. (cipd.org)
Another mistake is using measures punitively. If teams believe red status creates blame, they will manage the metric rather than reveal the barrier. Finally, avoid too many measures. Prosci recommends a few simple, trackable change success metrics and a regular cadence for monitoring and adaptive action [Prosci, 2024]. (prosci.com)
Measures of success or adoption indicators
Good indicators answer four questions. Are people ready? Are they using the change? Are they using it well? Is the expected outcome emerging? For many initiatives, combine readiness pulse results, training confidence, behavior observations, utilization data, proficiency or quality data, support demand, and business KPIs.
The action itself is working when adoption reviews happen on schedule, managers use the data in team huddles, barriers are resolved faster, red or amber groups receive targeted help, and status trends improve over time. PMI recommends post-deployment measures that look for shifts in desired behavior and connect back to objectives such as quality, cycle time, cost, and customer satisfaction [PMI, 2015]. (pmi.org)
Checklist for the change manager
The target behavior is defined for each impacted group.
Measures include readiness, use, proficiency, feedback, and outcome signals.
Green/amber/red thresholds are agreed before reporting.
Data sources and owners are confirmed.
Managers know how to interpret and act on the status.
Employee feedback channels are open and followed up.
Each report includes decisions, actions, owners, and due dates.
Measures are reduced or retired once adoption is sustained.
Optional reusable worksheet
Field | Prompt |
Impacted group | Which role, team, site, or stakeholder group is being measured? |
Required behavior | What must they do differently, visibly, and repeatedly? |
Evidence of readiness | What shows they understand, are willing, and feel able? |
Evidence of use | What shows they are using the new process, system, or behavior? |
Evidence of proficiency | What shows quality, accuracy, confidence, or reduced rework? |
Feedback source | How will the group tell us what is helping or blocking adoption? |
Status threshold | What makes this group green, amber, or red? |
Decision trigger | What action will we take if the group is amber or red? |
Owner and date | Who acts, by when, and how will we know it worked? |
References
Prosci. “Metrics for Measuring Change Management.” Published March 26, 2024; updated September 2, 2025. https://www.prosci.com/blog/metrics-for-measuring-change-management
Project Management Institute. “Measure twice, change once: practical strategies for change management.” October 10, 2015. https://www.pmi.org/learning/library/practical-strategies-for-change-management-9887
CIPD. “Change management: A guide for people professionals.” December 11, 2024. https://www.cipd.org/en/knowledge/guides/change-management/
CIPD. “Employee voice.” Date not stated. https://www.cipd.org/en/views-and-insights/cipd-viewpoint/employee-voice/
Shea, C. M., Jacobs, S. R., Esserman, D. A., Bruce, K., and Weiner, B. J. “Organizational readiness for implementing change: a psychometric assessment of a new measure.” Implementation Science, January 10, 2014. https://pubmed.ncbi.nlm.nih.gov/24410955/
Miake-Lye, I. M., Delevan, D. M., Ganz, D. A., Mittman, B. S., and Finley, E. P. “Unpacking organizational readiness for change: an updated systematic review and content analysis of assessments.” BMC Health Services Research, February 11, 2020. https://bmchealthservres.biomedcentral.com/articles/10.1186/s12913-020-4926-z
U.S. Office of Personnel Management. “Training Evaluation Field Guide.” January 2011. https://www.opm.gov/hrd/lead/pubs/FieldGuidetoTrainingEvaluation.pdf
Gallup. “Managers Account for 70% of Variance in Employee Engagement.” April 21, 2015. https://news.gallup.com/businessjournal/182792/managers-account-variance-employee-engagement.aspx