Projects often report that the system is built, the process is signed off, or training is complete. Those are useful project milestones, but they do not prove that people have adopted the change. A change takes hold when impacted people understand it, accept enough of it to try, build skill, use the new way of working, and perform with acceptable proficiency. Prosci makes a similar distinction by measuring individual progress through adoption states and then looking at adoption speed, utilization and proficiency [Prosci, 2024]. (prosci.com)

For this article, ABSUP means Awareness, Buy-in, Skill, Usage and Proficiency. Measuring ABSUP milestones beside project milestones helps the change manager answer a practical question: “Are people moving fast enough for the project benefits to be realized?” PMI’s benefits realization guidance connects strategy, deliverables and success measurement, so adoption evidence should be treated as part of value delivery, not as an optional reporting add-on [PMI, 2018]. (pmi.org)

This action is an adoption measurement and reporting intervention. It creates a side-by-side view of project progress and people progress. A project milestone describes what the project is supposed to achieve by a specific date; PMI’s milestone-planning guidance emphasizes that milestones should describe a desired state, not just an activity [PMI Andersen, 2006]. (pmi.org)

Use this action whenever business value depends on people changing behavior: a new system, operating model, policy, workflow, role design, customer process or compliance requirement. Use it early in planning, before go-live readiness reviews, during rollout, and after implementation when reinforcement and benefits tracking begin. It is especially useful when leaders are tempted to declare success at launch.

Start with the project plan, benefits case, impact assessment, stakeholder map, training plan, communications plan and available operational data. Confirm the impacted groups, the few behaviors that matter most, and the business outcomes those behaviors enable. Prosci recommends defining success early, involving sponsors, impacted leaders, subject matter experts and project managers, and introducing people-side metrics when technical metrics are being defined [Prosci, 2024]. (prosci.com)

The core stakeholders are the sponsor, project manager, change manager, business owner, people managers, L&D lead, data/reporting owner, and representatives from impacted teams. Prepare a one-page ABSUP-to-project milestone map, a simple RAG status definition, and a decision log. Timing should match project governance: weekly for active rollout, monthly for steady adoption, and at every go/no-go decision.

A sales organization is implementing a new CRM process. The project milestones are configuration complete, pilot complete, go-live, and hypercare exit. The ABSUP map shows that before pilot, sales managers must be aware of the reason for the change and able to explain team impacts. Before go-live, 90% of users must complete role-based practice and demonstrate the top three CRM tasks. Thirty days after go-live, usage must show that opportunities are updated weekly. At hypercare exit, proficiency is measured through data quality, reduced duplicate records and manager observation.

The project may be green at go-live because the tool is deployed, while ABSUP is amber because usage is uneven in two regions. The decision is not “delay everything” or “push through blindly.” The decision is targeted: extra manager coaching, local office hours, and a two-week follow-up before declaring adoption stable.

The change manager designs the ABSUP framework, facilitates reviews, interprets adoption gaps and recommends interventions. The project manager owns project milestones and integrates adoption gates into governance. The sponsor makes trade-off decisions and reinforces why adoption matters. People managers coach employees, gather feedback and observe behavior; Gallup emphasizes that managers play a central role during change and should use feedback loops to escalate employee issues [Gallup, 2020]. (gallup.com) The business owner owns benefits and post-project sustainment. L&D supports skill and transfer measures. Data owners provide system, process and performance evidence.

The first mistake is treating training attendance as adoption. Attendance may support Skill, but it does not prove Usage or Proficiency. The second is averaging across all groups, which hides resistant or under-supported pockets. The third is measuring too late, after go-live decisions are already made. The fourth is building a dashboard with too many indicators; McKinsey cautions that change metrics can become unwieldy and recommends focusing on the measures that matter [McKinsey, 2020]. (mckinsey.com) The fifth is using measurement punitively. Adoption data should identify barriers and support needs, not shame teams.

The action is working when adoption gaps are visible before they become benefit gaps. Useful indicators include faster movement from Awareness to Buy-in, fewer unresolved manager concerns, improved skill-demonstration results, rising active usage, reduced workarounds, lower support tickets, better process quality and clearer ownership after project close. Prosci’s three individual outcome measures—speed of adoption, ultimate utilization and proficiency—are a practical backbone for this section [Prosci, 2024]. (prosci.com)