Change Management

The gap between "project delivered" and "value realized" is almost always a change-management gap. A new HRIS goes live on schedule, under budget, with all features working — and six months later, managers still use spreadsheets, employees still file tickets the old way, and the ROI case collapses. Change management is the work that closes that gap: communication, training, incentive alignment, leadership behavior, feedback loops, reinforcement. Organizations that invest proportionally in change management capture the value projects were meant to deliver. Organizations that treat it as "training plus a launch email" do not.

Take a 6,000-person company rolling out a new ERP over 18 months. The change-management workstream runs in parallel to the technical build. Activities: (1) stakeholder mapping — who is impacted, how, and what their starting disposition is; (2) case-for-change narrative — why this is happening, what changes for whom, what does not change; (3) leader alignment — executives modeling the new behaviors and actively sponsoring; (4) change-agent network — trained champions in each business unit carrying the message and surfacing resistance; (5) training curriculum — role-specific, not one-size-fits-all; (6) communication cadence — sustained over 12+ months, not a launch event; (7) adoption measurement — login frequency, transaction completion, help-desk volume, user sentiment. The change-management team (10-15 people for a project this size, internal plus consultants) operates with its own plan, budget, and executive sponsor.

Change management is chronically under-resourced on technology projects. The budget for software licenses and implementation partners gets approved; the budget for sustained organizational change gets whittled to training decks and a launch webinar. The post-go-live reality is the same: the project hits its milestones, and adoption stalls. The organizations that get this right treat change management as a first- order investment — typically 10-15% of the total project cost — and staff it with people who have done it before. The organizations that don't produce a portfolio of technically-delivered, operationally-unused systems and wonder why their technology investments aren't paying off.

In manufacturing, change management interacts with unionized workforces, plant-level operations, and safety culture. Change moves slowly and requires union engagement.

In healthcare, change management among clinical staff is especially sensitive — changes perceived as adding to clinician burden face sharp resistance. Clinical leadership sponsorship is essential.

In financial services, change management intersects with regulatory timelines (changes often have mandatory dates) and risk controls (changes often have audit implications).

In tech, change fatigue is a structural issue — the volume of change is high, and teams develop antibodies to "yet another rollout." Less can be more.

In retail and hospitality, change management to distributed frontline staff is a different discipline — relying on mobile channels, managers as multipliers, and in-moment training rather than classroom curriculum.

In public sector, change management operates within political and civil-service constraints; sustained sponsorship across leadership transitions is the hardest challenge.

AI changes change management in 2026 in both useful and risky ways. Useful: personalized training, AI-generated communication content at scale, sentiment monitoring from workplace tools, adoption analytics that surface resistance pockets earlier. Risky: the speed of AI-enabled rollouts creates new change-management load — when every quarter brings a new capability, the organization lives in continuous change, and change fatigue becomes the binding constraint. Mature organizations are investing in change- management capability not just for specific projects but as a standing function — because the rate of change is now the baseline, not the exception.

• Underinvesting. Allocating 2% of project cost to change management and 98% to implementation. The adoption gap that results is predictable.
• Communication as change management. Emails and launch events are channels, not strategy. Behavior change requires more than messaging.
• No sustained sponsorship. Leaders launch the change, then return to their day jobs. Sustained visible sponsorship is what keeps change alive past the launch.
• Training without reinforcement. Classroom training followed by no reinforcement produces forgetting. Application, coaching, and measurement matter more than the initial training event.
• Ignoring resistance as a signal. Resistance often contains information — about unrealistic timelines, missing capability, or flawed design. Treating it only as obstacle misses the signal.
• Change fatigue unacknowledged. Running too many changes concurrently produces saturation. Portfolio-level change management matters as much as project-level.