When Change Efforts Keep Stalling or Meeting Resistance
The situation
You’re trying to roll out an important change — a new workflow, process, policy, or initiative — and it feels like you’re pushing a boulder uphill. Staff push back, workarounds pop up, timelines slip, and what looked good on paper unravels in real life. You start wondering why change always feels so hard, even when the idea itself is solid.
What’s really happening
Most change efforts don’t fail because the idea is bad — they fail because people feel excluded from shaping it. When decisions are made for people instead of with them, resistance is a natural response. In complex healthcare systems, frontline staff often see practical gaps and downstream consequences long before leadership does. When their insight isn’t engaged early, problems surface after rollout — costing time, trust, and energy.
What helps
Instead of implementing top-down, implement backwards:
Start with a proposal, not a final decision
Bring the idea forward early.
You might say: “Here’s a proposal — I’d love your input before anything gets finalized.”
Invite the people who will execute the change to help shape it
Engage them from the beginning. Bring the idea to the people who will be implementing it and ask for their insights.
Encourage honest feedback and let teams surface gaps early
Create space for real input.
You might say: “Let’s poke holes in this — what are we missing?”
Refine the plan before it becomes official
Use feedback to strengthen the approach. Use it to adjust the approach before making any final decisions.
Pilot small when possible, then finalize with shared ownership
Test, learn, and then roll out.
You might say: “Let’s test this on a small scale first and see how it works before we roll it out more broadly.”
This approach doesn’t take more time overall — it simply shifts the effort from fixing problems later to preventing them earlier.
When people help design the change, resistance drops, trust grows, and implementation moves faster.