Skip to content

Adoption and Change Realization Measures

This document defines candidate performance measures for assessing whether adoption and change conditions are contributing to Value Realization.

These measures should support Change Realization Management, Value Statements, Value Realization Statements, and other evidence-bearing artifacts.

Measurement Principle

Adoption measures are not automatically value measures.

Adoption and change realization measures should be used to establish whether realization conditions are present, persistent, and connected to value. They should not be used as substitutes for verified realized value unless the applicable Valuation Approach expressly permits that treatment.

Measure Classes

Activity Measures

Activity measures show that work occurred. They do not show that value was realized.

Examples:

  • communication delivered;
  • training session completed;
  • workshop conducted;
  • support session provided;
  • issue log reviewed.

Readiness Measures

Readiness measures show whether required conditions are in place before deployment, scaling, or realization review.

Examples:

  • readiness assessment completion rate;
  • role readiness coverage;
  • operational readiness gap count;
  • unresolved readiness defects;
  • decision-right clarity score.

Adoption Measures

Adoption measures show whether Players, Practices, Platforms, Products, Partners, or Projects are operating in the changed state.

Examples:

  • value-linked usage rate;
  • changed-practice adherence rate;
  • changed-decision cadence adherence;
  • changed-platform-use evidence;
  • expected-behavior observation rate.

Competency Measures

Competency measures show whether Players have the observable proficiency required to perform changed work.

Examples:

  • competency assessment completion;
  • competency maturity progression;
  • proficiency demonstration rate;
  • coaching issue closure rate;
  • independent performance readiness.

Resistance and Defect Measures

Resistance and defect measures show whether barriers, objections, frictions, or design defects are being surfaced and addressed.

Examples:

  • resistance issue count;
  • unresolved resistance issue aging;
  • barrier removal rate;
  • defect recurrence rate;
  • escalation closure rate.

Resistance should not be treated as irrational by default. It may indicate weaknesses in the value case, incentives, process design, evidence model, capability model, control model, or operating assumptions.

Reinforcement Measures

Reinforcement measures show whether changed behavior or operating conditions persist after deployment.

Examples:

  • reinforcement cadence adherence;
  • post-deployment behavior persistence;
  • reversion incident count;
  • sustained practice adherence;
  • support dependency reduction.

Value Evidence Measures

Value evidence measures show whether the changed state is contributing to expected value.

Examples:

  • evidence completeness for Value Statement support;
  • baseline-to-current variance;
  • validated outcome movement;
  • value-producing behavior persistence;
  • value erosion avoided;
  • realized value evidence quality.

Evidence Hierarchy

The preferred evidence hierarchy is:

  1. activity evidence;
  2. readiness evidence;
  3. adoption evidence;
  4. competency or capability evidence;
  5. performance evidence;
  6. value evidence;
  7. validation evidence;
  8. realization evidence.

Lower-order evidence may support higher-order evidence, but should not be represented as equivalent.

Governance Questions

Each measure should answer:

  • What realization condition does this measure support?
  • Which Effect does the measure relate to?
  • Which Value Realization Domain is affected?
  • What data source supports the measure?
  • What is the baseline?
  • What threshold matters?
  • What evidence quality applies?
  • Who validates the measure?
  • How does the measure connect to the Value Statement or Value Realization Statement?

Guidance

  • Do not treat attendance as competency.
  • Do not treat training completion as ability.
  • Do not treat system login or access as adoption unless the usage is value-linked.
  • Do not treat user satisfaction as realized value without evidence of value contribution.
  • Do not treat stakeholder sentiment as validation unless the Valuation Approach allows sentiment evidence.
  • Do not use adoption measures to inflate Value Realization Share.
  • Do not use measures without an identified evidence source and validation responsibility.