Change Isn’t the Enemy, Comfort Is

AI insights

Preview

Change isn't the enemy; comfort is. Many organizations stick to outdated processes, hindering progress. This article delves into why internal resistance often stalls change and how frameworks like Kotter’s and Kaizen can guide meaningful transformation. It highlights the importance of questioning the status quo and the role of external help in breaking through internal barriers. The narrative follows a conversation with a seasoned executive, illustrating the struggle between cost-saving goals and the reluctance to alter familiar processes. It emphasizes that while change management isn't just a presentation, small, strategic shifts can lead to significant improvements, especially when paired with AI insights. Don't let comfort hold you back.

Change isn’t the problem, the comfort is. Many organizations cling to familiar processes even when they no longer serve their goals. This article explores why internal resistance derails progress, how frameworks like Kotter’s and Kaizen can guide real transformation, and why sometimes, an outsider is exactly what a company needs to move forward..

  • Learn why “we’ve always done it this way” is costing you more than you think
  • Explore practical frameworks for driving meaningful change
  • See how AI and Kaizen work together to improve efficiency
  • Understand when and why external help makes internal change possible.

I was Zooming with a potential client. He leaned back in his chair like he owned the building. And in a way, he did, seventeen years at the same company, from project manager to SVP of Product.

The topic? Process. Specifically, UX delivery.

I pointed out the friction: handoffs, fragmented design systems, endless revisions, wasted hours. Tools could help. So could a few strategic workflow tweaks.

He nodded, then said it:

“The objective is to save money, but we can’t change the process.”

There it was, the corporate koan. Lower cost with zero disruption. Better results from the same ingredients. Magic thinking in a business suit.

Change for change’s sake isn’t the goal. Risk assessment is wise. But there’s a difference between caution and hiding behind legacy processes that stopped working years ago.

The Ritual of the Familiar

Most companies aren’t afraid of change. They’re afraid of admitting the old way isn’t working.

Processes become rituals, familiar, repeatable, comforting. People stick with them because they offer the illusion of control. Disrupting the ritual doesn’t just challenge the work, it threatens the identity built around it.

I’ve seen designers pour hours into spec documents no one reads. Developers stuck waiting on vague inputs. Teams locked in toolchains no one understands, but everyone defends.

All in the name of “how we’ve always done it.

Meanwhile, the CFO wants costs down. The CEO wants faster shipping. And no one wants to be the person who asks:

“What if we stopped doing it this way?”

Frameworks That Actually Work

You don’t need a revolution. But you do need a method.

Here are three I trust:

Kotter’s 8-Step Change Process

Create urgency. Build a coalition. Get quick wins. Great for leaders stuck in analysis paralysis.

ADKAR

Awareness. Desire. Knowledge. Ability. Reinforcement. Focuses on people, not just process. One behavior at a time.

Kaizen

Continuous, incremental change. Small tweaks. Daily questions. Quiet momentum. Ideal for UX and product teams that hate disruption but need evolution.

Think of Kaizen as change management in sneakers, fast, quiet, constant. Pair it with AI: let the machine spot inefficiencies, then apply Kaizen to chip away at them.

Change Management Isn’t a Deck

It’s not a keynote. Not a slide. It’s work.

One hallway conversation. One habit challenged. One person who’s been there ten years finally admitting maybe this process isn’t sacred.

diagram of ADKAR Model: A Framework for Individual Change

I like ADKAR because it’s simple. No jargon. Just human:

  • Awareness: “We’re losing two days per sprint on misfires.”
  • Desire: “What if we used a live doc? One update. Shared across teams.”
  • Knowledge: Show them.
  • Ability: Equip them.
  • Reinforcement: Celebrate the win. Loudly. Publicly.

That’s not theory. That’s Monday morning.

Why Outside Help Works (When Inside Won’t)

Here’s what happens when someone internal tries to lead change:
They get eaten alive. Politely. With smiles and calendar invites.

It’s not about the idea. It’s about the baggage, past arguments, team turf, perceived ambition. People see a threat, not a fix.

That’s where outside help works.

We don’t owe anyone a promotion.

We don’t care who built the system.

We care if it works.

And most importantly: we leave.

We’re not sticking around to protect egos. That clarity means we can call out what others tiptoe around.

I once sat in a room where two directors wanted the same change, but refused to agree because neither wanted to give the other the win. We reframed it as an external insight.

Green light.

Not because it was new.

Because it wasn’t political.

That’s the power of an outsider:

We don’t just bring ideas.

We get them through.

If You’re on the Inside. Yes, It’s Harder. But Not Impossible.

If you’re the internal voice trying to push change, the climb is steeper. But it’s not hopeless.

Start with Kaizen in your sphere.

Track wins. Show data.

Build alliances with other forward-thinkers.

Your baggage? Yes, it’s a factor. But your knowledge of the terrain is also your strength.

Every internal shift chips away at the monolith of “how we’ve always done it.”

The Award-Winning Process Nobody Wanted

I was brought in to fix a mess.

Hundreds of web properties. Disconnected teams. Conflicting development goals. Nothing shipped on time.

The ask?

Rebuild the design system process. Streamline delivery. Get results.

So I did the work. Talked to stakeholders. Sat with devs. Mapped the stack. Spotted the rot: hours lost to handoffs, redundant components, manual cleanup.

Then I embedded, not as a spectator, but inside the fire. We launched multiple sites. Fast. Clean. Calm.

The new system cut waste. Tightened review loops. Designers stopped chasing specs. Devs stopped rewriting the same buttons.

It worked. So well, it won internal awards. Applause at the all-hands. Rolled out across regions.

Then came the meetings:
“We’re not sure this is the right way.”
“It’s good, but it’s not our process.”

Same people.
Same system.
Suddenly: resistance.

They didn’t want better. They wanted familiar, slightly faster.

You can give people everything they asked for. But if it doesn’t feel like the old way, they’ll burn it down, with a smile.

That’s why you need outside help. Not just to fix the work. To break the emotional grip on legacy systems. To say what no one inside can:

What got you here won’t get you further.

Legacy Is a Weight, Not a Weapon

At a billion-dollar firm, I watched a lead dev print out user flows. Marked them up with a red pen. Scanned them back.

Why?

“That way, nothing slips through.”

You can’t keynote that out of someone. You show them a better way, and prove you’re not trying to erase them.

You’re trying to keep them in the game.

Start With One Thing. Break It. Rebuild It.

Kaizen sounds like a workshop. It’s not. It’s basic.

Pick the ugliest part of your process.

Ask: “Why do we do it this way?

Then really listen.

Then change one thing.

Even if it fails, you’ve done more than most.

AI Is Here. It Doesn’t Care About Your Org Chart.

AI won’t save your team if your team can’t change.

It’ll just show you, faster, how inefficient you already are.

Right now, AI can:

  • Audit design systems
  • Flag inconsistencies
  • Generate prototypes
  • Predict engagement

But it won’t convince someone who got promoted for maintaining the status quo.

I watched a senior designer ignore an AI usability report.

It doesn’t understand our users like I do.

The irony?

The users agreed with the AI.

AI isn’t coming for jobs. It’s coming for habits.

Your competitors are already using it, leaner, faster, with half your headcount.

Picture this: AI flags that 30% of team queries are about button states already documented.

Kaizen asks, “How can we fix that?

The fix? A Slackbot. A plugin. A better FAQ.

  • AI finds the pain.
  • Kaizen delivers the fix.
  • You measure the drop.

    That’s the loop.

Leadership Isn’t Keeping the Lights On. It’s Showing the Way Out of the Dark.

You don’t need to burn it all down. But you do need to ask hard questions about what you’ve built.

The best leaders don’t defend systems.
They challenge them.
Change doesn’t mean chaos.
It means relevance.

Start small.
Fix one broken link.
Automate one task.
Replace one pointless meeting with a live dashboard.

The SVP I talked to?
Still hasn’t changed the process.
Still wants to save money.
Still waiting for a miracle.

Don’t be that story.

Don’t let your leadership be defined by inaction.

“Great things are done by a series of small things brought together.”
– Vincent Van Gogh

Want help fixing the one thing your team keeps stepping over?

I’m ready when you are.

Change is hard.
Stagnation is lethal.
Pick your pain.

Pavel Bukengolts

Award-winning UX design leader crafting user-centric products through design thinking, data-driven approaches, and emerging technologies. Passionate about thought leadership and mentoring the next generation of UX professionals.