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 anyone who’s actually put software in front of clinicians, it’s a signal that someone is about to pathologize the dissent and skip listening to it.
“Clinician resistance.”
I’ve been in the room where these scripts get written and the trenches where they fall apart. At Epic, I was the implementation lead for two hospitals and six patient-facing web portals, directly supporting clinical teams as they navigated federal incentive programs and regulatory changes. When hospitals needed unique workflows, I built and deployed custom features, sometimes overnight, just to keep patient care and compliance on track. I co-led a national Physician Quality Reporting group, started a policy and tech network attended by over 100 healthcare organizations, and designed escalation protocols for 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 the same pattern: clinicians raising valid, specific risks were labeled “legacy thinkers” by people nowhere near the point of care.
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 was Doximity Dialer, now used by millions, and it didn’t come from a boardroom or a consultant. It started with listening to frontline physicians about the privacy and workflow headaches that legacy phone systems created. We built Dialer not to “overcome resistance,” 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.
Who Writes the Script?
The “clinician resistance” story is manufactured. Consulting giants like McKinsey, Deloitte, and Bain write the playbook, recasting professional skepticism as a personality flaw. In hospitals, HR and admin turn system breakdowns into “resilience” issues for the individual. Object on your own and you’re “managed.” Push collectively, and the union-busters arrive.
Tech vendors, including Epic, often reinforce the cycle. I’ve watched clinicians forced into documentation hell while their objections get filed under “technophobia,” despite mounting evidence that EHRs are a top driver of burnout. When I once imagined myself in their seat, I wrote that I would feel like a failure because the system itself is designed to make doctors feel inadequate, not because of my abilities. I’ve seen how “efficiency” means mandatory extra clicks for everyone but the end user.
The best healthcare tech happens with clinicians, not to them.
Then there’s academia. RAND and Harvard can diagnose burnout but always prescribe more training and “resilience” instead of vendor accountability.
In business school, I sat through healthcare management coursework where “clinician resistance” was just a line item to bulldoze through on the project plan, and nobody treated it as a red flag worth investigating.
Why Pathologize Resistance?
It works as a shortcut for leadership. Framing resistance as a defect means critique is delegitimized, accountability is 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 one transformation after another.
What’s lost is obvious to anyone who’s run a go-live: most “resistance” is professionalism. The clinicians who object are usually the ones protecting safety, standards, and patient outcomes. The so-called “resisters” are almost always the people you wish you’d listened to before launch.
If you build tech for healthcare, you’ve seen this. Maybe you’ve rationalized it under deadline, under pressure. But clinicians don’t resist technology; they resist bad technology. Every extra click, every broken workflow, every feature that flops in the wild is a threat to patient care and professional dignity.
When you build with clinicians and center their lived experience, you don’t have to fight “resistance.” Adoption and trust follow. When you get pushback, pause. Ask what 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, push back with your receipts, your data, your voice.
If you see collective action, respect it as a profession defending its standards.