Baby steps for big systems

Why complex systems improve through small changes, not perfect plans

There’s a quiet pressure in product and design work to have the answer before anything changes.

Do the research. Map the system. Run the workshops. Align the stakeholders. The idea is that if we stay in discovery long enough, the answer will reveal itself.

It’s easy to boil a solution down to a neat phrase that seems to capture the problem. But in complex systems that phrase rarely means much on its own.

Eventually you still have to decide what to do next.

A lot of the work I do sits inside messy processes that span multiple teams, multiple systems, and years of legacy processes, workarounds, and manual fixes baked into how things operate.

You can map it all, and frameworks like the Double Diamond help bring structure to that kind of complexity.

But even the best map will only show you what you already know.

No matter how much discovery you do, you will never fully understand how a system behaves until something actually changes.

It’s impossible to know what you don’t know.

So what’s the best way to move forward?

Over time I’ve become a big believer in a slightly less glamorous approach:

Try something and see what happens.

Not recklessly. Not all at once.

Just small, deliberate changes that move things forward and reveal what the system actually does.

A lot of the systems we design around have been around for years.

They might be clunky, but they’re familiar. People know where things live and how to use them to get their job done.

If you make huge changes all at once you risk removing the landmarks people rely on. Even improvements can feel disruptive if the whole landscape changes overnight.

Small changes tend to work better.

Adjust one step. Simplify something. Introduce something new alongside what already exists.

Then watch what happens.

Sometimes it works exactly how you expected. Often it doesn’t.

But either way you learn something real about how the system behaves.

In practice the work rarely looks like one neat Double Diamond.

It looks more like a series of smaller ones.

Understand a little. Try something. Learn from it. Adjust. Then repeat.

Perfect plans don’t exist, so aim for small course corrections that move you in the right direction.

Most of the time progress comes from moving forward, learning as you go, and making changes gently enough that people can move with you.

And when people trust that the changes are helping them, they start telling you where the real problems are.

That’s when you will really see the solution.

Then repeat.

Not because the first idea will be right.

But because moving forward will always teach you more than standing still.