Organizational Change Management for Technology Adoption
Organizational change management helps people move from current ways of working to new ones introduced by technology. It coordinates sponsorship, impact analysis, communication, learning, support, and measurement so deployment becomes sustained adoption.
itIT service management and support | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don't Panic — Organizational Change Management for Technology Adoption
Organizational change management, or OCM, is the part of a technology initiative that deals with people changing real work. Software can be deployed while everyone quietly carries on with the old process. This is less a rebellion than a useful clue: an available system and an adopted way of working are different species.
The first idea is that one initiative has two connected workstreams. Technical delivery builds, configures, tests, and releases the service. The adoption workstream maps affected groups, changed tasks, readiness, support, and evidence. They share a plan because training people on a workflow that is still wobbling is an expensive way to collect confused faces.
The second idea is the adoption chain. Reach, readiness, participation, usage, proficiency, sustainment, and outcome are separate questions. A message delivered is not understanding. A login is not useful work. A completed course is not demonstrated ability. Treat each measure as a clue about the next stage, not as a medal for the previous one.
The third idea is diagnosis. A concern may expose missing access, an inaccessible task, a conflicting incentive, limited capacity, lost expertise, or an unproven benefit. Calling all of those resistance saves time only if the aim is to avoid finding out what is wrong. Name the mechanism first. Then decide whether the repair is communication, practice, negotiation, support, or a change to the product or process.
A pilot is where these ideas meet actual conditions. It tests the workflow, access, manager conversations, learning, support, measures, and contingency path with a bounded, representative group. Friendly experts are useful, but they are also unusually good at making a difficult system appear well behaved. Include people whose constraints could change the release decision.
The surprise is that OCM cannot persuade a harmful, unusable, or unnecessary system into being valuable. It cannot replace product discovery, technical testing, accessibility work, security, consultation, or durable service ownership. Its job is narrower and more useful: keep evidence about changed work close enough to the delivery plan that someone can act on it.
Read the Intro for the full system and its vocabulary. Use the Slides when the two workstreams and adoption chain need a compact map. Keep the Cheatsheet nearby while planning impacts, pilots, and measures. The Practice Reference turns those ideas into working prompts. The Quiz checks the distinctions that launch schedules often blur.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://www.acmpglobal.org/page/change_management/Change-Management.htm
Supports
- Method-neutral definition of change management as transition from current to future state for expected benefits
- Relationship of change management to strategic planning, project management, organizational development, and process improvement
- Adoption of change and operation in the future state
- https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-ocm/introduction.html
Supports
- Technology adoption requires attention to organization alignment, leadership, capability, and culture
- Six-point change acceleration flow from mobilization and leader alignment through engagement, capacity, and sustainment
- Sponsor, communication, training, culture, and organizational-impact activities
- https://docs.aws.amazon.com/whitepapers/latest/aws-caf-people-perspective/change-acceleration.html
Supports
- Affected-group and change-impact mapping across process, people, organization, technology, data, and measures
- Readiness surveys, stakeholder capacity, role-based communication, and learning plans
- Adoption roadmaps aligned to technical milestones
- https://docs.aws.amazon.com/prescriptive-guidance/latest/oca-framework-engage-organization/change.html
Supports
- Change strategy implementation integrated with technical and program workstreams
- Impact review, risk mitigation, stakeholder feedback, and adaptation at major milestones
- Ongoing ownership of people-related, cultural, organizational, and political risks
- https://docs.aws.amazon.com/prescriptive-guidance/latest/oca-framework-mobilize-team/change-adoption-metrics.html
Supports
- Qualitative and quantitative adoption measures
- Leading and lagging indicators
- Measures for leadership, understanding, preparedness, learning, support, behavior, and sustainment
- https://www.prosci.com/methodology-overview
Supports
- Technical and people sides of organizational change
- Individual adoption as part of organizational results
- Prosci methodology components and 2021 methodology refresh
- https://www.prosci.com/methodology/adkar
Supports
- ADKAR outcomes of awareness, desire, knowledge, ability, and reinforcement
- Individual diagnostic perspective within organizational change
- Assessing barrier points and adapting support
- https://www.prosci.com/blog/adkar-core-to-the-people-side-of-change
Supports
- ADKAR development in 1996 and first white-paper publication in 1999
- Publication of the ADKAR book in 2006
- https://www.kotterinc.com/methodology/8-steps/
Supports
- Organization-level change elements including urgency, coalition, vision, participation, barrier removal, wins, acceleration, and institutionalization
- Evolution from the linear eight steps to iterative accelerators
- https://www.kotterinc.com/bookshelf/leading-change/
Supports
- Publication of Leading Change in 1996
- Introduction of an eight-stage process for leading organizational change
- https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2
Supports
- May–June 1995 publication of Leading Change — Why Transformation Efforts Fail
- Early articulation of recurring organizational transformation failures
- https://www.gov.uk/service-manual/measuring-success/measuring-digital-take-up
Supports
- Baselines, eligible populations, channel use, and digital take-up measurement
- Research into digital skill, literacy, willingness, and assisted support needs
- https://www.gov.uk/service-manual/user-research/how-user-research-improves-service-design
Supports
- Continuous, inclusive research with likely and disabled users
- Testing ideas and live services to expose barriers and improve design
- Involving the delivery team in observing real user behavior
- https://www.gov.uk/service-manual/helping-people-to-use-your-service/making-your-service-accessible-an-introduction
Supports
- Accessibility considered from discovery through live operation
- Inclusion of disabled people and assistive-technology users in research
- Accessibility as a whole-team responsibility
- https://www.gov.uk/service-manual/user-research/using-moderated-usability-testing
Supports
- Observing people perform realistic tasks to identify usability barriers
- Testing with assistive technologies and appropriate scenarios
- https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/employment/monitoring-workers/data-protection-and-monitoring-workers/
Supports
- Worker monitoring must be lawful, fair, transparent, and proportionate
- Excessive monitoring can affect privacy and wellbeing
- Use of the least intrusive means and governance of third-party monitoring tools
- https://learn.microsoft.com/en-us/microsoft-365-apps/best-practices/microsoft-365-change-guide
Supports
- Continuous technology change requires communication, planning, stakeholder preparation, feedback, and support
- Before, during, and after phases for user-impacting technology change
- Early-adopter validation and feedback loops
- https://dora.dev/capabilities/transformational-leadership/
Supports
- Leadership influences technology outcomes by enabling adoption of technical and product practices
- Vision, communication, support, intellectual stimulation, and recognition in transformational leadership
- https://doi.org/10.1177/001872674700100103
Supports
- June 1947 publication of Frontiers in Group Dynamics on social change
- https://aisel.aisnet.org/misq/vol13/iss3/6/
Supports
- 1989 publication of Perceived Usefulness, Perceived Ease of Use, and User Acceptance of Information Technology
- Measurement of usefulness and ease of use in technology acceptance
- https://doi.org/10.2307/30036540
Supports
- 2003 publication of User Acceptance of Information Technology — Toward a Unified View
- Integration and comparison of eight prior user-acceptance models
- https://www.acmpglobal.org/page/about_acmp
Supports
- ACMP incorporation and launch in 2011
- Development of a professional association and global chapters
- https://www.acmpglobal.org/page/the_standard
Supports
- September 2014 release of the ACMP Standard for Change Management
- Method-neutral, generally accepted change-management practices
- https://www.prosci.com/solutions/proxima
Supports
- Guided change planning, impact work, assessments, performance tracking, and sustainment in Proxima
- Alignment to the Prosci methodology and paid membership or licensing access
- https://www.kotterinc.com/methodology/
Supports
- Kotter methodology, training, and organizational change services
- Evolution from episodic linear change toward iterative change accelerators
- https://www.walkme.com/digital-adoption-platform/
Supports
- Cross-application usage analytics, friction discovery, contextual guidance, and workflow automation
- Personalized support at the point of work
- https://www.walkme.com/pricing/
Supports
- Quote-based paid access to WalkMe digital adoption capabilities
- Guidance, surveys, analytics, segmentation, automation, governance, and privacy controls
- https://whatfix.com/
Supports
- Personalized in-application guidance and analysis of adoption friction
- Guidance updates as processes, systems, and workflows change
- https://www.pendo.io/pendo-for-your-employees/
Supports
- Employee software process analytics, in-application guidance, sentiment, and portfolio usage insight
- Identification of cross-application friction and support for proficiency
- https://engineering.atspotify.com/2020/06/tech-migrations-the-spotify-way
Supports
- Technology migrations need portfolio prioritization, named ownership, testing with small groups, training when needed, and an explanation of value.
- Migration programs can stall in a long tail when teams are overwhelmed by competing upgrade demands.
- https://engineering.atspotify.com/2022/11/strategies-and-tools-for-performing-migrations-on-platform
Supports
- Large technology migrations face competing priorities, unclear accountability, and the need for progress metrics, projections, roadmaps, stakeholder support, and automation.
- https://slack.engineering/how-big-technical-changes-happen-at-slack/
Supports
- Adoption slows as difficult holdout use cases remain, and the change agent must build the path between current practice and the new technology.