Many changes appear complete at go-live but fail to deliver value because people do not use the new process, system, role, policy, or behavior in the intended way. Establishing adoption and usage objectives turns “we launched it” into “the impacted group is using it correctly, consistently, and sustainably.” This is a change-management intervention in governance, planning, and operating model design: it creates decision rights, shared definitions, measurement cadence, and ownership for adoption follow-up.

A good adoption objective connects the business benefit to observable behavior. Prosci recommends defining success early and extending it beyond technical implementation to include adoption and use by impacted groups [Prosci, 2024]. PMI similarly emphasizes measuring change before, during, and after implementation so leaders understand the starting point, identify barriers, and support benefit realization [PMI, 2015].

This action establishes a documented agreement on what adoption means, what usage counts, who owns each measure, how progress will be reviewed, and what decisions will be made when adoption is off track. It should distinguish three related ideas: adoption, meaning the target population has shifted to the new way of working; usage, meaning the new tool, process, or behavior is being used in the defined way; and proficiency, meaning the use is effective, accurate, and aligned with the intended outcome. Prosci’s adoption measurement language of speed of adoption, ultimate utilization, and proficiency is useful here [Prosci, 2024].

Use this action when benefits depend on people changing behavior, when leaders disagree about what “done” means, when adoption data is likely to be contested, when managers need a consistent coaching message, or when there is a risk that teams will use workarounds. It is especially valuable before training design, readiness assessments, go-live planning, and post-launch reinforcement.

The change manager should gather the business case, change definition, future-state process or operating model, impact assessment, stakeholder analysis, learning needs, available baseline data, and any compliance or privacy constraints. ACMP identifies goals, objectives, success criteria, roles, measurement, benefits, and sustainability as core change management concerns [ACMP, 2025]. GOV.UK’s service measurement guidance reinforces the need to define purpose, benefits, data sources, baselines, targets, and reporting methods before relying on metrics [GOV.UK, 2017].

Invite the sponsor, project or product owner, business process owner, impacted people managers, adoption or change leads, HR or learning partners, analytics or reporting owners, and representative employees. Schedule the working session early enough to influence the change plan, not after launch. The key decisions are: what behavior counts as adoption, what usage evidence is valid, what threshold indicates success, what time window applies, who owns the data, and what happens when results fall below target.

Begin by restating the business outcome in plain language. Ask, “What must people do differently for this benefit to be realized?” This keeps the discussion anchored in benefits rather than project deliverables, consistent with PMI’s emphasis on benefit-focused change planning [PMI, 2015].

Next, identify the impacted groups separately. A manager, front-line employee, support team, and sponsor may each need different adoption definitions. McKinsey’s transformation research emphasizes that people across the organization need specific roles and must know how to carry them out [McKinsey, 2021].

Then convert outcomes into behavior statements. Avoid vague language such as “use the tool.” Instead, define the required action, population, frequency, quality standard, and time frame. CDC’s SMART guidance is useful: objectives should be specific, measurable, achievable, relevant, and time-bound [CDC, 2024].

After that, select a small number of indicators. Include one primary usage indicator, one proficiency or quality indicator, and one leading indicator such as training completion, manager check-ins, or help-desk patterns. GOV.UK recommends choosing a few metrics that answer whether the service is working, identifying data sources, and providing context through baselines and trends [GOV.UK, 2017].

Finally, agree the governance rhythm. Define who reviews adoption data, how often, what thresholds trigger action, and who can change the adoption plan. Prosci recommends a regular cadence for tracking KPIs, analyzing results, and taking adaptive action [Prosci, 2024].

A company is replacing spreadsheet-based expense approvals with a new workflow system. The project team originally defined success as “system live for all employees.” The change manager facilitates a session and reframes success as adoption by employees, managers, and finance.

The agreed employee usage definition is: “Expense claims are submitted through the new workflow, with required receipts and cost centers completed, within five business days of purchase.” The manager adoption definition is: “Managers approve or reject claims in the workflow, not by email, within three business days.” The proficiency indicator is the percentage of claims returned by finance because of missing or incorrect information. The adoption objective is: “Within six weeks of launch, 85% of eligible claims are submitted and approved through the workflow, with fewer than 8% returned for rework.” This objective is specific, time-bound, and tied to the benefit of faster reimbursement and better financial control [CDC, 2024; GOV.UK, 2017].

The first mistake is measuring only implementation activity, such as emails sent, training attended, or licenses provisioned. Those are useful leading indicators, but they do not prove adoption. The second mistake is using vague adoption language that managers cannot coach against. The third is choosing too many metrics, which dilutes attention and creates reporting burden; GOV.UK recommends a small set of meaningful performance metrics supported by valid data sources [GOV.UK, 2017]. The fourth is using adoption data to blame teams instead of diagnosing barriers. High resistance may signal unclear benefits, poor workflow fit, insufficient capability, or competing priorities. Gallup recommends feedback loops and escalation of employee feedback during change [Gallup, 2020].

Useful indicators combine evidence of use, quality, confidence, and business effect. Usage indicators may include transaction completion, system activity, channel shift, process compliance, or frequency of required behavior. Proficiency indicators may include error rates, rework, cycle time, customer satisfaction, audit findings, or manager-observed capability. Leading indicators may include role-based training completion, manager briefing completion, knowledge checks, support requests, and sentiment themes. Business indicators should link to the expected benefit, such as reduced cycle time, lower cost, improved compliance, or better customer experience [PMI, 2015; GOV.UK, 2017].

If adoption is low, segment results by group, location, role, tenure, or workflow type before deciding on corrective action. GOV.UK warns that aggregate averages can hide meaningful differences between user groups [GOV.UK, 2017].

ACMP. Standard for Change Management©. Association of Change Management Professionals. 2nd edition published August 26, 2025.
​https://www.acmpglobal.org/general/custom.asp?page=the_standard

Prosci. “Metrics for Measuring Change Management.” Published March 26, 2024; updated September 2, 2025.
​https://www.prosci.com/blog/metrics-for-measuring-change-management

PMI. Jack P. Ferraro. “Measure twice, change once: practical strategies for change management.” Project Management Institute. October 10, 2015.
​https://www.pmi.org/learning/library/practical-strategies-for-change-management-9887

GOV.UK Service Manual. “How to set performance metrics for your service.” Government Digital Service. Published December 5, 2017.
​https://www.gov.uk/service-manual/measuring-success/how-to-set-performance-metrics-for-your-service

CDC. “Developing Objectives and Evaluation Questions.” Centers for Disease Control and Prevention. November 8, 2024.
​https://www.cdc.gov/tb-programs/php/evaluation/objectives.html

McKinsey & Company. “Losing from day one: Why even successful transformations fall short.” December 7, 2021.
​https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/successful-transformations

Gallup. Sherzod Odilov and Chris Musser. “Proven Change Management Principles: How to Effectively Initiate It.” July 15, 2020.
​https://www.gallup.com/workplace/315602/proven-change-management-principles-effectively-initiate.aspx