Change Copilot — People, Intuition, Impact
Case Atlas

Transformation case patterns

Every case carries its evidence tier. Tier A cases explicitly document Prosci/ADKAR usage. Tier B are strongly evidenced. Tier C are general change-management cases where ADKAR involvement is not confirmed — they are still instructive, but the model attribution is not claimed.

TIER ATier A — Explicitly documented Prosci/ADKAR

Organizations with published named case studies through Prosci, ADKAR referenced by name, or citation in Prosci Best Practices research with organizational identification.

TIER BTier B — Strongly evidenced

Documented CM practices (sponsor coalitions, ADKAR-structured diagnostics, change impact assessments, readiness gates) align precisely with Prosci methodology, but ADKAR is not explicitly named.

TIER CTier C — General change management (ADKAR not confirmed)

Credible change management evidence but no direct Prosci attribution. Included for cross-case pattern analysis and archetype building.

Cross-case patterns

25 recurring change problems

  1. 01 Sponsor becomes passive after program launch
  2. 02 Employees don’t understand the "why" of the change
  3. 03 "What’s in it for me?" is never explicitly answered
  4. 04 Middle managers are not equipped to lead change
  5. 05 Training occurs too late in the project cycle
  6. 06 Training is generic, not role-based
  7. 07 Technology goes live but people are not ready
  8. 08 Change fatigue from too many simultaneous programs
  9. 09 Change network becomes symbolic — meetings but no action
  10. 10 Communications become one-way broadcast channels
  11. 11 No structured feedback mechanism exists
  12. 12 Adoption is not measured after go-live
  13. 13 Reinforcement disappears 90 days post go-live
  14. 14 Business-as-usual pressure overwhelms transformation effort
  15. 15 Change impact is systematically underestimated in scoping
  16. 16 Local business units resist global standardization
  17. 17 Culture clash after M&A is underplanned
  18. 18 Project management and change management operate in silos
  19. 19 Leadership assumes "training completed" = adoption achieved
  20. 20 Technology implementation is mistaken for transformation
  21. 21 Benefits realization is never formally tracked
  22. 22 Sponsor coalition is incomplete — missing key business leaders
  23. 23 Poor stakeholder alignment before program launch
  24. 24 Resistance from power users who lose status or workarounds
  25. 25 Change readiness is assessed too late to act on findings
Industry patterns

How context changes the change

universal

Sponsor passivity, middle manager unpreparedness, the training–adoption gap, reinforcement disappearing at go-live, and change fatigue in multi-wave programmes appear in virtually every transformation.

byTransformation

SAP: Ability is the primary post-go-live gap,M&A: Desire is the primary integration gap,Culture: Ability to demonstrate new behaviours is the primary gap,AI adoption: Desire (role-security fear) is the primary barrier

byIndustry

Healthcare: regulatory compliance resistance overlays Desire gaps,Manufacturing: shift-worker training delivery is structurally difficult,Financial services: risk-averse culture amplifies Desire deficits,Government: political sponsorship instability undermines reinforcement

byMaturity

Organizations with mature Change Management Offices show dramatically higher Reinforcement scores. First-time change programmes disproportionately fail at Desire and Reinforcement due to insufficient diagnostic infrastructure.