Overcoming Resistance to Agile Leadership

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?

Some company cultures are just not compatible with Agile. They treat Agile as a process that can be implemented, rather than a change in mindsets, behaviors, and most of all, values of the people doing the work. Someone up top has decided that we’d better implement this Agile thing. The PMO is assigned to “go figure it out” and come back with a plan. A few months later, Agile processes are feeling heavily bureaucratic or like a bunch of checkbox exercises. There is confusion about roles and responsibilities, and things are getting messy. The problem is that you're struggling to adopt Agile methodologies at the values-level, making it feel more like a set of rules to follow rather than a different way of working altogether. It’s like your company starts up an employee baseball tournament. Only, you’re not allowed to go outside. You have to play in one of the big conference rooms. Oh, and you have to use whatever equipment you find in the supply room. The solution is to start with the values and principles behind Agile first, not the processes. The fundamental values of Agile are often in direct opposition to the established culture of the company. But by addressing the cultural blockers up front, you’ll be more likely to move toward Agile ways of working. 1) Self-organizing teams. The team is the primary unit of an Agile approach, not the individual. Decisions are often made collectively. People can switch roles or overlap without needing any permission or supervision from outside the team. The rigid culture around role definition, incentive and reward structures, and decision making will all need to be modified FIRST before you can support self-organizing teams. 2) Building in smaller increments. Teams cannot know in advance everything they need to know in order to build a working complex system, which most products and applications are. Instead, they need to start with a rough idea that includes a vision, some clear objectives, and some general constraints. Executives attempt to exert a high degree of control over everything before embarking on a project that is large and complex. Leaders will need to change the way they think about planning and funding projects to be able to adapt to Agile ways of working. 3) Adapting to change. The heart of Agile approaches is the acceptance of unknowns, and the ability to change direction based on new information coming in as we go. This is another hard pill to swallow for rigid corporate cultures. Planning has been an important part of company cultures since the days of Frederick Winslow Taylor, and old habits die hard. Executives need to get more comfortable with embracing flexibility rather than adhering to a plan. We work with leaders to help them understand, appreciate, and adopt the changes of mindset, culture, and values necessary before or during big transformations. If you're stuck in the middle of a messy Agile rollout, give me a ping and we'll talk.

We don’t resist change. We resist not knowing where we’ll land. Most pushback is rational. We hold on to what’s worked because the next step isn’t clear. If we don’t see the logic, If it doesn’t feel safe to try we stall. Every time. The job isn’t to “manage resistance.” It’s to de-risk what’s ahead. Here are 7 strategies that have helped my teams (and me) move through change faster: 1. Model it first → If leaders don’t go first, nothing moves. → We follow behavior, not slide decks. 2. Share the why, not just the timeline → Don’t wait for the perfect plan. → Share what’s changing, what’s at stake, and what we’re betting on. 3. Involve the people closest to the work → Real alignment doesn’t come from top-down decisions. → It comes from early input. 4. Make the first step feel doable → We don’t need the full blueprint. → Just a clear first move we can act on with confidence. 5. Train for what’s different → Belief ≠ readiness. → We resist when we don’t feel equipped. 6. Name what’s really going on → Resistance often hides fear or confusion. → Ask early. Ask directly. Don’t let it build. 7. Show it’s working and work hard on what’s not → Small wins build trust. → But trust grows faster when we’re honest about what still needs fixing. Most of us try to scale with complexity. But the real unlock? We simplify. That’s how we move forward - together. * * * I talk about the real mechanics of growth, data, and execution. If that’s what you care about, let’s connect.

"If you have to force change, you've already failed." This became painfully clear when I learned why the majority of organizational transformations collapse… Last week, in a workshop with Tamsen Webster, MA, MBA, I learned a term that fundamentally altered how I view organizational psychology: Reactance. I now call it "The Corporate Immune System" - and it's quietly destroying your change initiatives. Here's the counterintuitive truth most leaders miss: The harder you push for change, the stronger the organizational antibodies become against it. Consider this paradox: When you mandate transformation, you simultaneously create its greatest obstacle. When you force evolution, you guarantee devolution. When you demand innovation, you breed stagnation. HARD TRUTH: Your brain has a freedom detector. And when it senses a threat, it doesn't just resist - it architects elaborate systems of opposition. 𝗧𝗵𝗲 𝗦𝗰𝗶𝗲𝗻𝗰𝗲 𝗼𝗳 𝗦𝘂𝗰𝗰𝗲𝘀𝘀𝗳𝘂𝗹 𝗖𝗵𝗮𝗻𝗴𝗲: 1. The Autonomy Principle "Don't push the boulder. Build the slope." * Every forced change creates an equal and opposite resistance * The energy you spend overcoming resistance could have been spent creating momentum * Psychological safety isn't a buzzword - it's the foundation of transformation 𝟮. 𝗧𝗵𝗲 𝗣𝗮𝗿𝘁𝗶𝗰𝗶𝗽𝗮𝘁𝗶𝗼𝗻 𝗣𝗮𝗿𝗮𝗱𝗼𝘅 "𝗧𝗵𝗲 𝘀𝗹𝗼𝘄𝗲𝘀𝘁 𝘄𝗮𝘆 𝘁𝗼 𝗰𝗵𝗮𝗻𝗴𝗲 𝗶𝘀 𝘁𝗼 𝗳𝗼𝗿𝗰𝗲 𝗶𝘁" * Speed of implementation ≠ Speed of integration * Involvement beats compliance by a factor of 4 * The time you "waste" in collaboration is recovered tenfold in execution 𝟯. 𝗧𝗵𝗲 𝗟𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 𝗟𝗲𝘃𝗲𝗿𝗮𝗴𝗲 𝗣𝗼𝗶𝗻𝘁 "𝗖𝗵𝗮𝗻𝗴𝗲 𝗵𝗮𝗽𝗽𝗲𝗻𝘀 𝗮𝘁 𝘁𝗵𝗲 𝘀𝗽𝗲𝗲𝗱 𝗼𝗳 𝘁𝗿𝘂𝘀𝘁, 𝗻𝗼𝘁 𝘁𝗵𝗲 𝘀𝗽𝗲𝗲𝗱 𝗼𝗳 𝗳𝗼𝗿𝗰𝗲" * Trust is the hidden multiplier in all transformation equations * Authority can mandate behavior but never belief * The best change strategies make resistance harder than adoption Here's what the research shows: * 70% of change programs fail to meet their objectives (McKinsey) * Projects with excellent change management are 6x more likely to succeed (Prosci) * Organizations with effective change management practices report 143% higher ROI compared to those with minimal change management (Prosci) Intellectual humility moment: I had to unlearn a decade of "best practices" to understand this fundamental truth - the most effective change feels chosen, not imposed. What conventional wisdom about change leadership do you need to unlearn? #OrganizationalPsychology #ChangeManagement #LeadershipScience Tamsen Webster - Your reactance framework revolutionized my approach to change.