I remember sitting in the back of a cramped rental sedan about seven years ago, staring at a PowerPoint deck on my laptop. I was headed to a client site to "roll out" a massive operational overhaul. In my head, I was the hero. I had the spreadsheets, the Gantt charts, and a vision so clear I could practically taste it.

But when I stood up in that fluorescent-lit breakroom and started talking about "synergistic workflows" and "realigned reporting structures," I didn't see inspired faces. I saw crossed arms. I saw eye rolls. To be honest, I saw a group of people who were wondering if I’d ever actually done a day’s work in their shoes.

It was a total flop.

I’d made almost every mistake in the book. Since then, after 30+ years in the trenches of operations and management, I’ve learned that organizational change isn't a math problem... it's a people problem. And if I’m being vulnerable here, I still get it wrong sometimes. But I’ve gotten a lot better at spotting the traps before they snap shut.

If you’re leading a team through a transition, whether it’s a new software rollout or a complete cultural shift, you’re likely making one (or all) of these seven mistakes. Let’s look at how to fix them before you find yourself in the back of that metaphorical sedan, wondering where it all went wrong.

1. The "Grand Reveal" Mistake (Lacking a Clear Vision)

We often treat change like a surprise party. We go into a "war room," draw up the plans in secret, and then burst out with a "Surprise! Everything is different now!"

Yikes.

When people don't understand the why, and I mean the deep, messy, "in-the-trenches" why, they fill that vacuum with fear. If you haven't clearly articulated the vision, your team will assume the worst. Are people getting fired? Is the company in trouble?

How to fix it: Stop the secrets. Use my triage framework: Reduce → Route → Resolve.

• Reduce the noise by cutting out the corporate jargon.
• Route the "why" to the natural owners of the processes so they can explain it in their own words.
• Resolve to be transparent, even when you don't have all the answers.

People don't need a perfect plan; they need a clear direction. They can handle "we're doing this because our current system is failing our customers," but they can't handle "we're optimizing for excellence."

2. Bulldozing the Existing Culture

I once tried to implement a "high-accountability" tracking system in a company that had a very "family-first," relaxed culture. I didn't care about their history; I cared about the data. (I know... I can be a bit of a jerk when I'm focused on efficiency).

The result? The team didn't just resist the system; they actively sabotaged it. You can't bolt a new way of working onto a culture that isn't ready for it. Plans are like wet cement; if you try to build on them before they’ve set, or if you ignore the foundation underneath, everything eventually cracks.

How to fix it: You have to meet people where they are. If you’re pushing for a shift in communication, you need to understand how they currently communicate. Tools like DiSC assessments are a lifesaver here. They help you realize that a "D" personality needs the bottom line, while an "S" needs to know how this affects the team's stability.

3. Treating the Plan Like a Holy Relic (The Rigidity Trap)

Have you ever followed a GPS that told you to turn right into a lake? Some leaders treat their change management plans exactly like that. They see the plan is failing, but because it was "approved by the board," they keep driving into the water.

Treating change management like a rigid checklist is a recipe for burnout. Real life is messy. People get sick, markets shift, and sometimes the "perfect" software you bought is actually a nightmare to use.

How to fix it: Stay flexible. I’ve written before about the simple trick to improve your project management, and it boils down to this: build in "check-ins" where you’re allowed to say, "This part isn't working. Let's change it." If your plan can't survive a little reality, it's not a good plan.

4. Setting "Yesterday" Timelines

We all want results now. I get it. I’m the most impatient person I know. But when you set unrealistic timelines for organizational change, you aren't just stressing people out, you're actually slowing the process down.

When people are overwhelmed, they stop learning. They go into survival mode. They do the bare minimum to get you off their backs, and then they go back to their old habits the second you look away.

How to fix it: Focus on short-term wins. If you're doing a year-long overhaul, find something you can "fix" in two weeks. Celebrate it. Give the team a "win" so they have the energy to tackle the next mountain. It’s about building momentum, not just checking boxes.

5. Falling in Love with "Stuff" Instead of People

It’s so easy to get distracted by the shiny new CRM or the fancy HR software. We think, "If we just buy this tool, our problems will be solved." (Notice the name of my company? Yeah, I'm a fan of solutions... but software usually isn't the whole answer).

If you focus on the technical side and ignore the people side, you’re just buying an expensive paperweight. I’ve seen companies spend six figures on software that no one uses because the leadership forgot to ask the frontline staff what they actually needed.

How to fix it: Generate "pull" instead of "push." Instead of mandating a new tool, show the team how it solves a specific pain point they have. If you can integrate skills-based planning without complex software first, do it. Prove the concept, then buy the tool.

6. The "Copy-Paste" Framework Mistake

There are some great frameworks out there: Kotter, ADKAR, you name it. And while I use pieces of them, the mistake is thinking you can just copy-paste a framework from a textbook into your unique business.

Your business has its own quirks, its own "tribal knowledge," and its own specific set of characters. A generic framework doesn't account for the fact that your Head of Operations has been there for 20 years and hates change, or that your remote team feels disconnected.

How to fix it: Adapt, don't just adopt. Use the frameworks as a guide, but customize the implementation. I always look at actionable evaluations to see what’s actually sticking in this specific environment.

7. Measuring "Busyness" Instead of Business Value

This is the big one. We often measure the success of a change initiative by how many meetings we had or how many people "completed the training."

But did the change actually make the business better?

If you’re an Executive Director or a business owner, the ultimate metric for change is independence. Is the organization becoming more independent of you? Or are you now more involved because you have to micromanage the new "efficient" process?

How to fix it: Use these independence indicators to see if your change is actually working:

• Delegation: Are decisions being made at the appropriate levels, or is everything still flowing to your desk?
• Relationships: Are the key client relationships distributed, or do they still only talk to you?
• Absence Test: If you went on vacation for two weeks, would this new "change" hold up, or would it crumble?

If the change requires you to be the "Chief Reminder Officer," it’s not a successful change. It’s just a new burden.

Bringing it All Together

I know this is a lot. To be honest, even as someone who has been around the block, I still have to remind myself to slow down and listen more than I talk. Organizational change is messy. It’s loud. It’s often frustrating.

But if you can move away from the "Grand Reveal" and start involving your people: truly involving them: the results are incredible. You move from a state of "pushing" change to a state where the organization is "pulling" itself toward a better version.

I’d love to hear about the changes you’re navigating right now. Are you hitting a wall? Are you making one of these mistakes? (Don't worry, I've made them all). Let’s talk about it. Reach out via our contact page or check out our coaching services if you need a partner to help you navigate the trenches.

We can solve this together.

( Brett)