Altitude Sickness: Recognizing Genuine Resistance to Change

Opening Scene

A climber at altitude showing genuine symptoms — nausea, confusion, real trouble catching their breath — looks superficially similar to one who’s simply tired and grumbling about the cold, but a good guide learns to tell the difference, because one needs descent and the other just needs encouragement and a snack. An employee who’s quietly job-hunting because they believe AI genuinely threatens their role looks, on the surface, a lot like one who’s just annoyed by a clunky new interface, and treating the two the same way tends to make both of them worse.

In Plain English

Resistance to change in AI adoption ranges from minor, fixable friction to genuine, well-founded concern — about job security, about trust in a tool’s output, about being asked to do more with less support. Surface friction and genuine resistance need different responses, and treating one as though it were the other usually makes things worse rather than better.

The Old Way

Before organizations built in any real diagnostic step, pushback tended to get treated as a single, undifferentiated problem:

All pushback got lumped together as “resistance to overcome,” regardless of its actual underlying cause.
Legitimate concerns about job impact or tool reliability were dismissed outright rather than genuinely heard.
There was no diagnostic step before a response — leadership pushed harder as a default reaction to any and all pushback.

Telling ordinary fatigue apart from genuine altitude sickness is exactly the diagnostic step this kind of resistance work depends on.

What’s Changing (and Why AI Is the Reason)

Organizations are building in a genuine diagnostic step — listening sessions, anonymous surveys, direct conversations — before deciding how to respond to pushback.
This connects to the work covered in this content library’s dedicated data ethics case studies series, since some employee resistance to AI tools is, in fact, well-founded ethical concern worth taking seriously rather than managing away.
As AI increasingly touches roles once considered safe from automation, resistance rooted in genuine job security concern is becoming more common, and needs to be named honestly rather than euphemized.

The Metaphor, Fully Extended

The Expedition	Change Management Concept
A guide checking symptoms before deciding on descent or encouragement	A leader diagnosing the real cause of pushback before responding
Genuine altitude sickness that needs descent, not encouragement	Well-founded concern that needs a real answer, not a pep talk
Ordinary fatigue that needs rest, not retreat	Surface friction that needs support, not a policy change
A team member’s symptoms taken seriously, not dismissed	Employee concerns heard directly, not waved away

For Beginners: What to Actually Do

If you’re resisting an AI tool, try to name specifically why — interface friction and job security worry need different conversations entirely.
Voice concerns directly to someone positioned to address them, rather than only venting to coworkers.
Recognize that some resistance is legitimate signal, not a personal failing you need to overcome alone.

For Practitioners and Leaders: The Deeper Layer

Build a genuine listening mechanism before deciding how to respond to pushback, rather than assuming its cause.
Separate fixable friction from well-founded concern explicitly, and respond to each differently.
Take job security concerns seriously and address them honestly rather than papering over them with reassurance alone.

Quick Recap

Resistance to AI adoption ranges from minor friction to genuine, well-founded concern.
Treating all pushback the same way, by pushing harder, usually backfires.
A real diagnostic step — listening before responding — is becoming standard practice.
Job security concerns, in particular, deserve honest engagement, not dismissal.

Where This Fits in the Series

Article 4 covered the training needed to help the team acclimatize. Article 5 covers what to do when, even with that training, some team members show genuine signs of altitude sickness rather than ordinary fatigue. Article 6 turns to the opposite end of the spectrum: the climbers who go first, adjust fastest, and can help pull the rest of the team up behind them.