Skip to content
For physicians, by physicians
Leadership

Why Good Clinical Changes Die on the Floor, and How to Save Them

Most new protocols and workflows are sound on paper and abandoned in practice. Successful change depends less on the idea than on how leaders introduce, test, and support it.

Photo via Unsplash

The new handoff protocol was approved by the committee, announced in an email, and posted on the wall of the physician workroom. Three weeks later, a spot check found almost nobody using it. The idea was not wrong. The rollout was. And the leaders who championed it now believe their colleagues are simply resistant to change.

Physicians are not uniquely resistant to change. They are uniquely skeptical of changes that add work without clear benefit, arrive without explanation, and ignore the realities of the shift. Anyone who has worked a busy night has seen a well intentioned policy collapse on contact with the waiting room.

Explain the problem before the solution

Leaders tend to announce solutions. Clinicians respond much better to problems they recognize. Before introducing any new workflow, show the group the specific issue it addresses, ideally with local cases or local data your team has gathered. If physicians agree the problem is real, they will engage with the fix. If they do not, no rollout plan will save it.

Invite the skeptics early. The physician who predicts the protocol will fail usually knows exactly where it will break. Their objections are free design input.

Test small, then spread

Instead of launching across the department on a single date, pilot the change with a few willing physicians on a limited set of shifts. Watch what actually happens. Where do people skip steps? Where does the new process collide with the EHR, the nurses' workflow, or a consultant's expectations?

  • Make the new way the easier way, through order sets, templates, or default settings.
  • Remove at least one old task for every new one you add.
  • Assign a named physician champion on each shift during the early weeks.
If the new process takes more clicks than the old one, the old one will win.

Keep measuring after the announcement

Many changes quietly fade after the launch energy passes. Decide in advance how you will know whether the change is holding, and check at regular intervals. Share the results openly, including when adoption drops. A leader who says "we slipped, here is why, here is what we are adjusting" earns more credibility than one who declares victory at launch.

Close the loop with the frontline as well. When a change produces a measurable improvement, tell the people who made it happen. When it does not, be willing to retire it. Abandoning a failed initiative is not weakness. It preserves your ability to ask for the next one.

Before your next rollout, write a single paragraph that describes the problem in terms a tired physician at the end of a shift would agree with. If you cannot write that paragraph, you are not ready to launch.

Share this storyImages sized for Facebook, Instagram, TikTok, X and link previews
Dr. Daniel Reyes, DO

Dr. Reyes practices emergency medicine and writes about clinical decision making under pressure and the technology entering the ED.

This article is for professional education and does not replace clinical judgment. Treatment decisions should be based on the individual patient and current guidelines.