Overcoming Resistance In Change Management For Launches

A knee-jerk reaction to team resistance might be: “Fire them all and start again.” But here’s the truth you probably don’t want to hear: Your team isn’t resisting change, they’re resisting you. That’s a tough pill to swallow, but let’s be honest, change rarely fails because the idea is bad. It fails because trust is broken and because you skipped the “why,” and fear filled the silence you left behind. When your team pushes back, here’s what they’re really saying: “I don’t trust where this is going.” “No one asked me.” “I’m scared, and I don’t feel safe saying that out loud.” “You’ve changed things before and left us to clean up the mess.” Change is emotional, human, and messy. So if you want real buy-in? Don’t start with a strategy deck, start with your people. Here’s how: 1️⃣ Ask Invite input early. Before rolling out a change, ask your team what they think. What are their worries? What would make this easier for them? Use open-ended questions like: “What do you see as the biggest challenge here?” “How do you think this change could help us?” 2️⃣ Listen Really listen. Don’t just nod along, take notes, ask clarifying questions, and reflect back what you’re hearing. Acknowledge the emotion: “It sounds like you’re worried about how this will impact your workload. That’s a valid concern.” 3️⃣ Validate Show you value their perspective. Even if you can’t act on every suggestion, let them know their voice matters. Be transparent about any constraints. Make the change with them, not to them. Co-create solutions. Let the team own parts of the process. When things get tough, solve problems together, not in isolation. And when things get bumpy? Because they will: ✅ Celebrate the tiny wins, because they matter more than you think. ✅ Talk about the challenges and fix them together. When leaders try to solve the bumpiness alone, they leave their team feeling lost at sea. And let’s be honest, that’s a tough place to be left alone. So bring your team into the journey, or at least keep them in the discussion. My rule is simple: If it impacts them, communicate, don’t hide. Want to drive change that actually sticks? Start with trust, not tactics.

How do you take a resistant team and guide them through a successful transformation? I led a team that went from evaluating programs to developing them—a complete transformation. At first, there was a lot of pushback, but by understanding their concerns and using a thoughtful approach, we made the transition work.   ---Here’s what I learned--- 🔸Resistance isn’t about the change—it’s about fear of loss. Through candid one-on-one conversations, I discovered the team feared losing their expertise. 🔸Facts don’t inspire change. Stories do. Rather than overwhelm them with reasons for the shift, I shared stories. Emotional buy-in through storytelling sparked curiosity. 🔸Small behavioral nudges lead to lasting change. We didn’t push the team into full-scale program development right away. Instead, we used small steps that eased them into the transition. This made the change feel natural, not overwhelming. 🔸Your biggest resister can become your strongest advocate. I focused on the team’s informal leader—the person everyone trusted. Once he embraced the change, the rest followed. 🔸Embrace failure as a stepping stone to success. We reframed setbacks as learning opportunities. By openly discussing challenges and solutions, we created a culture where innovation thrived and fear of failure diminished. 🏡 Think of change like remodeling a house. Exciting, but full of unexpected snags. In business, it’s the same—something always comes up. Plan for it. Expect it. 💡 Key Lesson: Resistance isn’t a roadblock—it’s part of the process. Expect pushback and guide your team with strategic nudges. What unexpected challenges have you faced when leading change?

Your Team Resisting Continuous Improvement This is one of the most common leadership challenges I see inside organizations today. You introduce a change initiative or improvement program and instead of excitement, you’re met with resistance, indifference, or quiet compliance. Let’s talk about what’s really going on and how to navigate it. Most teams aren’t resisting change because they’re lazy or negative. They’re resisting because they’re overwhelmed. They’ve seen process improvement programs come and go. Each one demands more energy, more reporting, more meetings while their day-to-day pressures remain untouched. So resistance shows up like this: ▪️“We don’t have time for this.” ▪️“What we’re doing now is working fine.” ▪️Passive attendance in improvement meetings(no follow-through). ▪️Quiet reversion to old habits after the hype fades. All these sound familiar? Well, to break this cycle, you have to stop selling the vision and start solving real pain. Here’s how: → Start with their pain, not your plan Ask: “What’s frustrating you the most right now?” Build your first improvement around that. Solve something that slows them down today, not next quarter. → Keep it micro Forget transformation. Focus on a small win. Ask: “What’s one task we could make easier this week?” Success creates momentum. People buy into what works. → Make it theirs If you’re the only one pushing, it’s not sustainable. Invite the team to identify pain points, test ideas, and lead change. When it’s their idea, the energy is different. → Celebrate learning and not just success Teams need to know that failed experiments won’t be punished. If a trial doesn’t work, ask: “What did we learn?” That’s what builds a culture of real improvement. When teams own improvement: ▫️They become faster at spotting and fixing issues. ▫️Innovation happens closer to the work. ▫️Change doesn’t have to come from the top. It just happens from within. But when they don’t: ▪️Progress stalls. ▪️Leaders spend energy enforcing instead of empowering. ▪️The culture becomes resistant, not resilient. And if you can build teams that lean into improvement, you are able to: 📍Position yourself as a leader who drives results through people. 📍Reduce friction in delivery. 📍Increase the long-term capacity and agility of your team. But if you're always the one pushing change onto people, you risk being seen as the “process person” and not the strategic leader. Here's something to remember Don’t sell continuous improvement. Co-create it. Start small. Start real. Make it theirs. 👉 What are the resistance patterns you see and what’s one small improvement you could adopt?

If you want employees to support a new idea or experimentation program, Don’t drown them in fancy presentations or data. Tell them what they want to know: How will this disrupt their day-to-day. People don’t resist the program. They resist how it impacts them. So, this is what you’re going to do: 1. Sit down 1:1 and listen more than you speak. Ask open-ended questions like: → “What concerns do you have about this program?” → “How do you see it impacting your role?” 2. Identify the fear. Resistance stems from: → Fear of irrelevance or failure → Worry about extra workload without extra resources → Misalignment with their goals or compensation 3. Solve their problem first. Address their concerns directly. Show how the program will help them grow, simplify their work, or align with their goals. 4. Follow through. Once the program launches, routinely check-in. Make sure their concerns remain addressed, and adjust as needed. Real growth starts with creating an understanding.

Here's a puzzle that keeps me up at night: Why do initiatives with clear benefits face so much internal pushback? Take #CMS #SDOH Data Collection Requirements: Leadership perspective: This is obviously the right thing to do. Better population health, targeted interventions, improved outcomes. IT perspective: System overhauls, tight deadlines, compliance risks. Finance perspective: Significant upfront costs, unclear reimbursement. Nursing perspective: More documentation, workflow disruptions, patient discomfort. Provider perspective: Additional training, compliance burden, workflow changes. Same initiative. Completely different realities. We often champion initiatives based on their end-state benefits while health system teams experience implementation pain. When nurses resist SDOH screening, we see "resistance to change." They see "more work, same pay." Organizations that map stakeholder impacts before announcing initiatives see dramatically smoother implementations. They build support strategies, and not just communication strategies. Before the next major initiative: 1. Map the real experience and don't just present the benefits - understand who faces immediate pain vs. long-term gain. The groups experiencing Year 1 losses need different support than those seeing eventual wins. 2. Sequence the conversations and stop giving everyone the same "population health" message. IT directors needs resource planning. Nurses need workflow solutions and support (can we remove something else if adding this on?). CFOs need ROI timelines. 3. Plan for stakeholder-specific support. IT teams need dedicated implementation resources. Clinical staff need workflow optimization, not just training. Finance teams need milestone-based ROI demonstrations. Front-line staff need to understand "what's in it for me." 4. Reframe resistance as predictable dynamics when your nurses push back on SDOH screening, it's not resistance to change - it's a predictable response to increased workload without clear benefit. Plan for it. Want to map your next initiative before resistance emerges? Try my custom version of Andrew Tsang's Healthcare Seesaw - and see exactly how your "obviously good" idea affects each stakeholder group. I've attached screenshots of #TEFCA and #SDOH. https://lnkd.in/g2yHtpA8 What "obviously good" initiative surprised you with unexpected pushback? #ChangeManagement #StakeholderStrategy #HealthcareStrategy #DigitalTransformation #healthcare #clinicalinformatics #informatics

Resistance doesn't knock on your door: It grows quietly. In the silence after a decision is announced. In the meeting where no one pushes back anymore. In the project that keeps getting delayed for reasons no one can articulate. By the time it's visible, it's already hardened. But there's a window—early on—where resistance is still flexible. Where it can be surfaced, understood, and redirected. That window opens through questions. Not generic ones. Strategic ones. Here are 10 questions that surface resistance before it hardens: ✅ What feels unclear right now? Confusion hides anxiety. If people can't articulate what's unclear, they default to protection, Slowing decisions, avoiding ownership. Clarity reduces threat. Ask this often. ✅ What concerns haven't we talked about yet? Not "any questions?" That gets silence. Ask specifically about what's unsaid. It signals safety for discomfort to surface. ✅ Where might this change make your role harder before it makes it better? This normalizes the competence dip. When people feel slower, they interpret it as personal failure. Naming the difficulty reduces shame-driven resistance. ✅ What part of this change feels most disruptive to how you've worked before? Resistance often attaches to identity. This surfaces attachment to legacy processes without shaming experience. ✅ What risks are we overestimating—and what risks might we be underestimating? This moves conversation from fear to structured thinking. It prevents quiet catastrophizing while respecting legitimate concerns. ✅ Where are decisions slowing down—and why? Decision velocity is an early indicator of resistance. If calls are being escalated or revisited, something feels unsafe. Surface it before delay becomes culture. ✅ What would make this change feel more workable for you? This shifts people from passive resistance to active problem-solving. It gives them agency. Agency reduces threat. ✅ What assumptions are we making about readiness? Leaders often assume understanding equals preparedness. This surfaces capability gaps early, before frustration turns into withdrawal. ✅ Where are you feeling least confident right now? Confidence gaps go unspoken. When competence feels exposed, people over-control or disengage. Addressing confidence directly prevents both. ✅ If this fails, what will be the reason? The most revealing question. It surfaces hidden skepticism and fear constructively. Better to hear it now—when it can be addressed—than later, when it becomes "I knew this wouldn't work." These questions don't create resistance. They reveal what's already there. And what's revealed early can be redirected. Want the complete framework for leading conversations that surface resistance before it stalls your transformation? Download "The Hidden Landscape of Resistance" at freebook.sarajunio.com Free guide. Real questions. Built for leaders who want honest dialogue, not performative alignment.

"Resistance to change" is one of the most dangerous phrases in business. Not because it's wrong. Because it's lazy. When employees push back on a transformation, we reach for that phrase like a reflex. "They're resistant." "People fear change." "We need more communication to overcome resistance." Here's what's actually happening most of the time: employees are diagnosing problems that leadership hasn't seen yet. The team that won't adopt the new system? They've already figured out it doesn't match their actual workflow. The middle managers dragging their feet? They can see the contradiction between what you're saying and what you're measuring. The "resisters" on the front line? They're doing sophisticated analysis of whether this change will actually work, in real time, with better data than the executive team has. But orthodox change management doesn't have a category for that. It has "resistance" and "adoption curves" and tools for overcoming pushback. It has no tools for listening. So what happens? The diagnostic feedback gets pathologized. Employees who point out real problems get labeled resisters. Their concerns get addressed with more communication, which usually just means more repetition of the same message they already heard and found unconvincing. This creates a vicious cycle. Employees see their concerns aren't being heard. They conclude leadership isn't interested in reality, only in executing a predetermined plan. Trust erodes. People stop surfacing problems because it doesn't help and might hurt their career. The change proceeds with less intelligence than it started with. I watched this play out at a national healthcare network. Leadership rolled out a new digital intake system. Nurses pushed back. The executive sponsor called it "classic resistance" and ordered more training. One regional director quietly ran listening sessions instead. She asked staff to walk her through a typical day. What emerged wasn't fear of change. It was diagnosis. The system required triple data entry, broke integration with patient records, and delayed triage during peak hours. They paused the rollout. Embedded frontline staff in the redesign. Within three months, error rates dropped 40%. The so-called "resisters" saved the project. The shift from "overcoming resistance" to "harvesting intelligence" is one of the most powerful moves a leader can make. It changes who speaks up, what information surfaces, and how fast you can adapt when reality diverges from the plan. Most organizations never make that shift. They'd rather blame the humans than question the plan.

Every C-level Exec knows this truth: the hardest part of transformation isn’t building the strategy, it’s getting the organization to move with you. Resistance shows up quietly at first: delayed decisions, reluctance to adopt new processes, or teams defaulting to the familiar. It’s easy to interpret this as obstruction. But in reality, it’s a signal that people don’t yet see themselves in the future you’re trying to build. At the enterprise level, transformation requires more than a roadmap....it requires belief. Senior leaders must make the case for change early and often, frame the trade-offs honestly, and reinforce the organizational “why” in every conversation. When associates understand the purpose, have clarity on expectations, and feel their expertise is valued in the process, momentum accelerates. Alignment becomes cultural, not mechanical. As you lead your organization into its next chapter, don’t underestimate the power of involvement and communication. Invite your teams into the narrative, bridge the gaps between intent and execution, and show, consistently, what progress looks like. Transformation sticks best when people feel they are part of building it, not simply living through it. #Leadership #ChangeManagement #OperationalExcellence #ExecutiveInsights #BusinessTransformation

Your team resists change for a reason. They've been burned by half finished transformations before. The problem isn't your strategy. It's your organization's readiness for change. Here are the 4 pillars that determine success: LEADERSHIP COMMITMENT: → Leaders set direction and remove barriers → They model the behaviors needed for success → Without commitment from the top, change dies PROCESS FLEXIBILITY: → Agile, adaptable processes enable quick responses → Flexibility keeps momentum without losing consistency → Rigid systems break under transformation pressure CONTINUOUS LEARNING: → Equip people with new skills and tools → Encourage curiosity, coaching, and growth mindset → Learning transforms resistance into capability EMPLOYEE ENGAGEMENT: → People support what they help create → Involvement builds ownership and reduces fear → Engagement turns skeptics into champions But readiness isn't just about these pillars. It's about the systems that support them: ✓ Communication Clarity - Simple, consistent messages ✓ Stakeholder Buy In - Leaders actively advocating ✓ Training Availability - Right skills, resources, confidence ✓ Feedback Loops - Regular input to refine momentum ✓ Measurement Systems - Clear KPIs and progress tracking ✓ Resource Alignment - Time, budget, tools dedicated to change Most transformation failures aren't strategic failures. They're readiness failures. Organizations rush to implement before they're prepared. Then wonder why good ideas get poor results. The companies that transform successfully? They invest in readiness before they invest in change. Which pillar is strongest in your organization right now?

Your best idea just got shot down in a meeting. Again. Here's what most leaders miss: Resistance isn't your obstacle. It's your roadmap. I learned this during two years of stakeholder pushback on a digital initiative. "This is too complicated" actually meant, "We need a clearer implementation plan that explains everyone's role." The translation work is everything: "We can't prioritize this" may mean, "We have tough goals to meet and can't risk missing them." "Compliance will block it" may mean, "We need to understand regulatory requirements upfront." "This will never work" may mean, "Our project planning needs to evolve to handle this complexity." Why we miss this: When you hear resistance, your amygdala—the brain's threat detector—reacts milliseconds before rational thought kicks in. With “Amygdala Hijack,” you get into defensive mode automatically. Shift with three steps: 1. Interrupt the reaction. Take a breath and count to three. This pause activates your frontal lobes, enabling thoughtful response over a defensive reaction. 2. Ask questions that invite depth. "What would need to be true for this to work?" transforms adversaries into advisors. 3. Map patterns across stakeholders. When multiple people raise similar concerns, you've found a blind spot. That's your implementation roadmap revealing itself. Resistance isn't the enemy. It's often the source of the smartest feedback you'll get. What's one phrase you've heard that stopped you cold—and what do you think it was really saying? #ChangeAdvocates #resistance #strategy #leadership