Stop Fixing the Crisis, Find the System Pattern Creating It

Wondering what system advocacy actually is, and how it’s different from advocating for yourself? System advocacy means fixing the pattern behind a crisis, not just the one crisis in front of you. Here’s what that looks like.

I love this one, because it’s actually a hopeful story hiding inside a frustrating one.

Every crisis tends to get treated like it just fell out of the sky. A complaint lands, a service fails, something goes badly wrong, and the response is almost always the same: patch it up, say sorry, move on to the next one. What rarely happens is someone stepping back far enough to ask the bigger question, why does this keep happening, and why does it keep happening to different people in exactly the same way?

Once you start asking that question, everything opens up.

One crisis is a story, five is a map

A single failure can look like bad luck, a bad day, a one-off. But when the same kind of failure keeps showing up, to different people, in different corners of the same system, that’s not bad luck anymore. That’s a gift, honestly, because it means the fix is findable. Each repeat is a signpost pointing at the exact same spot in the road, and once you can see the signposts, you can finally do something about the road.

What’s usually sitting behind it

Underneath most repeated crises sits something fixable, a policy that doesn’t fit real life, an incentive rewarding the wrong outcome, a gap nobody’s circled back to close. None of that shows up in the headline version of the story. It only shows up when someone’s willing to line up a handful of separate incidents and notice the one root they all share. That’s the exciting bit. That root is something you can actually change.

Quick fixes still count, they’re just not the finish line

There’s nothing wrong with solving today’s problem today, that matters enormously to the person living through it right now, and I’ll always back getting someone through the immediate moment. But a quick fix that’s never followed by a real one just resets the clock until the same crisis shows up again wearing a different face. The best systems treat the quick fix as step one of something bigger, not the whole job done.

Moving from patching to preventing

This is where it gets genuinely good. Preventative redesign means asking what would need to change so this simply couldn’t happen the same way again, to anyone. That turns a system from one that’s forever putting out spot fires into one that’s actually getting better, year on year. Every pattern named and properly fixed is one less crisis someone else has to go through.

How to spot the pattern

It’s simpler than it sounds. Has this same complaint come up before, from someone else, in a similar shape? Does the cause sit with a choice someone made, or with a policy or process sitting upstream of them entirely? What would have to change structurally so this stops recurring, not just so this one case gets sorted? Ask those three things, and a pile of separate incidents turns into one clear, fixable target.

Why I find this hopeful work

Here’s the part I want to leave you with: a pattern, once it’s named, can be redesigned. A crisis on its own can only ever be soothed after the fact. A pattern can be stopped before it ever reaches the next person. Finding it isn’t about pointing fingers, it’s about finally getting somewhere real.

The bit that matters most

When the same crisis keeps happening to different people, it’s no longer an individual story. It’s a system pattern.

Every repeat carries a clue about where the real work needs to happen. Follow it far enough upstream, and you stop the next crisis before it ever starts.

Madeleine x