“We’ve Always Done It This Way”

And Other Silent Ways Teams Sabotage Themselves

There’s a phrase that shows up in small and large teams all the time. It doesn’t sound defensive or confrontational. In fact, it’s often said with a kind of passive certainty, as if it’s meant to end the conversation rather than invite one:

“We’ve always done it this way.”

It’s not the words that cause the damage. It’s what they replace: reflection, curiosity, progress.

Because let’s be honest. Most of the time, the reason something is “done this way” isn’t because it’s the best approach. It’s just momentum. Someone made a call years ago. Someone else built a workaround. And now it’s gospel.

But what worked then may be the very thing slowing you down now.

The process only works because one person holds it together

People don’t always resist change because they’re difficult. They resist it because change can feel like an accusation.

If someone suggests a better way, it can sound like, “You’ve been doing it wrong.”

In case management, where people are under pressure, managing risk, juggling admin, and trying to make a difference, the idea of rethinking your workflow can feel less like an improvement and more like a threat.

Especially when the current system only works because you know how to make it work.

You know which templates to ignore. You know that certain fields don’t mean what they say. You know where the real information lives. (Spoiler: it’s probably not in the official system.)

But if the process only works because one person knows the workaround, it isn’t a process. It’s a liability. And the moment that person is off sick, on leave, or moves roles, everything falls apart.

People don’t see the ripple effects of their habits

Let’s say someone keeps everything in their own notes app instead of logging it properly. They’re not trying to be difficult. They just have their own way.

But then someone else needs to cover a case. Or a safeguarding concern arises. Suddenly, there’s no clear picture of what’s happened. No handover. No timeline. No context. Just confusion.

Or take the boss who avoids checking emails. Doesn’t like them, doesn’t open them. The problem is, most of the team’s updates, decisions, and requests are stuck in that inbox. Instead of moving forward, the team sits in limbo, guessing what’s going on or chasing approvals that never come.

These aren’t tech issues. They’re visibility issues. And over time, they create friction that no one talks about, but everyone feels.

“We have a process” doesn’t mean it’s a good one

Systems are often a patchwork of old decisions and quick fixes that no one ever properly reviewed. Outdated templates. Confusing naming conventions. Folders full of duplicated files. Instructions that don’t match reality.

You’ll see things like case notes stored across multiple folders. Forms that no longer apply. Filenames like FINAL_use_this_one_v3. And somehow, everyone is expected to know what to do.

If a new staff member couldn’t understand what’s happening without sitting down for a full day of explanations, then what you have isn’t a system. It’s a mess everyone’s learned to survive.

When no one owns the decision, the problem just lingers

In a lot of services, decisions float. There’s a clinical lead, a service manager, a director. All technically involved. But no one actually accountable for fixing things.

Someone raises an issue. Maybe they flag that assessments are duplicated across two platforms. The clinical manager agrees it’s clunky. The service lead acknowledges it’s inefficient but says it’s “not the right time.” The director might worry about disruption or feel the team can’t be trusted to implement the change properly.

So the idea doesn’t get rejected. It just gets quietly shelved.

The team adapts. Builds another workaround. And eventually stops raising it altogether. Not because they don’t care. But because they’ve stopped expecting anything to change.

Meetings don’t fix things. Ownership does

Some problems get discussed endlessly. They go on agendas. They get raised in team meetings. People nod. People agree. But unless someone leaves the room with a decision and a deadline, all that talk just burns time.

It’s tempting to believe that talking about a problem is progress. But it isn’t. Not until someone owns it.

The hidden cost of dysfunction isn’t just time. It’s trust

Every time someone chases an update. Every time someone can’t find a note. Every time someone is left guessing. These things chip away at energy, motivation, and morale.

When people spend more time working around the system than working in it, something’s wrong. If no one says anything, or nothing changes when they do, people stop speaking up.

They disengage quietly. Slowly. Until the ambition that used to be there is gone.

So what actually fixes it?

It’s not about burning everything down and starting again. It starts with better questions.

• Does this still make sense for how we work now?

• Are we building around someone’s personal habit, or designing for the team?

• Could someone new step into this tomorrow and make sense of it?

• Are we protecting this process because it works, or just because it’s familiar?

• Is this a system we’re proud of, or something we’ve learned to tolerate?

“It still works” isn’t the bar

Just because the team hasn’t burned out, walked out, or broken down doesn’t mean everything’s fine. Silence doesn’t mean satisfaction, it usually means people have given up complaining.

If your team’s main skill is adapting around the system instead of working within it, the system isn’t working.

And if any of this made you shift in your seat? That’s good news. It means your instincts are still switched on. It means change isn’t just possible — it’s overdue.

That’s where progress starts.

What’s the “we’ve always done it this way” habit you see in your world — and what finally changed it?

#Casemanagement #operations #timesaver #TeamCulture