Leaders Who Are Scared of Change Shouldn't Lead Change

I watched a CEO commission a digital transformation. Real talk with the board: "We need to innovate. We're getting disrupted. This is existential."

Then the first proposal came through: "Let's reduce the approval chain so we can move faster."

CEO response: "That's too risky. We need to maintain control."

So they hired consultants (who recommended the same thing). CEO still said no. So they formed a committee to study whether the approval chain was a bottleneck.

Eighteen months later, they concluded: yes, the approval chain is a bottleneck.

The CEO's response: "We'll implement a new approval chain."

This is what happens when you green-light change while being terrified of actually changing anything.

The Parking Brake Problem

You can't drive a car fast with the parking brake on. You can rev the engine. You can feel the frustration. But you're not going anywhere.

That's what I see in most transformation attempts. Leadership wants the speed of a startup. They want the agility of a small team. They want disruption.

But they don't want to actually disrupt anything. They want to disrupt the market while keeping everything internal exactly the same.

A CTO I worked with wanted to move to agile. Brought in a coach. Reorganized the teams. Gave them autonomy.

Then every decision got escalated back to him. Not because they were bad decisions. Because he was uncomfortable not knowing exactly what people were working on at all times.

He wanted agile outcomes (speed, flexibility) but couldn't tolerate agile tradeoffs (distributed decision-making, uncertainty).

The teams felt like they had autonomy. Until they made a decision he didn't like. Then they learned the autonomy was conditional.

The Root Cause

Conservative leaders usually become conservative for good reasons. They've seen things blow up. They've learned that chaos costs money. They've built systems to prevent bad surprises.

That's good judgment. Until it isn't.

But here's the thing: they rarely recognize the moment when their judgment becomes a prison.

I worked with a financial services company that couldn't ship anything without a security review. Good reason—they'd had a breach once. Bad reason—everything now took six months and required seven approvals.

They brought in consultants who said: "You need faster security reviews."

The CISO literally said: "No. Security reviews exist to prevent surprises. Faster reviews mean less time to prevent them."

He wasn't wrong, technically. But he was optimizing for prevention of bad outcomes at the expense of ability to move at all.

When you can only move at the pace of your security reviews, you're not innovating. You're slowly disappearing.

What Happens Next

A leader commits to transformation. They're sincere. They genuinely believe they need to change.

But they have exactly zero experience with the kind of chaos that real change requires. They've built careers on control. Now they're asked to trust.

So they pick options that feel like change but aren't:

"Let's adopt agile" (but with the same approval structure) "Let's move fast" (but with detailed pre-approval of every decision) "Let's empower teams" (but report every decision to me immediately) "Let's innovate" (but within these specific constraints I've defined)

None of these are transformation. These are the simulation of transformation.

Real transformation requires the leader to not know what's happening. To trust that things will work out without their constant guidance. To tolerate some chaos.

Most leaders can't do that. So they don't actually transform. They just create the appearance of transformation.

I watched a company hire an innovation team to disrupt their business. Gave them budget. Gave them autonomy. Good setup.

Then checked in on them weekly. Challenged every assumption. Rejected ideas that felt risky. Forced them to build detailed business cases for things they wanted to try.

After a year, the innovation team had shipped exactly three small projects. All pre-approved. All low-risk. All things the main company could have built faster with less ceremony.

The CEO concluded: "Innovation teams don't work."

What actually happened: he couldn't tolerate the risk required for innovation.

The Honest Conversation

If you're a leader and you're genuinely scared of real change, here's the honest move:

Say it.

"We need some innovations but I'm not comfortable with the chaos that comes with real transformation. So we're going to do X" (where X is probably limited pilots, specific domains, things you can kill if they go wrong).

Then do that. Don't pretend you're doing transformation when you're not.

The problem comes when you promise transformation while creating conditions where only safe, pre-approved work can happen. You attract people excited about change. Then you frustrate them. Then they leave.

And you hire people comfortable with your real constraints. And you get a safe, boring organization. And you're confused why you're getting disrupted.

What Actually Works

Real transformation requires a leader who:

Is willing to kill things if they don't work Doesn't need to pre-approve every decision Can tolerate teams trying things that might fail Is willing to change their own mind Doesn't need to understand every decision before it's made

If you're not that person, don't commission a transformation. It's cruel to your team.

Instead, optimize what you have. Make incremental improvements. Keep the company stable.

Both are honest paths.

The dishonest path is promising transformation while maintaining complete control. That's not leadership. That's just frustrating people while pretending you're brave.

Most leaders choose the dishonest path. Then they wonder why innovation never happens.

It's not because innovation is hard. It's because you're driving with the parking brake on and blaming the car.