Kellymallery.com
Episode 23 - The Other Four Ways You Might Be Making Resistance Worse Without Realizing It
Have you ever found yourself tightening the rules, pulling out more data, bending over backward to keep everyone happy, or avoiding someone who just won't get on board?
You might think you're doing what's necessary to move a change forward. But what if some of those behaviors are actually making resistance worse?
In this episode of Thoughts on Change, we're wrapping up our series on the Resistobots™ by exploring the other four patterns that can get in the way of our effectiveness as change leaders: Commandax, Factron, Softstep, and Shellout.
These aren't labels for the people resisting your changes. They're patterns in us—the ways we instinctively respond when we're uncomfortable, feeling challenged, or facing resistance.
And while each one has a valuable strength behind it, those strengths can become counterproductive when we rely on them too heavily.
What You'll Learn
In this episode, I explore:
-
How trying to create more control and accountability can actually undermine ownership and initiative
-
Why relying on data and logic can cause us to dismiss legitimate concerns and human experiences
-
How the desire to keep everyone happy can prevent us from having the difficult conversations that move change forward
-
Why avoiding resistance doesn't make it disappear—and how it can create even bigger problems down the road
-
How our attempts to make ourselves more comfortable when facing resistance can get in the way of what other people actually need
-
How to recognize your Resistobot™ responses and make more intentional choices about how you show up as a change leader
Meet the Four Resistobots™: Commandax, Factron, Softstep, and Shellout
Each of these four Resistobots™ represents a different way we can respond when someone pushes back on a change.
Commandax: The Need to Take Control
Commandax loves structure, systems, accountability, and knowing exactly what's happening. But when resistance shows up, Commandax can respond by tightening the grip: adding more rules, oversight, approvals, and direction.
The problem? The more control we try to create, the less ownership we might actually be building.
Factron: The Need to Be Logical
Factron believes that facts, data, and evidence should speak for themselves. When someone questions a recommendation, Factron's instinct is to bring out another spreadsheet, another analysis, or another chart.
But human concerns aren't always logical problems. Someone can understand your data perfectly well and still have legitimate fears or experiences that haven't been addressed.
Softstep: The Need to Keep Everyone Happy
Softstep values relationships and wants everyone to feel comfortable, included, and supported. But when the desire to avoid disappointing people takes over, we can soften our message, avoid difficult conversations, and make compromises that take us away from what actually needs to happen.
You can care about someone's feelings without making yourself responsible for keeping them happy.
Shellout: The Need to Avoid
Shellout wants to protect us from risk, conflict, and uncomfortable situations. Sometimes that means putting off a difficult conversation, focusing on the people who already support the change, or hoping resistance will eventually go away.
But resistance doesn't usually disappear just because we stop talking about it. Sometimes it simply goes underground.
What Do All Six Resistobots™ Have in Common?
Whether we're fixing, explaining, controlling, proving, pleasing, or avoiding, all six Resistobots™ have something in common: they're ways we try to make ourselves more comfortable when we're experiencing resistance.
And that's where things get interesting.
Our automatic responses might make us feel better in the moment, but that doesn't mean they're creating the outcomes we want.
We might be trying to build ownership but taking control. Trying to build relationships but avoiding the conversations that matter. Or trying to understand a problem while dismissing someone's experience.
The goal isn't to get rid of these strengths. It's to recognize when they're taking over and develop more range and choice in how we respond.
The Big Takeaway
Resistance isn't just an opportunity to understand what's happening with someone else. It's also an opportunity to understand what's happening with you.
When someone pushes back, pay attention to what happens inside you.
What do you immediately want to do? Fix it? Explain it? Take control? Prove your point? Make everyone happy? Avoid the conversation?
Your response gives you valuable information about the strengths you rely on and the insecurities or discomfort that might be hiding underneath.
Becoming a better change leader isn't just about learning more tools and techniques for getting other people to change. It's also about understanding how you show up when change gets hard.
Your Experiment
For the next week, pay attention to what happens when someone resists something you're trying to accomplish.
Instead of immediately focusing on what they're doing, turn your attention inward and ask yourself:
-
Which Resistobot™ is showing up right now?
-
What am I feeling in this moment?
-
What am I trying to accomplish with my response?
-
What might this person actually need from me?
-
What would I do differently if I wasn't trying to make myself more comfortable?
You don't have to change your behavior perfectly. You don't even have to change it at all this week.
Just start noticing.
Because you can't make a different choice if you don't recognize the choice you're making now.
Links
-
Find Your Resistobot™ Quiz: Discover which Resistobot™ responses you tend to default to when you encounter resistance.
-
Credible Heard Used: Explore the program designed to help you uncover your Resistobot patterns and become a more effective change leader.
Transcript
Hey there, and welcome back to Thoughts on Change, where we help human herders like you stop fighting resistance. Over the last several episodes, we've been looking at resistance from a different angle. We started with the idea that people may not actually be resisting the change itself. They may be resisting the future they imagine the change will create. Then we explored what they might be afraid of losing in that future. And more recently, we're turning the lens around. Instead of asking, why are they resisting? We've started asking, how are we as change leaders responding to their resistance? Sometimes without realizing it, our attempts to help can actually make resistance worse, not better. And in the last two episodes, we've explored the resistibots. These are the different patterns of behavior we can fall into when we're uncomfortable, particularly when facing resistance. Last episode, we talked about doctrina. That's the part of us that believes if people just understood what we understand, they'd get on board. And before that, we talked about quickshift. That's the part of us that sees a problem and immediately wants to fix it. Today we're going to wrangle the remaining resistabots, those other four responses that we can have. And these are some interesting ones because they show up in ways that might not look like fighting resistance at all. Sometimes when we encounter resistance, we try to take control. And sometimes we double down on the facts and logic. Sometimes we work really hard to keep everybody happy. And sometimes we just avoid the whole thing altogether. Does that sound familiar? All right, let's meet Command Dax, Factron, Sof Step, and Shellout. Welcome to Thoughts on Change, the podcast about the messy, political, emotional, deeply human side of leading change. I'm Kelly, and I believe anyone can implement lead tools until they actually have to get people to use them. Run here, we talk about how to move culture, how to build credibility, and how to influence without bulldozing. Basically, how to herd humans without losing your mind. Before we dive in, I want to remind us all of something important. The Resistibots aren't labels for other people. They're not ways to categorize the people who are resisting our change. They're patterns in us. They're the ways we tend to respond when we're under pressure, when things aren't going the way we expected, and when someone pushes back on something we believe is important. And here's the thing: every one of these bots has a strength behind it. That's what makes them so tricky. We're not talking about inherently bad behaviors. We're talking about strengths that can become overused, particularly when we're uncomfortable or when we feel vulnerable and insecure. The goal is to recognize when they're taking over and make a more intentional choice about how we respond. Because realistically, we need all of the resistibot strengths. It's just a matter of which one to use when. All right, let's start with command X. Let me paint a picture. You've been working on an improvement initiative. You've got a plan. You've got a timeline. You've got the roles and responsibilities. You've thought through how everything is supposed to work. And then someone starts pushing back. Maybe they aren't following the new process. Maybe they're doing things their own way. Maybe they're questioning decisions that have already been made. And suddenly you find yourself getting a little more directive. You start checking in more frequently. You add another approval step. You clarify the expectations. You create another tracker. You start telling people exactly what needs to happen and when it needs to happen by. And when they still don't do what you expect, you tighten things up even more. Because clearly they need more direction. This is Command X. Command X is the part of us that wants control. Command X likes structure. It likes systems. It likes knowing what's happening, who's doing what, and whether things are going according to plan. And honestly, there's a lot to love about Command X. In continuous improvement, structure is incredibly valuable. We need standards, we need clear expectations, we need accountability, we need systems that help people understand what good looks like and makes it easier to achieve. Command X can help us create stability, consistency, and clarity. The problem isn't that Command X exists. The problem is when our need for control becomes more important than our ability to adapt. Because when someone resists, Command X can interpret that resistance as a sign that we need to exert more control, more direction, more oversight, more rules, more accountability. But here's the question I want you to consider. What if the more control you try to create, the less ownership you're actually creating? Think about what happens when someone feels like every decision is being made for them. They stop thinking for themselves. They stop taking initiative. They start doing exactly what's expected and nothing more. They find ways to work around the system because they don't feel like they have any say in it. And now you've created a situation where you feel like you need even more control because people aren't taking ownership. Do you see the cycle? I think this is a particularly easy trap for those of us in leadership and CI roles. We're often responsible for delivering results. We have commitments, timelines, business objectives. And when things start going sideways, there's a lot of pressure to get things back on track. Control can feel like the fastest way to do that. But here's something worth considering. When someone pushes back or things start to go differently than you planned, what if what they actually need is more involvement, not more direction? What if they need to have some influence over how the change happens? What if they're worried about losing control over their own work? And your response is to take even more control away from them. You might be reinforcing exactly what they're worried about. So the next time you feel that urge to tighten things up, pause and ask yourself, am I creating clarity or am I trying to create control for myself? And those aren't always the same thing. You might also ask, where could I give this person more ownership? What decisions am I holding on to that someone else could make? What structure would help them succeed without requiring me to oversee every move? And what might they be experiencing as a loss of control? Command X doesn't need to disappear. We absolutely need structure and accountability. But we need to make sure we're creating the conditions for people to succeed, not just creating a system that makes us feel more in control. Now, let's talk about Factron. This one is especially interesting for those of us who work in data-driven environments. Imagine you've identified an opportunity for improvement. You've collected the data, you've done the analysis, you've quantified the problem, you've figured out how much time, money, or effort is currently being wasted. And then you've presented all of this to the people who need to support this change. But someone still isn't convinced. They say, I just don't think this is going to work. Or I don't see why we need to do it this way. And you're thinking, but the data! You've got evidence, numbers, facts. How could anyone look at all of this and come to a different conclusion? So you start bringing up more data. You build another spreadsheet, you run another analysis, you show them the numbers from another site, you demonstrate the financial impact because surely if they could just see the facts, they'd understand. Factron is the part of us that relies on logic, facts, and rational thinking. Factron believes that the best way to make a decision is to look at the evidence. And honestly, there's a lot to love about Factron. Data matters, evidence matters. We don't want to make important business decisions based on assumptions or whoever has the loudest voice in the room. In CI, we spend a lot of time teaching people to go see, collect data, understand the problem, and make decisions based on what we actually know. Factron helps us separate facts from opinions. It helps us challenge assumptions. It helps us build credible recommendations. Those are incredibly valuable skills. But here's where Factron can get us into trouble. We can start treating human concerns as if they're simply a logic problem. And humans aren't particularly logical creatures. We like to think we are, we like to believe we make rational decisions based on the information available to us. But our decisions are also influenced by our experiences, emotions, relationships, fears, and what we believe might happen to us in the future. And no amount of data automatically makes those things disappear. Imagine someone is worried about a new production process, right? They're concerned that it will make their job harder. You show them the data demonstrating that the process should reduce overall cycle time. But that doesn't necessarily make them feel any better because they're not worried about the average cycle time. They're worried about what happens when the process breaks down at two in the morning and they're the one who has to figure out how to fix it. Or maybe they're worried that the new process will make them look incompetent while they're learning it. You can have all the data in the world showing that the new process is better. But that doesn't mean you've addressed their concern. And here's another thing. When we rely too heavily on logic, we can accidentally communicate that someone's feelings or experiences aren't valid unless they can prove them with data. Think about how often we hear things like, well, that's just anecdotal. Do you have data to support that? That's not what the numbers are telling us. And sometimes those are perfectly reasonable questions and responses. But sometimes we use them to dismiss information that doesn't fit our expectations. Just because something isn't quantified doesn't mean it isn't real. And just because someone can't articulate their concern in a perfectly logical way doesn't mean there's nothing worth understanding. So here's what I want you to consider, my factrons. When someone challenges your recommendation, are you trying to understand their perspective? Or are you trying to prove that your perspective is the correct one? Because those are two very different things. The data might tell you that a change should improve performance, but the person doing the work might tell you that there's a risk you haven't accounted for. Both pieces of information matter. So instead of immediately reaching for another spreadsheet, try asking, what are you seeing that I'm not? What about this change concerns you? Where do you think our analysis might be missing something? What has your experience taught you about this process? And here's what I really like. What would we need to see to know whether this is actually working? Now you're not using data as an argument, you're using data to learn together. Factron is incredibly useful, but facts should help us understand reality, not become a weapon we use to dismiss someone else's experience. Now, let's move to a bot that I think a lot of people might recognize in themselves. I know I certainly do. Soft step. Imagine you're leading a change initiative, you've got a recommendation that you believe is important, but you know some people aren't going to like it. You know there will be disagreement, you know someone might be disappointed, and you really don't want to create conflict. So you start softening the message. You say things like, this is just an idea, we don't have to do it this way, let's see what everyone thinks. You might even avoid being direct about what needs to change. You might even agree to things that you don't actually think are a good idea. You might even take on extra work to make things easier for everyone else. Or you might keep revisiting decisions because someone isn't happy with the outcome. And before you know it, you've made a whole bunch of compromises that have moved you pretty far away from what you originally believed was important. Because keeping everyone happy has become more important than actually making progress. Hello, soft step. Soft step is the part of us that wants to please people. Soft step values relationships. It wants people to feel comfortable, included, and supported. It doesn't like disappointing people. It doesn't like conflict. And it can be really uncomfortable when someone is upset with us. There's a lot to love about soft step. Relationships matter. Trust matters. We need to understand how our decisions affect other people. We need to be able to collaborate, build connections, and create environments where people feel safe speaking up. Soft step helps us do those things. The problem isn't that soft step exists. The problem is when our desire to maintain relationships gets in the way of having the conversations that actually strengthen those relationships. Here is something I think is particularly important for women in leadership and CI roles. We can sometimes feel a lot of pressure to be liked, to be approachable, to be collaborative, to make sure everyone feels heard. And those are all wonderful qualities. But what happens when we start believing that being a good leader means making sure nobody is ever uncomfortable with us? We might avoid giving difficult feedback. We might hesitate to challenge someone's thinking. We might let someone derail a conversation because we don't want to upset them. We might say yes to requests that we know aren't realistic. We might spend so much energy trying to get everyone on board that we lose sight of what actually needs to happen. Here's the thing. You can care about someone's feelings without making yourself responsible for keeping them happy. Let's hear that one again. You can care about someone's feelings without making yourself responsible for keeping them happy. Sometimes people are going to be disappointed with a decision. Sometimes they're going to disagree with you. Sometimes they're going to be frustrated. And that doesn't automatically mean you've done something wrong. In fact, sometimes the most respectful thing you can do is be honest and direct, even when it's uncomfortable. Because when we avoid the hard conversation, we're often prioritizing our own comfort over the other person's ability to understand what's happening. There's another downside to soft step that I want to explore. When we constantly accommodate other people, we can unintentionally create expectations that everything is negotiable. We say we're committed to a change, but then we keep making exceptions. We establish a standard, but then we allow people to work around it because we don't want to upset anyone. We communicate expectations, but then we don't follow through when someone doesn't meet them. And eventually, people stop taking those expectations seriously. Not because they're bad people, but because our behavior has taught them that the expectations aren't really expectations. And that when we get frustrated that people aren't following through, but we have to take a look at the part we might be playing in that dynamic. So the next time you feel that urge to make someone happy or smooth over a disagreement, ask yourself: am I trying to protect this relationship or am I trying to protect myself from the discomfort this conversation is creating? You might also want to ask, what am I afraid will happen if I disagree? What needs to be said that I'm avoiding? Am I making a commitment I actually believe in? And how can I be both kind and clear? Because those things aren't mutually exclusive. You can be compassionate and still hold a boundary. You can be collaborative and still make a decision. You can care about someone's experience and still ask them to do something difficult. Soft step helps us build relationships, but relationships don't get stronger because we avoid every uncomfortable moment. Sometimes they get stronger because we're willing to have the conversation. And finally, we have shell out. This one might be the sneakiest of all because sometimes we don't even recognize that we're doing it. Imagine you're leading a change initiative and you know there's someone who isn't on board. Maybe they've been vocal about their concerns, maybe they've challenged your recommendation in meetings. Maybe every time you bring up the change, you know you're going to get another round of questions and pushback. And honestly, you're tired. You don't have the energy for another difficult conversation. So you start avoiding it. And then you put off the meeting, you decide to wait until they're in a better mood. You focus on the people who are already supportive. You hope that if you just keep moving forward, this person will eventually come around. Or maybe you tell yourself that the resistance isn't worth addressing right now. And sometimes that might be true. But sometimes you're not making a strategic decision. You're avoiding something uncomfortable. That's shell out. Shell out is the part of us that wants to avoid. It wants to stay away from risk, conflict, and uncomfortable situations. It wants to protect us from the things that might go wrong. And there's a lot to love about shell out. Risk management matters. We shouldn't jump into every situation without thinking. Sometimes we need to slow down, assess the situation, and make sure we're not creating unnecessary problems. Sometimes we need to choose our battles. And sometimes walking away from an unproductive conversation is exactly the right thing to do. The problem isn't that shell-out exists. The problem is when avoiding discomfort becomes more important than addressing what needs to be addressed. Here's something worth thinking about. When we avoid someone who is resisting, what happens to the underlying concern? Does it disappear? Usually not. It just goes underground. Maybe that person stops raising concerns in meetings, but continues doing things the old way. Maybe they stop challenging your ideas but start expressing their frustration to their coworkers. Maybe they quietly wait for the initiative to fail. Or maybe they simply disengage. And now you've got a bigger problem than the one you were trying to avoid. Because you haven't actually addressed the resistance. You've just removed yourself from the conversation. I think this is particularly interesting when we connect it back to the imagined future problem we've been talking about. Remember, someone might be resisting because they're worried about losing something important. Maybe they're worried about losing competence, control, predictability, or their ability to do their job well. And when we avoid talking to them, we miss the opportunity to understand that. We miss the opportunity to discover something important. We might even miss a legitimate risk that could derail the change later. Here's another thing about shell out. It doesn't always look like running away. Sometimes it looks like being really busy. We have other priorities. We have more important things to work on. We'll get to that conversation next week. We'll revisit it after the next milestone.
unknown. We'll wait until we have more information. And sometimes those are legitimate reasons. But sometimes they're just really good excuses. So here's a question I want you to consider. What conversation are you hoping you won't have to have? Maybe it's a conversation with someone who disagrees with you. Maybe it's a conversation with your boss about a decision you don't support. Maybe it's a conversation with a team about expectations that aren't being met. Maybe it's a conversation where you might have to admit that something about your original recommendation isn't working. Whatever it is, there's probably something uncomfortable sitting underneath that avoidance. And the longer you avoid it, the more power it can have over you. So the next time you notice yourself putting off a difficult conversation or task, ask, am I choosing not to engage because it's the right decision or because I'm uncomfortable? You might also ask yourself, what am I afraid might happen if I address this? What's the cost of continuing to avoid this? What information might I be missing by staying away? And what's one small step I could take towards having this conversation? And remember, you don't have to charge into every conflict. You don't have to address everything immediately. But you do need to recognize the difference between intentionally choosing when to engage and automatically avoiding something because it makes you uncomfortable. Shell out can help us manage risk, but it shouldn't be the reason we let important conversations go unspoken. So now we've explored all six resistabots. Quickshift wants to fix, Doctrina wants to explain, Command X wants to control, Factron wants to rely on logic, Soft Step wants to please, and Shellout wants to avoid. And while these behaviors look very different, I think there's something really important they all have in common. They're all ways we try to make ourselves more comfortable when we're experiencing resistance. Think about it. When someone pushes back on our recommendation, it can feel uncomfortable. We might feel frustrated, we might feel questioned, we might feel like we're losing control. We might worry that we're not being effective. We might worry that someone doesn't like us. Or we might simply feel overwhelmed by the amount of effort it's going to take to move things forward. And our resistibots give us a way to respond to that discomfort. We fix, we explain, we control, we prove, we please, we avoid. And here's the tricky part. These responses make us feel better in the moment. Quickshift gives us the satisfaction of taking action. Doctrina gives us the satisfaction of demonstrating our expertise. Command X gives us a sense of control. Factron gives us the reassurance of having evidence on our side. Soft Step helps us avoid disappointing people. And Shellout protects us from those uncomfortable conversations. But just because a behavior makes us feel better doesn't mean it's creating the outcome we actually want. In fact, more often than not, it's doing the opposite. We're so focused on managing our own discomfort that we lose sight of what the other person might actually need from us. And that's where the real opportunity is. I want to be really clear about something. I'm not suggesting that you stop fixing problems or stop explaining things or stop creating structure or using data or stop caring about relationships or stop avoiding every single conflict. Those are all valuable capabilities. The goal isn't to get rid of these behaviors, it's to have more range and choice over what behaviors we use when. Sometimes they need clear direction. Sometimes they need data. Sometimes they need us to prioritize the relationship. And sometimes the best decision is to conversation. The difference is whether we're making that choice intentionally or whether our resistibot is making it for us. And I think that's a really important distinction for anyone who wants to become a more effective change leader. We don't need to become different people. We need to become more aware of the patterns we fall into and develop the ability to choose a different response when the situation calls for it. So, what do we actually do with all of this? Well, this is where I want to bring back something I introduced in an earlier episode. The first step is recognizing what's happening, facing that bot. When you feel that familiar urge to jump in, explain, take control, prove your point, make everyone happy, or avoid the conversation, pause. Don't immediately judge yourself for it. Just notice. You might even give that little voice a name. Oh, there's Quick Shift. Well, hello, Command Axe. Well, Soft Step is having a moment. Sometimes just recognizing the pattern creates enough space for you to make a different choice. And then I want you to get curious. Instead of immediately reacting to the other person's resistance, start asking yourself, what am I experiencing right now? What am I uncomfortable with? What am I trying to make happen? And perhaps most importantly, what might this person actually need from me right now? Maybe they need to be heard. Maybe they need more involvement. Maybe they need clarity. Maybe they need you to address a legitimate concern. Maybe they need a little more time. Or maybe they need you to be direct about an expectation. You won't know unless you get curious. And this is really the heart of the work. It's moving from automatically reacting to resistance to intentionally responding to it. Not because you have to get it right every time, but because you have more choices than you might realize. So here's what I want you to take away from this entire resistabot series. Resistance isn't just an opportunity to understand what's happening with someone else. It's also an opportunity to understand what's happening with you. When someone pushes back, pay attention to what happens inside you. What do you immediately want to do? Your response gives you valuable information. It shows you the strengths you rely on most and the insecurities or discomfort that might be hiding underneath. And when those strengths become automatic, they can actually get in the way of the very thing you're trying to accomplish. You might be trying to build ownership, but taking control. Trying to create understanding, but dismissing someone's experiences. Trying to build relationships, but avoiding the conversations that matter. Or trying to reduce risk, but avoiding the very information that could help you manage it. The goal isn't to stop being who you are. It's to recognize when your strengths are working against you and learn how to use them more intentionally. Because ultimately, becoming a better change leader isn't just about learning more tools, techniques, and frameworks for getting other people to change. It's also about understanding how you show up when change gets hard. And that might be some of the most important work you ever do. So here's what I want you to try over the next week. Pay attention to what happens when someone resists something you're trying to accomplish. And instead of immediately focusing on what they're doing, turn your attention inward. Ask yourself which resistabot is showing up right now? What am I feeling in this moment? What am I trying to accomplish with my response? What might this person actually need from me? And finally, what would I do differently if I wasn't trying to make myself more comfortable? You don't have to change your behavior perfectly. You don't even have to change it at all this week. Just start noticing. Because you can't make a different choice if you don't recognize the choice you're making now. And that awareness is where the real transformation begins. So that wraps up our series on the Resistibots. We've explored all six patterns and how the ways we respond to resistance can sometimes create even more resistance. If you're curious about which ResistaBots you tend to default to, I've got a free Find My Resistibot quiz that you can take here. I'll also put a link in the show notes. And if you've recognized some of these patterns in yourself and want to explore how they're affecting your success as a change leader or your teams, I run a program called Credible Heard Used that is focused on helping you uncover your bot and learning the best techniques for you to shift your approach so you can stop fighting people's resistance and start becoming the real change influencer you want to be. You can sign up on my website here, and also there will be a link in the show notes. And if you are interested in a more intimate session for you and your team, please email me as I am scheduling those as well. Here's what I really want you to remember: you don't have to fight resistance. You don't have to convince everyone. And you certainly don't have to become someone you're not to be an effective change leader. You just need to understand what's happening, both in the people you're trying to help and in yourself. Thanks for listening to Thoughts on Change. And until next time, let's get back to hurting those humans. That's a wrap for this episode of Thoughts on Change. If you're also out there trying to move culture instead of just installing tools, hit subscribe and share this with a fellow CI warrior. And remember, progress beats perfection, curiosity beats control, and culture beats everything. See you next time.