The System Isn't Broken. You Just Can't See It.

Here's a question worth sitting with.

When something goes wrong at work — when someone makes a mistake, burns out, or quietly quits — do you look at the person, or at the system they were operating in?

Most leaders look at the person. They assume the problem is a lack of effort, skill, or commitment. They roll out more training. They write up performance plans. They hire consultants to fix culture.

But Donella Meadows, one of the sharpest systems thinkers of the last century, found something uncomfortable after decades of research: the places where we put almost all of our attention are the places with the least leverage for change.

The invisible architecture

Every organisation runs on systems. Not just the obvious ones — the HR policies, the org charts, the workflows — but invisible ones too. The unspoken rules about who gets to speak in meetings. What happens when you make a mistake. How decisions actually get made, as opposed to how we say they get made.

These invisible systems shape behaviour more powerfully than any mission statement ever could.

Brené Brown describes healthy systems as needing permeable boundaries. For a system to operate, the boundaries have to let feedback flow in and out, bringing new information, so the system can recalibrate and respond.

But when organisations get scared — when there's pressure, scarcity, or uncertainty — something dangerous happens. The walls close. The system becomes self-referencing. It stops listening. It stops learning.

And that's when people get hurt.

The system failure we call "human error"

Here's a pattern you've likely seen play out many times.

Something goes wrong.

We find the person closest to the failure.

We blame them.

We feel better.

The same thing happens again.

We call this accountability. Safety researchers call it something less flattering: the gravitational pull towards finding a human to pin it on. And because no system builds itself, few systems operate by themselves, and none maintain themselves, the search for a human somewhere in the path of a failure is always going to succeed.

That search is a trap.

When we blame individuals for systemic failures, we guarantee those failures will repeat. We treat the symptom while the disease spreads.

Why systems resist change, and why that's useful information

Peter Senge spent decades at MIT studying why organisations struggle to learn and change. His conclusion was elegant and uncomfortable: the harder you push against a system, the harder it pushes back.

This isn't a flaw. It's a feature.

Systems persist because they create stability. They provide predictability. Even dysfunctional systems serve someone's interests, or they wouldn't survive.

Which means fighting a system head-on is usually a losing strategy. It's exhausting, and it rarely works. The people who actually change things are the ones who understand the system deeply enough to find what Senge called leverage points — the places where a small shift produces a large change.

But here's the counterintuitive part. Those leverage points are almost never where you think they are.

Finding the lever

Meadows ranked twelve places where you can intervene in a system, from least to most powerful. The places we focus on most — the parameters, the metrics, the targets — come last on her list.

Think about it. Every organisation obsesses over metrics. We set goals, track KPIs, build dashboards. But changing a number rarely changes behaviour. If someone is already burned out, telling them their productivity target is now 15% higher doesn't help. It makes things worse.

The most powerful leverage points sit deeper:

• The flow of information. Who knows what? What feedback is being blocked or distorted?
• The rules of the system. What is actually being rewarded and punished, regardless of what the policy says?
• The goals. What is this system actually optimising for?
• The paradigm. What assumptions and beliefs does this system rest on?

When you change what information people have access to, you change behaviour. When you change the rules, you change incentives. When you change the goal, you change direction. When you change the paradigm — the underlying beliefs about how things work and what's possible — you change everything.

The school question

Here's an example that might land close to home.

Think about school. The system tells us that an A equals success. So we optimise for A's. We teach to tests. We punish mistakes. We reward compliance.

But here's the question that changes everything: are you at school to learn something, or are you at school to get an A?

They're not the same thing. Sometimes they're opposites.

When you're optimising for grades, you avoid hard challenges, because they're risky. You don't ask questions, because you might look stupid. You don't try new approaches, in case they don't work. The system designed to promote learning actually inhibits it.

The same dynamic plays out at work every day.

When the system rewards looking busy over being effective, people look busy. When the system punishes those who raise problems, problems go unreported. When the system optimises for short-term metrics, long-term sustainability suffers.

The system is working perfectly. It's just not working for what you think it's working for.

A different way to look at being stuck

The next time you feel stuck — or the next time you see someone on your team struggling — try asking a different question.

Instead of "what's wrong with this person?", ask: "what is the system making easy, and what is it making hard?"

There are really only two possibilities.

You're trying to do something that cannot be done — the laws of physics, the constraints of time, the limits of human capacity.

Or you're trying to do something that is hard or uncomfortable because there's a system that doesn't want you to do it differently.

Most of the time, it's the second one.

The discomfort you feel when you try to change things? That's the system pushing back. The obstacles that keep appearing? That's the system protecting itself. The sense that you're swimming upstream? That's what it feels like to work against invisible architecture.

This isn't paranoia. Systems are built to maintain equilibrium. They resist change the way a body resists a fever — automatically, continuously, and without conscious intent.

Making the invisible visible

Here's what we've learned from years of helping organisations see their own systems.

The first work is making the invisible visible. You cannot change what you cannot see. And most leaders are swimming in systems they've never examined — systems they inherited, systems they've normalised, systems that feel like just how things are.

But how things are is not how things have to be. Every system was designed, even if that design was unconscious, incremental and accidental.

Every system was designed. Which means every system can be redesigned.

The question isn't whether you have the power to change things. The question is whether you can see clearly enough to know what to change.

Building a workplace where things work

Here's what becomes possible when you start thinking in systems.

A workplace where the tools are at hand. Where meetings don't paralyse progress. Where decisions get made when they need to get made, and where they don't get undone.

A workplace where people expect good things — from their leaders, their peers, and the market. Where they expect to be heard when they have something to say, and expect that with hard work they can make a difference.

A workplace where people are educated, not merely well graded, and are kept trained and up to speed.

A workplace where people are treated with dignity and respect. Where short-term urgency is never used as an excuse to abandon the principles that built the organisation in the first place.

This isn't utopia. This is what happens when you stop treating people as the problem and start treating the system as the intervention point.

The real work

Systems thinking sounds abstract until you start applying it. Then it becomes the most practical thing in the world.

It means asking: what feedback loops are reinforcing the behaviours we don't want? What information isn't flowing that should be? What rules are creating perverse incentives? What goals are we actually optimising for, regardless of what we say?

It means investigating system failures rather than just pointing fingers. It means holding individuals accountable and examining whether the system gave them what they needed to succeed. Those two things are not in tension.

It also means understanding that you are part of the system. Your own mental models, assumptions and blind spots are contributing to the patterns you're trying to change. Senge put it simply: he has to be prepared to be wrong, because if it were obvious what we ought to be doing, we would already be doing it. So he's part of the problem.

A different kind of leadership

The leaders who make lasting change aren't the ones who push hardest against systems. They're the ones who understand systems deeply enough to work with them, using the system's own rules and relationships rather than fighting head-on.

They're designers, not just commanders. They see their job as building workplaces where good outcomes are likely, rather than heroically intervening when bad outcomes occur.

They ask better questions. What is this system actually optimising for? Where are the leverage points? What small changes might produce big effects? What would have to be true for people to succeed here?

And they stay curious. They keep looking. They keep learning. Because in a world of complex systems, humility isn't weakness. It's accuracy.

Seeing it is the hard part

All of this rests on one thing, and it's the thing organisations find hardest.

You have to be able to see the system before you can find the leverage point. And the invisible architecture is invisible precisely because it's distributed — across rostering, workload, structure, turnover, incidents, policies, and how change gets handled. No one person holds it in view. It exists in the gaps between systems that don't talk to each other.

That's the problem a Gentia Roadmap is built to solve. It works from the material your organisation already produces and assembles it into one picture: where people-related risk is concentrated, what conditions are producing it, and which change would most likely shift the outcome.

Which is another way of describing what this article has been arguing for. Not finding the person nearest the failure. Finding the leverage point.

The system isn't broken. You just couldn't see it. Now you can.