You’ve Navigated Change Before. Here’s Why This Time Feels Different

Picture this: you're sitting in a leadership team meeting, and the situation in front of you feels familiar. Not identical to something you've seen before, but close enough. Your brain is already ahead of the conversation, quietly pulling up case files — the reorg you navigated three years ago, the team friction you resolved before that, the market shift you steered through. You've done this. You know what this looks like.

And then something doesn't land. The approach that worked before doesn't move the needle. The team seems vaguely disengaged. You try harder and get roughly the same result. There's a low hum of frustration that you can't quite name.

That feeling is worth paying attention to. It might not mean you're doing something wrong. It might mean the kind of problem in front of you has changed and the playbook, however excellent, was written for a different game.

First, Let's Acknowledge What Experience Actually Does

Experience is not overrated. Years of navigating ambiguity, managing people through disruption, and making decisions with incomplete information builds something real — a calibrated judgment that can’t be shortcut. Pattern recognition, emotional steadiness, the instinct to know which fires actually need fighting. These things matter enormously.

The issue isn't experience itself. It's the assumption, usually unconscious, that because you've handled disruption before, you understand the disruption in front of you. That assumption is worth examining.

Two Kinds of Hard: The Distinction That Changes Everything

Leadership researchers Ronald Heifetz and Marty Linsky drew a line that most leadership frameworks skip right over. They distinguished between two fundamentally different types of challenges: technical and adaptive.

Technical challenges are complex, sometimes genuinely difficult, but they're solvable with existing knowledge and expertise. There's a right answer, and the right people with the right tools can find it. Think restructuring a workflow, implementing a new system, or managing a budget shortfall. Hard? Yes. But the kind of hard that experience was built for.

Adaptive challenges are different in kind, not just degree. They require people to change their behavior, beliefs, or values — not just apply better techniques. The problem isn't fully defined yet. There's no expert with the answer. The "solution" usually involves some loss, some letting go of what worked before. Think culture transformation, building trust after a fracture, or leading people through a change that no one really wanted.

These two types of challenges can look nearly identical from the outside. The same symptoms — team resistance, stalled progress, recurring conflict — can signal either a technical problem that needs a better solution or an adaptive challenge that needs a fundamentally different approach.

When you apply a technical fix to an adaptive challenge, you don't just fail to solve it — you can deepen it. The team gets better processes, but the underlying dynamic doesn't shift. The reorg happens, but the culture problem migrates to the new structure. And experienced leaders, whose pattern recognition is well-developed and fast, are often the last to notice the misread.

Three Signs Your Playbook Has Stopped Working

None of these are definitive on their own. But if more than one is present, it's worth slowing down before reaching for another solution.

1) You keep solving the same problem.It gets addressed, things improve, and then it comes back — sometimes in the same form, sometimes wearing a different hat. Recurring problems are frequently adaptive challenges being managed with technical solutions. The fix works on the surface, but the root cause hasn't been touched because the root cause isn't a process. It's a belief, a behavior, or a relationship dynamic.

2) Your team seems disengaged from your solutions. Not outwardly resistant — just not energized. They implement what's asked, but there's no momentum. Adaptive challenges require co-creation; they can't be handed down. When people feel like change is being done to them rather than with them, even well-designed solutions land flat. If you're doing most of the problem-solving and the team is mostly executing, that's a signal worth investigating.

3) You feel vaguely frustrated that what used to work isn't working. This one is easy to dismiss. It can feel like a personal failing — like you've lost your edge, or the team isn't as capable as previous ones. But that low-grade frustration is often the first reliable signal that the nature of the challenge has shifted. It's worth asking: am I frustrated because I'm doing something wrong, or because I'm applying a good approach to the wrong kind of problem?

What Adaptive Leadership Actually Looks Like in Practice

The goal here isn't to abandon experience — it's to use it differently. Three shifts that matter:

⭐ Slow down the diagnosis. Before reaching for a solution, spend more time with the problem. Ask: is this the kind of challenge my expertise was built for? Or is there something here that requires learning or doing something new? The pause between recognizing a familiar pattern and acting on it is where adaptive leadership lives.

⭐ Get curious about what you don't understand. Adaptive challenges almost always have human complexity at their core — competing values, unspoken fears, identity and belonging questions. The leaders who navigate them well tend to ask more questions and offer fewer answers, at least early on. Not because they lack confidence, but because they understand that the people closest to the problem usually hold pieces of the solution.

⭐ Treat your experience as a starting point, not a conclusion. Bring everything you know to the table. And then stay genuinely open to the possibility that this situation requires something beyond what you already know. The leaders who adapt well in VUCA environments aren't the ones with the least experience — they're the ones who carry their experience lightly enough to learn through it.

When the Discomfort is the Signal

Back to that meeting. The leader whose playbook isn't working isn't failing — they're standing at a genuinely important threshold. The discomfort of "this isn't landing" is information, not indictment. It's the moment that separates leaders who manage familiar challenges well from leaders who can navigate genuinely new terrain.

In a VUCA world, that second kind of leadership isn't optional. The challenges keep changing type, not just intensity. The playbook doesn't stop working because you've gotten worse. It stops working because the world has gotten more interesting.

The question isn't whether to build a new playbook. It's whether you're willing to notice when the old one has reached its limit.

Want to keep learning strategies for adapting to the VUCA world?

Subscribe to the Mindset Wizardry newsletter for weekly insights and tools on leading through VUCA with more clarity and less noise. Click this link to join our free mailing list: https://kajabi.mindset-wizardry.com/contact-form


Reference

Heifetz, R. A., & Linsky, M. (2002). Leadership on the line: Staying alive through the dangers of change. Harvard Business School Press.

Next
Next

Lead Yourself First: The Prerequisite Nobody Talks About