What Saturn's Rings Taught Me About Systems Thinking

The first time I pointed a telescope at Saturn, I expected to be impressed by its size. What actually got me was how still it looked.

Here's a planet with rings made of billions of particles, spanning 282,000 kilometers, pulled on constantly by seven major moons — and from 1.2 billion kilometers away, through a 6-inch lens, it just sits there. Frozen. Like someone painted it on the sky.

I've been thinking about that stillness ever since.

What the rings actually are

Saturn's rings aren't a solid thing. They're billions of separate chunks of ice, from dust grains to pieces the size of a house, each on its own orbit, kept roughly in line by the gravity of the moons.

Nobody's running this. There's no controller deciding where each particle goes, no architect who drew the gaps and the color bands on purpose. Each particle just follows gravity. Run that for 4.5 billion years and you get rings.

The parallel to the systems I work on

I've spent two decades inside enterprise IT. ServiceNow environments with thousands of configuration items. Networks that grew over fifteen years of acquisitions, migrations, and vendor choices made by people who've long since retired.

Nobody designed those either, not really. They came from thousands of small decisions — some good, some just expedient, made under a deadline, made without knowing what had already been decided upstairs.

The environment I manage today doesn't look anything like any architecture diagram ever drawn for it. It's the sum of its history, not the execution of a plan.

That used to bother me. It felt like a discipline problem — if people had just followed the standard, kept the docs current, reviewed every change properly. Then I spent some time with Saturn's rings and it stopped bothering me quite as much.

Order without a designer

The rings aren't a mess just because nobody designed them. They're structured. The Cassini Division, that dark gap between the A and B rings, exists because orbital resonance swept it clean over billions of years. There are spiral density waves rippling through the rings, caused by the pull of the moons.

Structure, with no one drawing it.

Complex systems tend to organize themselves whether you want them to or not. The real question isn't whether that happens — it will — it's whether you understand your system well enough to work with that tendency instead of fighting it.

In practical terms: an enterprise environment that grew organically over fifteen years isn't a disaster waiting to be bulldozed. It's a system that's been under load long enough to find its own balance. Some of that balance is good — the integrations that survived three rounds of vendor changes. Some of it is bad — the workaround from 2019 that quietly became load-bearing. Your job isn't to impose a clean design on top of it. It's to understand it well enough to know what to actually change, and what to leave alone.

The limits of knowing

ServiceNow's discovery tool is really just an attempt to answer one question: what does the system actually look like right now? Not the documented version. The real one.

After years of chasing the gap between the CMDB and reality, I've got a lot of respect for how hard that question is. The map is never the territory. A CMDB is a useful approximation, not the truth.

It's true of Saturn's rings too. We have incredibly detailed models that can predict ring-particle positions centuries out — and the Cassini spacecraft still kept finding things those models didn't predict, in thirteen years of orbiting the planet.

A good-enough map is genuinely useful. A perfect one isn't coming. Knowing the difference matters more than chasing the second one.

What I take back from the telescope

Mostly humility, and a bit less anxiety about complexity I didn't design.

A system nobody designed on purpose, that grew under constraints nobody planned for, isn't automatically worse than one that was architected top-down. Sometimes it's found a balance no architect would have thought to specify.

The stillness I saw in Saturn's rings wasn't the absence of complexity. It was complexity at rest — all that motion adding up to something that looks, from far enough away, like peace. Good infrastructure looks like that too.

The chaos is still underneath. You just don't want people to have to see it.