Transcript
You know that moment when everyone agrees something needs to change? The presentations are brilliant. The language is progressive. The workshops are packed. Everyone nods. Everyone commits. And then... nothing happens. Or worse: Something appears to happen. But underneath? Everything stays exactly the same. Today we're talking about why transformations fail even when nobody's actively resisting. And why this isn't a culture problem. It's a system problem.
The Wrong Question
When transformation fails, we immediately look for someone to blame. We say: The employees aren't open enough. Middle management is scared. The culture is too slow. Leadership doesn't get it. The organization is just... like that. Sounds reasonable, right? It's completely wrong. Because here's what we miss: People almost always act rationally. Not courageously. Not visionally. Rationally. They follow the rules you give them. They respond to the incentives you create. They avoid the punishments you've built in. So when someone won't take a risk, it's usually not because they're cowards. It's because your system punishes risk. When someone won't make a decision, it's not because they lack initiative. It's because your structure removed their authority but kept their accountability. The problem isn't the people. It's the operating system they're running on.
The Uncomfortable Truth
Here's the thesis of this episode. And it's going to sting: Most transformations don't fail because people resist change. They fail because the existing system works perfectly. Yes. Perfectly. Think about it: Your KPI systems reward stability, not learning. Your processes reward CYA, not speed. Your hierarchies reward agreement, not truth. Your reporting systems reward justification, not insight. And then we wonder why innovation is slow. Why responsibility gets delegated up and down but never actually taken. Why everyone says "agile" but nobody moves. This isn't a bug. This is the feature. The system is doing exactly what it was designed to do. Which is: survive. Not transform. Survive.
I Fought the Law
There's this old song – "I Fought the Law." Green Day does my favorite version. Most people hear it as a rebel anthem. But it's actually something else. It's a diagnosis. The narrator isn't fighting people. He's fighting a system. And the system wins. Not because it's morally right. Because it's structurally dominant. "I fought the law and the law won." That's not defeat. That's pattern recognition. In business, it looks like this: Good idea meets budget logic. Budget wins. Bold proposal meets career path calculus. Career path wins. Responsibility meets lack of decision rights. Paralysis wins. The system doesn't say "no." That would be honest. It says: "Sure – but under our conditions." Which means: "Sure – but not really."
Transformation Theater
The result is something we've all seen: Agile transformation without power redistribution. New Work without trust culture. Innovation labs without risk budgets. AI strategy without changes to decision-making. Customer centricity without authority to say no to internal stakeholders. I call this: Transformation Theater. It looks like change. It sounds like progress. It uses all the right words. But it doesn't touch the rules of the game. And as long as incentives, risks, and decision rights stay the same, every transformation is just a new label on an old bottle. Here's how you spot it: Are people rewarded for learning from failure? Or just for avoiding it? Can teams actually kill projects that aren't working? Or do they have to pretend they're working until the budget runs out? Do you measure what matters? Or what's easy to measure? Can someone go against process and be proven right? Or is "following process" more important than being right? If the answer makes you uncomfortable, you're doing theater.
The Real Cause
Why does this keep happening? Because transformation happens at the wrong level. We talk about: Vision. Values. Mindset. Culture. Attitude. But we avoid the actual questions: Who decides what – and what's off limits? Who carries which risks? Which metric loses its power? What happens when someone breaks the process and is proven right? What do we stop measuring? Who loses their veto? These aren't comfortable questions. So we don't ask them. Instead, we send people to workshops. We create vision statements. We talk about psychological safety. All good things. But they're downstream. You can't workshop your way out of structural contradictions. You can't vision-board your way past misaligned incentives. You can't culture-statement your way around power that refuses to move. The system always wins these battles. Because the system isn't playing the same game you are.
The Power Question
If we're honest about this, we have to accept something most people don't want to hear: Transformation is not a culture project. It's a power question. And power is uncomfortable. You can't smile it away. You can't facilitate it. You can't rebrand it. Real change requires asking: What do we stop doing? Not just what do we start. Who loses influence? Not just who gains opportunity. Which sacred cow do we actually slaughter? Not just which ones do we talk about questioning. What gets unmeasured? Not just what new thing we track. These questions reveal something critical: Every system that resists transformation is actually perfectly optimized for something. Maybe it's optimized for political stability. Maybe for risk avoidance. Maybe for legacy revenue. Maybe for control. But it's optimized. And that's why it resists. Because from its perspective, it's not broken. It's winning.
The Pattern
Here's what really happens in most transformations: Phase 1: We identify a problem. Good so far. Phase 2: We create a solution that addresses the symptoms. Still okay. Phase 3: We implement that solution within the existing power structure. Here's where it breaks. Because the existing power structure is usually why the problem exists. You can't solve a structural problem with a programmatic solution. You can't fix a power problem with a process improvement. You can't transform a system that was designed to prevent transformation. I fought the law. And the law won. Every. Single. Time.
The Shift
So what do we do? First: Stop blaming people for responding rationally to irrational systems. Your people aren't the problem. Your brilliant, well-meaning, hardworking people are doing exactly what you're asking them to do. Which is survive in the system you built. Second: Start with structure, not culture. Change the incentives first. Move the power first. Shift the risks first. Culture will follow. It always does. Culture is downstream from structure. Third: Accept that transformation costs something. Someone's metric becomes less important. Someone's veto goes away. Someone's comfortable position becomes uncomfortable. If nobody's uncomfortable, nothing's actually changing. Fourth: Ask better questions. Don't ask: "How do we get buy-in?" Ask: "What are we optimized for that we need to stop being optimized for?" Don't ask: "How do we change the culture?" Ask: "What are the three incentives we need to kill?" Don't ask: "How do we get people to embrace change?" Ask: "What systemic barrier makes change irrational right now?"
Closing
So next time you hear: "People aren't pulling their weight." "The organization isn't ready." "We need to work on culture first." Ask a different question: What is this system so successfully doing that it survives every attempt to change it? Because if the law always wins, the problem isn't the fighter. It's the game you're playing. Maybe we need to stop fighting the law. And start changing it.
If this perspective made you uncomfortable – good. That's where real change starts.
