top of page

Episode 22 - Why Explaining More Can Make Resistance Worse

Have you ever spent weeks analyzing a process, building the business case, and putting together the data to support a change—only to have someone tell you they don't think it will work?

​

So you explain the data again. You walk them through the business case. You add another example, another chart, and a few more slides.

​

And somehow…they're still not convinced.

​

Sound familiar?

​

In this episode of Thoughts on Change, we're exploring Doctrina, one of the Resistobots™ that can get in the way of our effectiveness as change leaders.

Sometimes, our expertise and ability to explain why a change makes sense can actually make resistance worse.

​

What You'll Learn

In this episode, I explore:

  • Why being an expert in Continuous Improvement can make it harder to recognize when someone else's concerns aren't a knowledge problem

  • How explaining more can become a way to avoid listening to uncomfortable feedback

  • Why you can be right about a proposed change and still be wrong about what someone needs from you

  • How the future someone imagines can be very different from the future you're trying to create

  • Simple questions you can ask to understand resistance before jumping into explanation mode

​

Meet Doctrina: The Resistobot™ That Wants Everyone to Understand

Doctrina is the part of us that wants to teach, explain, and convince.

​

Doctrina believes that if people just had the right information, they'd see things differently. So when someone pushes back, our instinct is to explain the business case, share more data, and help them connect the dots.

​

And there's a lot to love about Doctrina. Sharing knowledge, making the invisible visible, and helping people understand why a change matters are valuable skills.

But when Doctrina takes over, we can start assuming that a lack of understanding is the reason someone isn't on board.

​

Sometimes it is. But sometimes, something else is going on entirely.

​

The Expertise Trap: When Your Knowledge Gets in the Way

As change practitioners, we spend years learning to identify waste, analyze processes, solve problems, and improve performance.

​

We develop expertise. We learn what good looks like. And we get pretty good at explaining why a particular approach makes sense.

​

But that expertise can make it difficult to recognize when someone else's concern isn't actually a knowledge problem.

​

Maybe they understand the business case perfectly well but are worried about what happens when the new process breaks down. Maybe they're concerned about losing flexibility, being judged on their performance, or having to make another improvement initiative work without adequate support.

​

You can explain the business case beautifully and still fail to address the thing they're worried about.

​

And the more you explain, the more you may reinforce their belief that you aren't listening.

​

When Explaining Becomes a Way to Avoid Listening

Have you ever found yourself in a conversation where you keep explaining why you're right, while the other person keeps pushing back?

​

Before you know it, you're debating details instead of understanding each other.

 

In this episode, I share a personal story about how my own Doctrina response showed up when I asked my husband to do something differently. I kept explaining why my request made sense, convinced that if he just understood my reasoning, he'd agree.

​

But I was avoiding an uncomfortable possibility: maybe he didn't like how I was approaching the situation. Maybe my way wasn't actually the best way.

It's surprisingly easy for our desire to help to get tangled up with our desire to be seen as competent and credible.

​

When that happens, we can start treating every objection as something to overcome instead of something to understand.

​

Being Right Isn't the Same as Creating Understanding

You can be right about the change and still be wrong about what someone needs from you.

​

The data can be right. The analysis can be right. The proposed process can even be better than the current one.

​

But understanding why a change makes sense isn't the same as feeling ready, willing, or able to make that change.

​

Someone can agree that a new process will reduce waste and still worry about meeting production targets while learning it. They can recognize that a new standard is better and still be concerned that it doesn't account for the realities of their daily work.

​

If what someone needs is to be heard, have a risk addressed, or gain some control over how the change happens, more information might not help.

​

The challenge is figuring out what kind of help is actually needed.

​

Back to the Future They're Imagining

Remember the idea we've explored in previous episodes: people may not be resisting the change itself. They may be resisting the future they imagine the change will create.

​

You might see a process that eliminates waste. They might see a process that makes it harder to get their job done when something unexpected happens.

You might see greater accountability. They might see a system that makes their mistakes more visible.

​

You might see a better standard. They might see another requirement they'll be expected to follow without additional support.

​

You're explaining the future you want to create while they're worried about a very different future.

​

Until you understand what they're concerned about, you may spend the entire conversation trying to convince them that your future is better—without addressing what makes theirs feel risky.

​

What If You Asked Instead?

The goal isn't to stop explaining or sharing your expertise. It's to stop treating explanation as your only tool for responding to resistance.

​

The next time someone pushes back on a change and you feel the urge to explain why it makes sense, try pausing and asking:

  • “What concerns you most about this change?”

  • “What do you think is going to happen when we implement this?”

  • “What part of this doesn't make sense to you?”

  • “What am I missing?”

  • “Can you walk me through how you see this affecting your work?”

  • “What would you need to see or understand to feel more confident about this?”

 

These questions shift the conversation from a presentation into an exchange.

You might discover a misunderstanding you can clear up. You might uncover a legitimate risk you need to address. Or you might learn that the person has a concern you hadn't considered at all.

​

The point is to choose your response based on what's actually happening, rather than automatically reaching for the tool you're most comfortable using.

​

The Big Takeaway

Your expertise can be incredibly valuable. But when explaining becomes your automatic response to resistance, you can accidentally make it harder for people to hear you.

​

You might mistake a legitimate concern for a lack of understanding, talk past the future someone is worried about, turn a conversation into a debate, or miss information that could help you implement the change successfully.

​

The next time someone pushes back, pause before you explain.

​

Ask yourself:

“Am I trying to help this person understand, or am I trying to get this person to agree with me?”

​

You might still need to explain. But you might discover that the conversation needs something else first.

​

And that something else could be the difference between someone who feels like you're trying to convince them and someone who feels like you're actually working with them.

​

Your Experiment

For the next week, pay attention to the moments when you feel the urge to explain why something makes sense—especially when someone disagrees with you, questions your recommendation, or expresses concern about a change.

 

You don't have to change your behavior right away. Just notice.

​

Write down:

  • What did the other person say?

  • What did I immediately want to explain?

  • What was I assuming they didn't understand?

  • What might they actually have been concerned about?

  • What could I have learned if I had asked a question before explaining?

 

You don't need to get it right every time. The goal is to start recognizing when Doctrina is taking over, so you have more choice about what you do next.

 

Links

  • Find Your Resistobot™ Quiz: Discover which Resistobot™ responses you tend to default to when you encounter resistance.

  • Doctrina: Learn more about the Resistobot™ that wants to teach, explain, and convince.

  • Video

​

Transcript

Hi, and welcome back to Thoughts on Change, the podcast where we make change make sense. If you've been listening to the last few episodes, we've been talking about resistance from a slightly 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. Or as I'm calling it, the imagined future problem. Then we dug into what they might be afraid of losing in that future. And more recently, we turned the lens around. Instead of asking, why are they resisting? We started asking, how am I responding to their resistance? Because sometimes, without realizing it, our attempts to help can actually make resistance worse, not better. In the last episode, we talked about quick shift. That's the part of us that sees a problem and immediately wants to fix it. Someone has a problem, we have a solution. Someone isn't convinced, we have another solution. And if they still aren't convinced, well, clearly we just haven't found the right solution yet. Today we're going to look at another response that can sneak up on us. Especially those of us who work in continuous improvement, operational excellence, lean, or change leadership. This time, we're not necessarily trying to fix the problem. We're trying to explain it. We're trying to help people understand why the change makes sense, why the data supports it, why the business needs it, why the process is better this way, how it will work, the principles behind it. And if they don't seem to get it, let me explain some more. Because surely, if they just understood what we understand, they'd get on board, right? Well, maybe. But what happens when our need to explain becomes more important than our need to understand? What happens when we shift from being a teacher to being a preacher? Today we're talking about Doctrina. 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. 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. Let me paint a picture. You've spent weeks, maybe months, working on a specific change initiative. You've done the analysis, you've collected the data, you've mapped the process, you've identified the waste, you've talked through the business case. You've probably got a beautiful presentation with charts, graphs, and enough evidence to make your case several times over. You know why this change is necessary. You know what problem it solves, and you know why the new way is better than the old way. Then you bring it to the people who actually have to work with the new process and make the change a reality. And someone says, I don't think this is going to work. Or, we've tried something like this before. Or, I don't understand why we need to change this in the first place. And you think, okay, maybe I haven't explained this clearly enough. So you walk them through the data again. You explain the business problem, you show them the current state and the future state. You point out the inefficiencies, you explain the benefits, you answer their questions. And when they still aren't convinced, you add a few more slides. Maybe you bring in another example. Maybe you show them what another site has accomplished or another area. Maybe you explain the financial impact one more time. Because surely if you can just help them see what you see, they'll understand. And once they understand, they'll agree. And once they agree, they'll support the change. Except sometimes they don't. Sometimes they get quieter. Sometimes they start arguing with you about the details. Sometimes they nod politely in the meeting and then go right back to doing things the old way. And sometimes, the more you explain, the more determined they seem to become to prove you wrong. Which is incredibly frustrating. Because you're not trying to make their lives harder. You're trying to make things better. So what's going on? Let's meet Doctrina. If you've been following along with the Resistibots, you know these aren't labels for other people. They're patterns in us. They're the ways we tend to respond when we're under pressure, particularly when we encounter resistance. And Doctrina is the part of us that wants to teach, explain, and convince. Doctrina believes that if people just had the right information, they'd see things differently. Doctrina thinks they don't understand why this matters. They haven't seen the data and connected the dots. They don't know what I know. If I can just explain it better, they'll get it. And honestly, there's a lot to love about Doctrina. In change management, knowledge matters. Understanding the problem matters. Being able to explain the business case matters. We need to help people see connections they might not have noticed. We need to make the invisible visible. We need to explain why we're doing something differently and what we're trying to accomplish. And doctrina helps us share knowledge, build understanding, and make a case for change. Those are valuable things. The problem isn't that doctrina exists. The problem is when doctrina assumes that a lack of understanding is the real reason someone isn't on board. Because sometimes it is. But sometimes something else is going on entirely. And when we automatically respond to resistance by explaining more, we can end up talking right past the person we're trying to help. I think this is particularly a particularly easy trap to fall into when you've developed real expertise in something. You've spent years learning how to identify waste, analyze processes, solve problems, and improve performance. And you can look at a situation and see things that other people don't see. You understand the principles behind the tools. You know what good looks like. You may even have seen the same problem play out dozens of times. And when someone challenges a change you've worked hard to develop, you naturally want to help them understand why you've made the decisions you have. After all, you have reasons. You aren't just making things up as you go along. You've thought this through. You've done the work. And you want people to understand that. But here's where Doctorina can get us into trouble. Our expertise can make it difficult to recognize when someone else's concern isn't actually a knowledge problem. Maybe they understand the process perfectly well. Maybe they understand the business case. Maybe they even agree that the new process is more efficient, but they're worried about what happens when the new process breaks down. Maybe the old process gave them flexibility, they're afraid of losing. Or maybe they've been through three other improvement initiatives that looked great on paper, but created more work for them on the floor in reality. And maybe they're concerned that the new standard will be used to judge their performance. Or maybe they simply just don't trust that the people implementing this change understand what their day-to-day work actually looks like. You can explain the business case beautifully. You can show them all the data in the world. And none of that necessarily addresses the thing they're worried about. The problem isn't that they don't understand your reasoning or the why. The problem is that your reasoning doesn't resolve their concern. And if you keep explaining, you may actually reinforce their belief that you aren't listening. Here's something worth considering. Imagine you are sharing the information about an upcoming change and someone raises a concern about it. You explain why the change makes sense and they raise another concern. You explain that one too, and they push back on a detail. You provide more evidence, and they tell you that something similar failed in the past. You explain why this time will be different. And before you know it, the entire conversation has become a debate. You're presenting your case, they're presenting theirs, you're trying to convince them, they're trying to convince you. And neither of you is getting much closer to understanding the other or to a path forward. Now, from your perspective, you're being helpful. You're answering their questions and providing information, you're giving them the opportunity to understand the reasoning behind the change. But here's a question I want you to consider. What if explaining is helping you avoid something uncomfortable? What if it's easier to explain why you're right than to sit with the possibility that someone has a legitimate concern you haven't considered? What if it's easier to give someone more information than to ask a question you don't know the answer to? Or what if when someone challenges your recommendation, you experience that challenge as a challenge to your competence? You know your stuff, you've worked hard to develop that expertise, and now someone is questioning your recommendation. So you start explaining. Not necessarily because they need more information, but because you want them to recognize that you know what you're talking about. I've personally experienced how easy it is for our desire to help to get tangled up with our desire to be seen as competent and credible. And when that happens, we can start treating every objection as something we need to overcome instead of something we need to understand. I remember asking my husband to do something differently, and he pushed back. So I explained why I was asking him to do this, what it would do for me, what it would do for him, what it would make easier in the long run for all of us. And he still pushed back. I was so frustrated. As you can maybe imagine, this led to a fight. And looking back on it now, Doctrina was definitely at the wheel. I just kept thinking, if he'd only understand, he would do it. But I failed to allow myself to see the uncomfortable truth. That I was avoiding hearing that he didn't like how I was doing this thing I was asking him to change. That maybe my way wasn't actually the best way. So let's talk about another piece that I think is especially important for those of us in CI. We can be right about the change and still be wrong about what someone needs from us. Let me say that again. We can be right about the change and still be wrong about what someone needs from us. The data can be right, the analysis can be right, the business case can be right. Heck, the proposed process can even be better than the current one. Being right about the solution doesn't mean we automatically understand the person who's going to have to live with it and what it will take to actually make the change successful. Having the right answer doesn't mean we know what will help someone move forward. This is where I think we need to separate two things that we often treat as the same. Understanding why a change makes sense is not the same as feeling ready, willing, or able to make that change. Someone can understand that a new process should reduce waste and still be worried about whether they'll be able to meet their production targets while learning it. They can agree that a new system will improve visibility and still be concerned about who will use that visibility to judge them. They can recognize that a new standard is better and still be frustrated that the people who designed it haven't accounted for a problem they encounter every day. More information might help with some of those concerns, but it won't necessarily address all of them. And if we keep providing information when what someone needs is to be heard, to have a risk addressed, or to have some control over how the change happens, we're going to miss the mark. We might even make things worse. Because the message they receive wouldn't necessarily be Kelly is giving me some useful information. It could be Kelly has already decided what I should think and she's going to keep talking until I agree. And that is not exactly a recipe for building trust. So let's connect this to what we've been talking about in the previous episodes. Remember that idea that people may not be resisting the change itself. They might be resisting the future that they imagine the change will create. And remember that the future they're imagining might include losing something important to them. Maybe it's control, maybe it's competence, maybe it's predictability, maybe it's the ability to do their job well without having to fight the system all day. Now, imagine that someone is worried about one of those things. They tell you they're not convinced the new process will work. And you respond with a presentation about how much more efficient the process will be. You're explaining the future you want to create, but they may be worried about a very different future. You see a process that will eliminate waste. They see a process that will make it harder to get their job done when something unexpected happens. You see a system that will create greater accountability. They see a system that will make their mistakes more visible. You see a standard that will make the work easier. They see another requirement they're going to be expected to follow without getting any additional support. And neither of you may realize that you're talking about two completely different futures. This is why I think it's so important to be curious about what someone is actually concerned with before we launch into our explanation. Because if we don't understand the future they're imagining, we may spend the entire conversation trying to convince them that our future is better. Without ever addressing what makes their future feel risky. Now, of course, there are situations where people really don't understand. Sometimes they haven't seen the data, sometimes they don't understand the problem we're trying to solve. Sometimes they have incorrect or incomplete information. And sometimes we haven't done a good job explaining what we're trying to accomplish. And of course, yes, sometimes the right thing to do is explain. I'm not suggesting we stop sharing our knowledge or making the case for change. The question is whether we're choosing to explain because that's what the situation calls for, or because explaining is our automatic response whenever someone disagrees with us. And those are very two different things. And the way to tell the difference is to get curious. Instead of assuming that a lack of understanding is the problem, try finding out what the person actually understands and what they're concerned about. And you might discover that they have a genuine misunderstanding that you can clear up. Great. You might discover that they understand the change perfectly well, but have identified a legitimate risk that you need to address. Also great. And you might discover that they have a completely different concern that you hadn't even considered. That can be uncomfortable, but it's useful information. And you might discover that they aren't ready to agree with you yet. That's useful information too. The goal isn't to avoid explaining, it's to stop treating explanation as the only tool we have for responding to resistance. So what does this look like? Well, the next time someone pushes back on a change and you feel that urge to explain why it makes sense, try pausing before you launch into your reasoning. Instead of immediately responding with, let me explain why we're doing this, try asking what concerns you most about this change. Or what do you think is going to happen when we implement this? Or what part of this doesn't make sense to you? And here's one I particularly like. What am I missing? That last question can be surprisingly powerful because it communicates that you aren't assuming you have the whole picture. You're open to the possibility that there's something you haven't considered. And sometimes that's exactly what you need to discover. Now you can also try, can you walk me through how you see this effect in your work? Or what would you need to see or understand to feel more confident about this? And notice what all of these questions do. They change the conversation from a presentation into an exchange. You're no longer just trying to get information into someone's head. You're trying to understand what's already there. And once you understand that, you can make a much better decision about what kind of help is actually needed. Maybe you do need to explain the business case. Maybe you need to demonstrate the new process. Maybe you need to address a legitimate concern. Maybe you need to change something about the proposed solution. Or maybe you simply need to listen for a while without trying to convince anyone of anything. The point is that you get to choose your response based on what's actually happening rather than automatically reaching for the tool you're most comfortable using. I'm not asking you to become less knowledgeable. I'm not asking you to stop advocating for good ideas. And I'm definitely not suggesting that every decision needs to become a consensus-building exercise where we keep talking until everyone agrees. Sometimes we need to make decisions. Sometimes we need to explain the rationale. Sometimes we need to be clear about what's changing and what isn't negotiable. But even when a decision is already made, understanding someone's concerns can help us implement that decision more effectively. You don't have to agree with every concern someone raises to take it seriously. You don't have to change your recommendation every time someone disagrees with you. You. And you don't have to pretend you don't know something when you do. What you can do is create a little space between hearing resistance and trying to overcome it. Notice that urge to explain. Notice when you start building your argument before the other person has finished talking. Notice when you're preparing your next piece of evidence instead of listening to what they're actually saying. And ask yourself Am I trying to help this person understand? Or am I trying to get this person to agree with me? These are not the same thing. Helping someone understand means being willing to discover what they think, what they know, and what they're concerned about. Trying to get someone to agree means starting with a conclusion you want them to reach and working backward from there. One creates space for a conversation. The other can turn the conversation into a battle. And if you've been listening to this podcast for a while, you know that fighting resistance isn't the right battle. So here's what I want you to take away from this episode. Your expertise can be incredibly valuable. But when explaining becomes your automatic response to resistance, you can accidentally make it harder for people to hear you. You might mistake a legitimate concern for a lack of understanding. You might talk past the future someone is worried about. You might turn a conversation into a debate. You might make people feel like their concerns aren't being heard. And you might miss important information that could help you implement the change successfully. Doctrina isn't bad. Doctrina helps us share knowledge, explain ideas, and make a compelling case for change. But when Doctrina takes over, we can become so focused on making people understand our reasoning that we forget to understand theirs. So the next time someone pushes back on a change, pause before you explain. Ask yourself, what am I assuming they don't understand? And then ask, what could I learn if I stopped explaining long enough to ask a question? You might still need to explain, but you might discover that the conversation needs something else first. And that something else could be the difference between a person who feels like you're trying to convince them and a person who feels like you're actually working with them. So here's what I want you to try over the next week. Pay attention to the moments when you feel that urge to explain why something makes sense. Especially when someone disagrees with you or questions your recommendation or expresses concern about a change. You don't have to change your behavior right away. Just notice. And when you notice, write down what was the other person saying? What did you immediately want to explain? What were you assuming they didn't understand? And what might they actually have been concerned about? And here's the question I really want you to consider. What could you have learned if you had asked a question before explaining? We don't need to get it right every time. The goal is simply to start recognizing when Doctrina is taking over so we could have more choice about what we do next. Thanks for listening to Thoughts on Change. Next time we'll round up the remaining Resistibots. And so if you're interested in learning more about them or learning which bots you tend to default to, you can take a free Find My Resistibot quiz link in the show notes. And feel free to reach out if you want to have a chat about your bots and how they're affecting your success or the success of your team. All right, that's it for today. 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.

bottom of page