The Root of Change (2007 → 2026)

I've been thinking about centralization for a long time.

Years ago, I thought I understood the direction fairly clearly.

Large centralized systems were becoming brittle. Networks were making it possible to distribute capabilities that once had to live in one place. Eventually, I thought, the same organizational change we had seen in computing would appear elsewhere.

Some of that happened.

Some didn't.

The analogy turned out to be more useful as a question than as a prediction.

Computing provides an appealing story about decentralization.

Early systems could place enormous capability in a central machine while terminals around it depended on that machine to do most of the work. Later, networks made it practical to distribute computing across many machines.

That brought real advantages.

Work could happen in more places. Capacity could be added differently. Some failures could be isolated rather than taking down everything around them.

Then we built enormous data centers.

Apparently the lesson wasn't simply that centralization was obsolete.

The internet itself contains the contradiction.

It is distributed enough that information can move across many networks, yet much of what we actually do online depends on a relatively small number of companies, platforms, data centers, payment systems and other intermediaries.

Both structures exist at once.

Once I noticed that, the question became more interesting.

Maybe centralization and decentralization aren't opposing destinations.

Maybe they're tools.

A town probably shouldn't manufacture its own microprocessors.

It might want more than one way to communicate during an emergency.

A small business doesn't need to operate its own payment network.

It may want to retain enough of its customer relationships that losing access to one platform doesn't make the customers disappear.

A community can benefit enormously from a large electrical grid while still finding value in local generation that can continue operating under some conditions when the larger grid has trouble.

The question changes depending on what we're trying to protect.

Centralization is very good at some things.

It can establish common standards, pool expensive resources, coordinate activity across large distances and make complicated services available to people who couldn't reasonably reproduce them locally.

That's why we keep building centers.

They solve real problems.

They create some too.

As more activity passes through a central institution, failure there can affect more people. Decisions become farther removed from some of the places experiencing their consequences. An organization can become efficient at the scale it measures while creating costs somewhere outside the measurement.

Distribution changes those tradeoffs.

Local systems can preserve capabilities when larger ones fail. Different approaches can coexist. Someone closer to the consequences may be able to notice problems sooner.

Then another set of difficulties appears.

Who maintains the standards?

What happens when two systems need to communicate?

Who pays for duplicated capacity that spends most of its time unused?

What happens when a small local institution is badly governed?

Distance isn't the only place accountability can disappear.

Anyone who has lived in a small town knows that proximity doesn't automatically produce wisdom.

So I've become less interested in decentralization as a principle.

I'm more interested in deciding where a center is useful and where dependence on that center becomes dangerous.

There are some practical questions that help.

What happens if this institution disappears tomorrow?

Can another part continue functioning?

How difficult is it to leave?

Who holds the information needed to rebuild the relationship somewhere else?

Does concentrating this function create a capability we couldn't otherwise have?

Does distributing it preserve something we'd otherwise lose?

And who experiences the consequences when the decision is wrong?

Those questions produce different answers in different places.

A national weather service makes sense.

So does the person down the road who knows which creek rises first.

A large hospital can support equipment and expertise a small clinic never could.

That doesn't make the clinic unnecessary.

A national payment network lets a local store transact with almost anyone.

The store still benefits from knowing its customers.

A large information network can tell us what happened across the world five minutes ago.

Someone still has to attend Tuesday night's town meeting.

The mistake may be asking one scale to do the work of all the others.

We've done that in both directions.

Large institutions sometimes assume that because they can coordinate something, they understand every local condition involved.

Localists sometimes assume that because decisions happen nearby, they'll therefore be better decisions.

Neither follows automatically.

Scale changes what can be seen.

A large system can detect patterns invisible to one community. A community can notice conditions too small or particular to matter in national data.

Those aren't competing forms of knowledge unless we make them compete.

They can correct each other.

This is part of what I've been trying to understand through the infrastructure we're building around a regional newspaper.

There are things we should own locally.

Our archive is an obvious example. If preserving the region's memory is part of the newspaper's job, depending entirely on someone else's platform to preserve it would create a strange vulnerability.

There are other things I have no interest in reproducing locally.

We don't need our own global card network.

We can connect to one.

The boundary is the interesting part.

Use the larger system where its scale creates value.

Keep enough capability locally that using it doesn't require surrendering the relationships that make the local institution valuable.

And make the connection replaceable where possible.

That's not decentralization in the pure sense.

It's certainly not independence.

It's closer to choosing dependencies deliberately.

I suspect many systems become fragile not because they contain centers, but because something that began as a useful center gradually becomes the only place a necessary capability can exist.

At first the concentration is efficient.

Then everyone adapts around it.

Alternatives disappear because maintaining them looks wasteful.

Knowledge moves toward the center.

Eventually losing the center becomes almost unimaginable.

That's when efficiency and fragility can start looking surprisingly similar.

The opposite mistake is possible too.

Redundancy has costs.

Local control has costs.

Maintaining several ways of doing something can consume resources that would have been better used elsewhere.

Resilience isn't free.

So there isn't a clean rule.

There is a tradeoff that has to be revisited as conditions change.

Twenty years ago, I thought I was watching society move from centralized systems toward distributed ones.

Now I'm less certain that history moves in directions that cleanly.

What I can see is a continuing negotiation among scales.

Some capabilities move outward because technology makes that possible.

Others concentrate because scale makes them cheaper or more powerful.

Then people discover consequences they didn't anticipate and the boundary moves again.

Maybe that's healthier than reaching the destination I once imagined.

A system capable of changing where it places responsibility may be more adaptable than one committed to either concentration or distribution as an article of faith.

The center isn't necessarily the problem.

The edge isn't necessarily the answer.

The useful question is what each should be trusted to hold.