It’s the diagnosis pulled out whenever a doctor or nurse pushes back on some new system, tool, or“transformation.” To outsiders, it sounds neutral—a “change management” hiccup. But to anyonewho’s actually put software in front of clinicians, it’s a signal that dissent is about to be pathologized, not heard.
“Clinician resistance.”
I’ve been in the room where these scripts get written and the trenches where they fall apart. At Epic, I was theimplementation lead for two hospitals and six patient-facing web portals, directly supporting clinical teams as they navigatedfederal incentive programs and regulatory changes. When hospitals needed unique workflows, I built and deployed customfeatures—sometimes overnight—just to keep patient care and compliance on track. I co-led a national Physician QualityReporting group, started a policy and tech network attended by over 100 healthcare organizations, and designed escalation protocolsfor regulatory crises.
Next time you hear “clinician resistance,” treat it as a signal.It’s an invitation to fix what’s broken, build trust, and actually improve care.
In every case, I saw thesame pattern: clinicians raising valid, specific risks were labeled “legacy thinkers” by people nowhere near the point ofcare.
Later,as a product manager at Doximity, I managed teams of engineers, UX designers, and data scientists across multiple launches,ultimately taking full ownership of user growth and mobile app strategy. My team’s most successful launch—DoximityDialer, now used by millions—didn’t come from a boardroom or a consultant. It started with listening to frontlinephysicians about the privacy and workflow headaches that legacy phone systems created. We built Dialer not to “overcomeresistance,” but to solve pain points clinicians had flagged for years. The result was immediate adoption, not because we“managed change” but because we respected the realities of care. When you listen up front, “resistance” isreplaced by trust.
Who Writes the Script?
The“clinician resistance” story isn’t organic—it’s manufactured. Consulting giants like McKinsey,Deloitte, and Bain write the playbook, recasting professional skepticism as a personality flaw. In hospitals, HR and admin turnsystem breakdowns into “resilience” issues for the individual. Object quietly and you’re “managed.”Push collectively, and the union-busters arrive.
Tech vendors—including Epic—often reinforce the cycle. I’vewatched clinicians forced into documentation hell while their objections get filed under “technophobia,” despite mountingevidence that EHRs are a top driver of burnout. I’ve seen how “efficiency” means mandatory extra clicks foreveryone but the end user.
The best healthcare tech happens with clinicians, not tothem.
Then there’s academia. RAND and Harvard can diagnose burnout but always prescribe more training and“resilience”—never vendor accountability.
And business school? I sat through healthcare management courseworkwhere “clinician resistance” was just a line item to bulldoze through on the project plan, not a red flag to investigate.
Why Pathologize Resistance?
Because it’s a shortcut for leadership. Framing resistance as a defect means critique is delegitimized, accountabilityis dodged, consulting budgets stay bloated, and clinicians are kept too atomized to organize. Burnout and turnover get chalked up to“resilience gaps,” never the churn and incoherence of endless transformation.
What’s lost is obvious toanyone who’s run a go-live: most “resistance” is professionalism. The clinicians who object are usually the onesprotecting safety, standards, and patient outcomes. The so-called “resisters” are almost always the people you wishyou’d listened to before launch.
If you build tech for healthcare, you’ve seen this. Maybeyou’ve rationalized it—under deadline, under pressure. But here’s the truth: clinicians don’t resisttechnology, they resist bad technology. Every extra click, every broken workflow, every feature that flops in the wild is athreat to patient care and professional dignity.
When you build with clinicians—when you center their livedexperience—you don’t have to fight “resistance.” Adoption and trust follow. When you get pushback, pause. Askwhat the frontline knows that you don’t. When a whole unit objects, don’t cherry-pick “early adopters.”Figure out what the skeptics are actually protecting.
In healthcare, “move fast and break things” means breaking
people. Go slow. Get it right. If leadership blames staff, use your receipts, your data, your voice—push back.
If you seecollective action, respect it. That’s what a profession looks like defending its standards.