Change Management Fatigue: Why Trust May Be the Better Strategy

Change management was once reserved for significant events, such as mergers, restructurings, layoffs, or system-wide changes. Now, it is often applied by default, even for minor updates like introducing a new tool or redrawing a stakeholder map. Routine adjustments trigger communications plans, training, and the appointment of change champions. As a result, we have started managing changes that may not require such oversight.

This approach has consequences: 75 percent of organizations still use a top-down method, making decisions, announcing them, cascading information, and providing training. However, 73 percent of employees report moderate to high stress linked to these change programs, and 54 percent of those experiencing change fatigue are seeking new jobs. These outcomes suggest that over-management, especially for minor changes, leads to unnecessary strain rather than improvement.

This trend does not stem from leaders enjoying the process itself. Instead, visible and formal change management creates a sense of action. Tangible outputs like communications plans and training presentations reinforce this feeling. However, allowing teams to adapt to minor changes independently may feel less like leadership, even though it is often more appropriate.

Research confirms this perspective. Employees’ commitment to change depends less on rollout quality and more on two factors: their freedom to determine how to implement change and their trust in leadership’s intentions. When companies impose 'empowerment' as a managed initiative, it often backfires. Employees view it as extra work, not as trust, leading to exhaustion. Trust cannot be manufactured through formal programs; attempts to do so may undermine it.

The solution is not to apply change management more carefully, but to use it more selectively and replace formal processes with genuine trust.

The first step is to review all current formal change activities and assess whether they are truly necessary. Not every change is disruptive. Only changes that affect assessment, compensation, organization, or employment require comprehensive management. Applying the same process to routine adjustments causes unnecessary fatigue.

We should reconsider when people are involved in the process, not just how often they are consulted. True autonomy occurs before plans are finalized, not through feedback surveys after decisions are made. Seeking input post-decision appears performative and leads to the 'empowerment as extra work'. Change capacity should be treated as a finite resource, not as unlimited. Multiple small changes introduced simultaneously can combine into a significant, unanticipated burden if not managed collectively.

This is not an argument against change management. Major changes that affect how people work, their reporting lines, or employment status should receive careful attention. However, more processes are not always better. Sometimes, the most effective leadership is to trust that a change does not require formal management.

I believe organizations should focus on trusting people to adapt, rather than perfecting the management of change. These are distinct skills, and we have prioritized the wrong one.