The Tyranny of the Fix

Put a group of smart, well-meaning people in a room with a problem and a deadline, and something very predictable happens.

They fix it.

Quickly. Earnestly. With colour-coded spreadsheets, action logs, and a strong sense of momentum.

And sometimes… they fix the wrong thing.

When the deadline becomes the mission

There’s a particular energy that appears when a problem is framed as urgent. A system breaks. A metric dips. A complaint lands. A delivery date looms.

The question immediately becomes:

“What do we need to do to get this sorted by Friday?”

From that moment on, the fix becomes the mission. The deadline becomes the north star. Everything else. Curiosity, context, cause are quietly pushed aside.

No one is being careless. In fact, the opposite is true. People are focused, committed, professional. They want to help. They want progress.

But somewhere along the way, one question gets skipped:

Why is this a problem in the first place?

Symptoms are very persuasive liars

Most workplace problems don’t arrive with a neat label saying root cause. They arrive as symptoms.

• “This process is too slow.”

• “Customers are unhappy.”

• “We’re missing deadlines.”

• “This team is overloaded.”

Symptoms are loud. They demand attention. They make us feel useful when we act on them.

So we redesign the process. Add a workaround. Create a tracker. Patch the system. Add another meeting. Another approval. Another control.

The symptom improves and everyone breathes. Briefly. 

Until a new problem appears. Or the old one comes back wearing a different hat.

The questions we don’t like to ask

Stopping to ask why can feel uncomfortable, especially when time is tight.

Because “why” questions have a habit of leading somewhere awkward:

• Why does this keep happening?

• Why does this team always carry the risk?

• Why are we compensating for a system that was never designed properly?

• Why are we fixing this manually every year?

• Why does solving this problem create that one?

These questions don’t always fit neatly into a project plan. They don’t respect deadlines. And they sometimes point to problems that are bigger, slower, or more politically difficult than the one on the agenda.

So instead, the group agrees to focus on the fix in front of them.

Groupthink isn’t loud, it’s cosy

Groupthink rarely looks like bad decision-making in the moment.

It looks like alignment.

Everyone nods. The plan makes sense. The actions feel reasonable. No one wants to be the person who says, “Hang on… are we sure this is the real problem?”

Especially when everyone else is already sprinting toward a solution.

Questioning the direction can feel like being unhelpful. Slowing things down. Being “theoretical” when the group wants to be “practical”.

But this is exactly how teams end up stuck in frustrating loops — fixing, firefighting, and wondering why the same issues keep resurfacing under new names.

What if we paused, just briefly?

This isn’t an argument for endless analysis or paralysis by philosophy.

It’s an argument for a pause with intent.

Before fixing, ask:

• Is this the cause, or just the thing we can see?

• If we fix this, what problem might we create next?

• Is there a deeper issue that, if addressed, would remove the need for this fix entirely?

• Could we solve two problems at once if we widened the lens?

• Are we optimising for delivery… or for learning?

Even five minutes of structured “why?” can save months of rework later.

Progress isn’t always forward

The hardest thing to accept in deadline-driven environments is this:

Sometimes the most productive move is to stop moving.

To step back. To question the framing. To resist the gravitational pull of the obvious fix.

Because real progress isn’t just about delivering something by a point in time. It’s about making sure we’re not just getting better at treating symptoms while the underlying condition quietly worsens.

Fixes feel good. Understanding lasts longer.