It’s Rarely the Person

There’s a particular operational problem that gets misdiagnosed more often than almost any other.

It looks, from the outside, like a people problem.

Someone isn’t performing.
The team seems disorganised.
A new hire is making mistakes or working slowly.

The assumption, reasonable enough, given what’s visible, is that the wrong person is in the role, or that the person needs more supervision, more training, more something.

In my experience, that assumption is wrong more often than it’s right.

What’s usually happening is that the structure around the person is broken, and the person is absorbing the consequences.

That distinction matters.

What it looks like in practice

I worked with a business where the field team appeared to be perpetually disorganised. They arrived at jobs without the right equipment, drove unnecessary distances, and left clients waiting. The logical conclusion was that the workers needed tighter management.

What was actually happening was this:

The office carefully prepared the weekly schedule, assigning jobs and people in advance. The manager, without informing the office, routinely changed those assignments. The workers showed up to what they’d been told, found the situation had shifted, and spent their day improvising. The office had no idea, so clients weren’t notified.

Nobody was incompetent. Nobody was careless.

The system simply had two people making decisions about the same thing with no agreed-upon process for communicating those changes, and no expectation that one was needed.

Once that became visible, the fix was straightforward. Define who owns the schedule. Build a communication channel for changes. The team didn’t change; the structure did.

And the chaos stopped.

A second situation, a different business, same underlying pattern.

A manager handed over responsibility for completing a series of important documents that accompanied each finished project. The documents weren’t identical; depending on the location and nature of the work carried out, the information required varied considerably.

The handover consisted of one sentence:

“Take this one as an example, they’re all the same.”

They weren’t all the same.

The person newly appointed to the task had no way of knowing that. She spent hours researching what should have been explained, made errors that took further time to correct, and looked, from the outside, like someone who wasn’t up to the job.

She was, in fact, doing her best with nothing to work with.

The problem wasn’t her capability. It was a handover built on assumptions rather than structure.

Why this matters

In both cases, the instinct was to look at the person. And in both cases, looking at the structure would have been faster, cheaper, and considerably fairer.

Structural problems are harder to see than people problems. A person who’s struggling is visible. A missing process, unclear ownership, or a handover with no real substance; these don’t announce themselves. They create friction, and the friction tends to land on whoever is closest to the work.

Operational gaps rarely feel like gaps from the inside. The manager who said “they’re all the same” wasn’t being careless; he genuinely believed it. The manager changing the schedule wasn’t trying to create chaos; he was making decisions that felt practical in the moment.

Neither could see the downstream effect, because the structure wasn’t designed to make it visible.

What to look for

If someone in your business is underperforming, making repeated mistakes, or seems slow to get up to speed, it’s worth asking a few questions before drawing conclusions about the person.

What were they actually given when they started the task or the role? Was the handover thorough, or was it assumed that things were self-explanatory?

Are there two people making decisions in the same area without a clear protocol for communicating those decisions?

Is the information they need to do the job well held somewhere accessible, or does it live in someone else’s head?

The answers don’t always point to a structural problem. Sometimes the person genuinely isn’t the right fit.

But in my experience, it’s worth ruling out the structure before you rule out the person.

Fixing a structural gap is considerably easier than replacing a team member, and considerably less costly in every sense.

The chaos at ground level is rarely where the problem originates. It’s usually just where it lands.

If you’re seeing patterns in your business that feel like people problems, it may be worth examining the structure underneath them before making personnel decisions. Identifying where operational design is quietly failing is exactly the kind of work I do.

If you’d like to explore it properly, get in touch.