In a minimum of 400 words, what is the most dramatic example of resistance to change that you have encountered? Looking back, what strategies might have been used to facilitate the change process? Your example does not necessarily need to be drawn from the world of health information technology, although it should have a technology focus.

Resistance to Change: The Battle Over Electronic Health Records

Introduction

Among the most consequential and contentious technology transitions of the past two decades, the large-scale adoption of Electronic Health Record (EHR) systems stands out as a dramatic case study in resistance to change. Having observed this transformation unfold across multiple healthcare institutions, the depth and persistence of the pushback from clinical staff – particularly physicians – were striking, revealing how deeply rooted cultural, professional, and psychological forces can derail even well-funded and well-intentioned technological initiatives.

The Phenomenon: Physician Resistance to EHR Implementation

In the mid-2000s, a large regional hospital network undertook the ambitious task of replacing its paper-based medical records system with a comprehensive EHR platform. The organisation had invested millions of dollars in licensing, infrastructure, and training. Leadership framed the change as a quantum leap forward — improving patient safety, streamlining billing, enabling data analytics, and ensuring regulatory compliance. By nearly every objective measure, the new system was superior.

And yet, the resistance was fierce.

Physicians, who had practised for decades using familiar paper charts, verbal handoffs, and self-designed shorthand systems, viewed the EHR as an intrusion rather than an improvement. The most vocal resistors argued that the system slowed them down, forced them through rigid documentation workflows that did not reflect clinical reality, and, most emotionally charged, pulled their eyes away from patients and toward screens. Some senior physicians openly refused to use the system, continuing to write paper orders and delegating EHR entry to nurses and residents. Others complied in form but not in spirit, entering minimal or boilerplate documentation that undermined the system’s analytical value.

What made this resistance particularly dramatic was its breadth and its social legitimacy. Unlike resistance that emerges from ignorance or fear alone, physician opposition was articulate, organised, and backed by real-world evidence. Studies began circulating documenting increases in documentation time, physician burnout, and clinician dissatisfaction, lending credibility to resistors and creating a feedback loop that emboldened others. Within eighteen months of go-live, turnover among senior physicians had measurably increased, morale surveys reflected significant deterioration, and the organisation faced a quiet but unmistakable crisis of confidence.

Root Causes of the Resistance

Understanding why the resistance was so intense requires looking beneath the surface complaints. Kotter and Schlesinger (1979) identified four primary reasons individuals resist change: self-interest, misunderstanding, different assessments of the situation, and low tolerance for change. All four were present in this case.

Physicians had spent careers developing expertise in a particular way of working. The EHR did not merely change a tool; it restructured their professional identity and disrupted their sense of mastery. A surgeon who had practised for thirty years had an intuitive, fluid relationship with a paper chart. That fluency vanished overnight, replaced by frustrating clicks, drop-down menus, and system alerts. The loss of competence, even if temporary, was psychologically destabilising.

There was also a genuine and legitimate misalignment between how the system was designed and how clinical work actually flows. The EHR had been built largely around billing and compliance requirements, not clinical cognition. Workflows that made sense from an IT or administrative perspective felt alien and counterintuitive at the bedside. Physicians were not simply being stubborn, they were signalling a real design gap that the organisation was slow to acknowledge.

Finally, the change was imposed rather than co-created. Physicians were consulted superficially during the selection process but had little meaningful influence over configuration, training design, or implementation timelines. This exclusion bred resentment and a sense that the system was something being done to them rather than with them.

Strategies That Could Have Facilitated the Change

Reflecting on this experience, several evidence-based strategies could have significantly reduced resistance and improved adoption outcomes.

First, genuine stakeholder engagement from the outset. Lewin’s classic change model emphasises the necessity of “unfreezing” current attitudes before attempting movement (Lewin, 1951). This unfreezing requires that those affected by change feel heard, respected, and genuinely influential. Forming physician-led design committees with real decision-making authority — rather than advisory roles — would have built ownership and surfaced usability concerns before go-live rather than after.

Second, identifying and empowering change champions. Within any clinical environment, some early adopters are respected by their peers and genuinely enthusiastic about innovation. Investing in these individuals as internal advocates — training them deeply, giving them protected time to support colleagues, and elevating their voices — creates social proof that change is achievable and beneficial. Kotter’s eight-step model highlights the formation of a powerful guiding coalition as essential to any major change initiative (Kotter, 1996).

Third, phased implementation with meaningful feedback loops. Rather than a simultaneous system-wide go-live, a staged rollout beginning with willing early adopters would have allowed the organisation to identify problems, refine workflows, and build a library of success stories before exposing resistant users to a still-imperfect system. Critically, feedback from early adopters needed to be visibly acted upon, demonstrating organisational responsiveness and building trust.

Fourth, recognising and addressing the emotional dimension of change. Bridges’ Transition Model (2009) distinguishes between the external change (the new system) and the internal transition (the psychological journey people must make). The organisation focused almost entirely on the technical change and largely ignored the transition. Structured forums where physicians could express grief, frustration, and anxiety without those expressions being treated as obstruction would have provided emotional release and signalled that leadership understood the human cost of the transformation.

Fifth, workflow customisation as a sign of respect. Allowing clinical departments to configure the EHR to better reflect their unique workflows, rather than imposing a single standardised configuration, would have demonstrated that the system existed to serve clinicians, not the reverse.

Conclusion

The EHR implementation described here ultimately succeeded, but at a higher human and financial cost than necessary. Years of suboptimal adoption, physician attrition, and morale damage could have been substantially reduced through more participatory, emotionally intelligent, and phased change management strategies. The most important lesson is not technical but relational: technology change is, at its core, a human enterprise. Systems succeed not when they are implemented but when they are embraced, and embracing requires trust, respect, and genuine partnership between those who drive change and those who must live it.