How Do You Lead a Team That Doesn't Want to Improve?

I've been working with leaders for forty years. The most common version of this problem doesn't look dramatic. The team shows up. The work gets done. Reviews are acceptable. But the manager knows — and the team knows — that something real has stopped happening. Nobody's improving. Nobody's pushing. The meetings have a particular quality, the kind where everyone nods and nothing moves. If you're in that situation, you've probably already tried the obvious things. This is about what's actually going on underneath them.

Resistance Isn't What You Think It Is

Here's what I've noticed over four decades of working with leaders: the moment a manager labels their team "resistant," they've already made a mistake. Not a malicious one. An understandable one. But a mistake that locks them into a frame that makes the actual problem invisible.

Resistance is not a personality trait. It's not laziness dressed up in sophisticated clothing. It's almost always a response — a completely rational response, from the team's perspective — to something in the environment. The question worth asking isn't "why won't they improve?" It's "what are they protecting themselves from?"

I've worked with biotech teams in Camarillo where the apparent resistance was actually a collective memory of an initiative two years earlier that went nowhere, cost three people extra weekend hours, and ended without acknowledgment. When the next initiative arrived, the team's skepticism wasn't irrational. It was learned. They weren't refusing to improve. They were refusing to invest in something they'd been burned by before, under a leadership structure that never admitted what happened.

At NBVC and in defense contracting environments around Port Hueneme, I've seen a different pattern: teams where improvement means admitting the current way is wrong, and admitting the current way is wrong feels like criticizing the people who built it — including sometimes the person asking for the change. That's not stubbornness. That's loyalty operating in the wrong direction, and a leader who doesn't understand that distinction will spend months pushing against a wall that would open from the other side.

There's also identity protection. A team member who has been the expert for seven years does not experience "let's try a new approach" as an opportunity. They experience it as a threat to the thing that makes them valuable. If they learn the new way, are they conceding that the old way was inferior? Are they erasing the decade they spent mastering it? These aren't conscious questions. They're running underneath the surface, producing what looks from the outside like foot-dragging and excuses.

The leaders who get this — who understand that resistance is information rather than obstruction — stop trying to overcome it. They start getting curious about it. That shift, from pushing to understanding, is where the actual movement begins.

Why Most Managers Make It Worse Without Knowing It

Enthusiasm is one of the most underrated sources of team resistance I've seen. A new leader comes in — or an existing leader gets a new idea — and leads with energy. This is a great opportunity. Things are going to be different. We're going to grow. The team, hearing this, does not think: wonderful, I'm excited. The team thinks: here we go again.

The problem with leading with enthusiasm before trust is established is that it reads as pressure. And pressure, in people who've already made a calculation that improvement isn't safe, produces the opposite of the intended effect. They get quieter. More compliant on the surface. More resistant underneath.

Then there's the leader who treats skepticism as disloyalty. Someone on the team raises a concern — a legitimate concern, the kind of concern that would actually improve the initiative if taken seriously — and the leader, consciously or not, receives it as an attack. The response, even if it's verbal agreement, carries a charge. The skeptic notices. They stop raising concerns. And now the leader has no signal at all, which they mistake for buy-in.

Performance reviews as coercion deserve their own paragraph. I've sat with managers who genuinely believe that linking improvement to annual reviews creates motivation. In some contexts, for some people, there's a sliver of truth to that. More often, it creates compliance theater. The person performs the behaviors required to get a satisfactory review. The internal relationship to the work doesn't change. The moment the review pressure lifts, the behavior reverts. The manager has not created improvement. They've created a performance of improvement, which is considerably more expensive to sustain.

The "just be positive" leader is worth naming directly. This is the manager who believes that modeling positivity creates positivity — that if they project enough confidence and enthusiasm, it will spread. What actually spreads is inauthenticity. Teams are remarkably good at detecting the gap between what a leader says and what a leader actually believes. When they detect that gap, they stop trusting anything that comes out of it.

The Three Types of Resistance (and Why They Need Different Responses)

• The burned-out complier. Shows up, does the work, nods in meetings, volunteers nothing extra. Not angry, not vocal — just empty. This person gave more than they had for too long and learned that the extra was never noticed or reciprocated. They're not refusing to improve. They're protecting what's left. Pushing harder makes this worse. The only thing that moves this person is genuine recognition followed by a real reduction in unnecessary demands.
• The low-trust skeptic. Has a specific reason, usually historical, to doubt that this initiative will go anywhere. They've seen it before. They'll wait to see if this time is actually different before investing. They're not resistant to improvement — they're resistant to wasted effort. The response is not persuasion. It's demonstrating, through small actions, that this time the follow-through is real.
• The genuinely misaligned. This person's values, working style, or professional goals don't match the direction the team is heading. This is the hardest situation because improvement, for this person, might mean becoming someone they don't want to be. No amount of motivation or incentive resolves genuine misalignment. This is a placement problem, and it often requires a harder conversation than most managers are willing to have.
• The identity-protector. Has built their professional identity around a specific expertise or way of working. Being asked to change that feels like being asked to acknowledge that what they've been doing was wrong. The response that works is framing growth as addition, not replacement — and being genuinely patient, not performatively patient.
• The waiting-to-be-proven-wrong skeptic. Doesn't believe the change will work, but isn't emotionally invested in being right. They're open, in principle, but they need evidence before they invest. These are often your best eventual allies if you earn it. They respond to results, not vision.

What Doesn't Work — and Why Leaders Keep Trying It Anyway

Off-sites have a particular hold on corporate culture that I've never fully understood, given their consistent failure rate. The logic seems to be: if we take the team out of the environment where the problem lives, into a hotel in Santa Barbara or a retreat center in Ojai, the problem won't follow. It always follows. You've just moved it somewhere with better catering.

What off-sites do accomplish is a temporary disruption of routine that can produce genuine connection, and occasionally genuine insight. But unless what gets surfaced in that environment is integrated into actual structural and relational changes back in the office, by the third week post-off-site you're looking at the same team with a shared memory of a nice weekend. The resistance is back, and now the team has also learned that the off-site is the organization's preferred way of not dealing with real problems.

Culture decks and values workshops are a related category. I've watched leadership teams spend weeks crafting value statements — Integrity, Excellence, Collaboration — and then present them to teams who recognize immediately that the stated values don't match the actual decision-making they observe daily. The gap between espoused and enacted values doesn't build culture. It destroys trust. And a team that doesn't trust the values document will not be moved by a better values document.

Incentive structures address a different problem than the one most resistant teams have. If the resistance is about effort — people capable of more, choosing to do less because the reward structure doesn't justify more — then incentives make sense. But most of the resistant teams I've worked with are not in an effort problem. They're in a safety problem, or a trust problem, or a meaning problem. Adding a bonus to a situation where people feel unseen or burned doesn't fix the unseen or burned part. It adds a transaction to a relationship that's already transactional in the wrong direction.

What Changes When You Lead From the Inside Out

In my experience, the most common unexamined thought a struggling manager carries is some version of: "If my team isn't improving, I'm failing as a leader." Reasonable enough on the surface. But follow that thought downstream and you get a leader who experiences every sign of stagnation as a personal indictment, who approaches team conversations with a low-grade urgency that the team can sense but can't name, who over-explains the importance of improvement in ways that feel less like inspiration and more like pressure.

The team, picking up on this, responds the way teams usually respond to unspoken pressure: they get careful. Careful means minimal. Careful means don't volunteer anything that might make this worse. Careful means do your job and go home.

When a leader starts seeing that thought as a thought — not as a fact about their situation, but as a story they're carrying and acting from — something changes in how they show up. Not because they work harder at appearing calm. Not because they perform anything. Because they stop being run by the thought. And when the urgency leaves them, the team's defensiveness has less to press against. I've watched this happen enough times that I no longer find it surprising: the leader changes something internal, and within weeks the team dynamic shifts — not because anyone announced anything, but because something real changed and teams feel the difference between performance and reality.

This is the part of leadership that most executive training skips over entirely. There's a reason: it's harder to put in a slide deck than "here are five communication techniques." But the internal environment a leader creates — the felt sense their team has of whether this person is operating from fear or from clarity, from ego or from genuine interest — is the single most powerful variable in how a team performs. You can optimize every external structure and still have a team that won't move, if the leader's internal state is producing the wrong signal.

I see this consistently in the Amgen and biotech context around Thousand Oaks and Camarillo. Scientists promoted into leadership positions are brilliant at solving technical problems. Many of them approach human problems the same way — identify the variable, control for it, optimize the output. When the variable is a person's resistance, that approach produces the opposite of what they want. The team isn't a variable. They're people responding to a relationship. And the relationship starts with what the leader is carrying, not what the leader is saying.

Five Shifts That Actually Move Resistant Teams

1. Stop explaining and start asking. Most leaders in this situation talk more than they listen. They explain the vision, the rationale, the importance of improvement. The team hears: you need to convince us. Try instead: "What would need to be true for this to feel worth your time?" Then actually listen. Not to respond — to understand. The question itself signals that you're willing to hear something inconvenient, which is the first real signal of safety most resistant teams haven't received.

2. Find the one person who isn't resistant and work with them visibly. Not to create social pressure on the others — that backfires quickly. But because movement is contagious in ways that persuasion isn't. When one person on the team has a genuine positive experience with the new approach, and when that experience is visible to others, the calculation changes. Not for everyone. But for the waiting-to-be-proven-wrong skeptics, it's evidence that actually matters.

3. Name the history before the team does. If there was a failed initiative, name it. If there was a broken promise, name it. Don't wait for someone else to bring it into the room as ammunition. When a leader names the past accurately and without defensiveness, it removes the past as a weapon and adds it to the shared context. "We tried something like this eighteen months ago and it didn't go the way anyone hoped. I want to talk about why, because I think it matters for what we're doing now." That sentence does more for trust than three off-sites.

4. Make improvement smaller than the resistance. Asking a resistant team to commit to transformation creates the exact psychological experience that produces more resistance. Ask for something small. Something so small it doesn't trigger the self-protective response. One change. One meeting. One experiment with a real end date. Micro-commitments build a track record of follow-through — on both sides — that macro-visions can't.

5. Address your own thought patterns first. This is the one most leaders skip and the one that matters most. What story are you carrying about this team? "They don't care." "They're lazy." "They're threatened by change." Whatever the story is, it's in the room. Teams don't hear words. They hear the whole person. Get clear on what you're actually thinking, and whether that thinking is producing the leadership you want to show up with.

When the Problem Isn't the Team

I've spent most of this piece on what leaders can do differently. But there's a harder conversation underneath all of it, and I'd rather say it directly than leave you with the impression that every resistant team can be turned with the right approach.

Sometimes the organization created the resistance and has no intention of changing the conditions that created it. A leadership team that talks about growth while consistently punishing the people who try new things. A culture that says it values innovation and rewards compliance. An environment where the people who volunteer are the people who get the most work added to their plate. If that's the environment your team is operating in, their resistance is correct. They've made an accurate assessment of their situation.

Sometimes the misalignment is real and fundamental. Someone on the team has different values, different goals, or a different professional identity than the direction requires. The kind thing — genuinely the kind thing — is to name that honestly and help them find a better fit, rather than spending eighteen months trying to change someone into a person they don't want to be.

And sometimes the leader is the problem in ways that go beyond thought patterns. A pattern of broken commitments. A specific interpersonal dynamic with one team member that poisons the whole. A decision that was made poorly and never acknowledged. These don't get fixed by leading from the inside out. They get fixed by being honest about what happened and making a genuine repair.

The question worth sitting with: is this a team problem, a leader problem, or an organizational problem? The answer determines what's actually available to you.