Resistance to Change: Why It Happens and What Actually Works

In aviation, change is constant. New regulations, airworthiness directives, safety requirements, technologies, and operational improvement initiatives are introduced on a regular basis. Some of this change is externally driven and unavoidable. Other changes are internally driven, aimed at improving efficiency, reliability, or performance.

Yet despite this constant flow of change, implementation is rarely straightforward. Some changes are fully embedded, others are partially adopted, and many lose momentum after initial rollout.

In practice, this is where change management in aviation often fails—not in the design of change, but in how it interacts with operational reality.

Resistance to change is often described as a people problem. In reality, it is better understood as a system response to disruption in stability.

When operations are stable, teams build routines that reduce uncertainty. People know what to expect, how to act, and where responsibility sits. Any change—regardless of its quality—interrupts that stability. What appears as resistance is often caution in a safety-critical environment where predictability is part of how risk is controlled.

The challenge is not whether change is accepted, but how it is introduced into a system already balancing multiple constraints.

Change introduces uncertainty into stable systems

Most airline operations are built on repetition. Maintenance planning, operational coordination, compliance activities, and reporting cycles depend on predictable execution. Over time, organizations optimize not only for efficiency, but for reliability under pressure.

Even when a change is objectively an improvement, it temporarily increases uncertainty. People must interpret new steps, adjust responsibilities, and adapt to new ways of working. During this transition, performance can appear to decline before it improves.

Resistance often appears here. It is not resistance to improvement, but resistance to losing operational clarity without immediate replacement.

Hidden workload is often underestimated

Change is usually designed from a procedural perspective: what should be added, removed, or modified. What is less visible is the actual workload created at the operational level.

In aviation environments, teams already operate close to capacity. Operational disruptions, time pressure, and compliance demands leave limited space for experimentation during daily work.

When change is presented as “just adapting,” it overlooks the fact that adaptation itself requires time, attention, and correction. Without creating capacity for this, resistance becomes predictable system behavior.

Resistance is often a signal, not an obstacle

What is labeled as resistance is often feedback from the system.

Frontline teams are usually the first to see when a change does not align with operational reality. A new reporting structure may improve visibility at management level but create duplication in execution. A standardized process may increase compliance but reduce flexibility in irregular operations. A digital tool may improve traceability but slow down time-critical decisions.

In these cases, resistance is not the problem. It is information about misalignment.

Ignoring it does not remove the issue. It only moves it elsewhere in the system.

Ownership determines adoption

Change that is only communicated tends to remain superficial. Change that is co-developed tends to be embedded.

In aviation, frontline expertise is often deeper than what is captured in formal procedures. When change is designed without involving the people who execute the work, it risks being correct in theory but misaligned in practice.

This is where structured alignment approaches such as Hoshin Kanri become relevant. Strategy deployment only works when objectives are translated into operational reality through dialogue, not one-way instruction. The catchball process is especially important because it creates continuous feedback between leadership intent and operational feasibility.

Ownership does not mean agreement with every detail. It means involvement in shaping how change will work in practice. Without it, adoption depends on enforcement rather than understanding.

The pressure of speed and the nature of change

Change in aviation is not optional. Some changes are externally driven and unavoidable—regulatory updates, airworthiness directives, safety requirements, and compliance obligations. These must be implemented within strict timelines.

At the same time, many changes are internally driven. These include process improvements, organizational adjustments, and digital transformations. These require a different approach because success depends on alignment with frontline execution.

Treating both types of change in the same way creates friction. Regulatory change requires disciplined execution. Operational change requires engagement, feedback, and adaptation.

However, both share one requirement: they must be introduced without destabilizing operations.

When change is accelerated without alignment, the system compensates through partial adoption, informal workarounds, or parallel processes that are not always visible.

Building change that lasts

Effective change is not about removing resistance. It is about designing transitions that respect how operational systems behave.

This requires:

• Understanding existing workflows before redesigning them

• Identifying where additional workload is created

• Creating space for learning during transition

• Involving operational teams early in the design phase

• Using structured alignment methods such as catchball

• Accepting that short-term instability is part of improvement

Change is not an event. It is a transition from one stable state to another. The quality of that transition determines whether improvement becomes embedded or fades out.

Lean perspective

From a Lean perspective, change must be understood where work actually happens. Going to the Gemba allows leaders to see operational reality rather than assumptions.

Kaizen ensures change is incremental and tested rather than disruptive. Small adjustments reduce system shock while allowing continuous improvement. Standard work provides stability, but only if it reflects real operational conditions.

Hoshin Kanri adds strategic alignment, ensuring that objectives are not just defined but translated into executable actions through structured dialogue.

When change is built with those who perform the work, resistance decreases—not because it disappears, but because alignment replaces imposition.

Conclusion

Resistance to change in aviation is not an obstacle to progress. It reflects how complex systems protect stability under uncertainty.

Some changes must happen because they are required. Others must succeed because they are designed. In both cases, success depends on how change is introduced into the system.

When operational reality is respected and alignment is actively built, change becomes part of the system rather than something imposed on it.

Learn to engage teams and achieve strategic objectives →