Explorers and Settlers

We like beginnings.

We like the moment something new appears - the spark, the sketch, the prototype that hums with possibility.

In the product world, that makes us explorers.

We draw maps where there were none. We build new things because the old ones feel too slow, too fixed, too full of compromise.

But once a thing exists - once it has users, bugs, and consequences -someone has to stay behind.

Someone has to keep it standing.

The People Who Stay

Every product has two kinds of people: explorers and settlers.

They’re not roles on an org chart - they’re temperaments.

Explorers thrive in uncertainty. They chase novelty and the high of the new. They don’t just enjoy solving problems - they enjoy inventing them.

Settlers, on the other hand, bring order. They tend, maintain, and refine. They build routines, documentation, and safety nets so the system can keep breathing once the explorers have moved on.

Both are essential.

And both drive each other slightly mad.

Confession of an Explorer

I should admit it: I’m an explorer.

I like to start things- projects, ideas, teams. I live for the moment something clicks. But if you ask me to maintain it, version it, document it… well, I’ll start sketching the next thing before you finish the sentence.

For a long time, I thought that was fine. That explorers built the future and settlers merely kept it tidy.

But the truth is less romantic.

Without settlers, explorers leave behind beautiful ruins.

It’s easy to build something new.

It’s hard to keep something working.

And the longer I’ve worked in digital design, the more I see that the hard work, the meaningful work, is in what happens after the launch.

The Explorer’s Arrogance

Explorers are often guilty of arrogance, even if it’s accidental.

We treat maintenance as mediocrity - the aftercare that follows genius.

We move on before the ink dries. We call it iteration, but it’s really escape.

We talk about “moving fast” as if speed itself were a virtue, rather than a way to avoid staying long enough to see what breaks.

Settlers, meanwhile, are left to deal with the mess - the rushed architecture, the half-finished migration, the features that shipped with a shrug and a TODO.

To an explorer, a settler looks like a blocker.

To a settler, an explorer looks like a tourist.

But progress without upkeep is just a kind of neglect wearing cool shoes.

Inspired by

The Guardian

This piece began after reading The Guardian’s editorial on the crisis of upkeep.

It argued that Britain isn’t failing because nothing new is being built - it’s failing because what already exists is being left to rot.

Bridges unpainted. Pipes unrepaired. Systems unreformed.

It’s not a crisis of creation, but of care.

That thought stayed with me because it’s just as true in digital products.

Most of our failures aren’t the absence of invention, they’re the erosion of attention.

Software doesn’t die because it was badly designed.

It dies because no one tended it once the pitch deck was approved.

We build faster than we maintain, and then act surprised when things fall apart.

The Guardian was talking about governments, but it might as well have been talking about GitHub.

The Hidden Art of Maintenance

Maintenance isn’t glamorous, but it’s deeply creative.

To maintain something well, you need empathy for its history and imagination for its future.

Slack gets this.

Every few months, they run Fix-It Weeks - scheduled pauses where engineers drop new feature work entirely to focus on quality, debt, and polish.

It’s a deliberate act of slowdown: hunting bugs, simplifying code, improving performance, writing the documentation that everyone pretends already exists.

There’s something beautifully humble about it.

A company famous for speed choosing, periodically, to stop… and care.

GOV.UK’s Design System works the same way.

Their team spends as much time maintaining as inventing. They review every new component like gardeners inspecting a hedge - pruning, shaping, making sure it grows in harmony with what came before. It’s not fast work, but it’s what makes their design language one of the most stable in the world.

And in open source, the lesson is older still.

Thousands of maintainers quietly patch security holes, refactor dependencies, and respond to issue threads long after the original explorers have left.

Their work isn’t innovation in the shiny sense, it’s survival.

They are the settlers of the internet.

You can feel the difference in a well-maintained product.

It has continuity.

It grows older without feeling old.

The Loop of Renewal

The healthiest organisations have stopped treating explorers and settlers as opposites.

They build a loop.

Explorers create; settlers sustain; and through that sustained care, new possibilities for exploration appear.

Creation and maintenance feed each other . Each makes the other possible.

It’s less a handover and more a rhythm - expansion and contraction, invention and attention.

A steady pulse of progress that doesn’t need to burn itself out to move forward.

At Slack, that rhythm is formalised through Fix-It Weeks.

At GOV.UK, it’s embedded in process.

At GitHub, it happens invisibly, through the volunteer caretakers who keep the web’s foundation from crumbling.

Exploration and settlement become a loop, a cycle of renewal that keeps both creativity and integrity alive.

The Cost of Neglect

Neglect is the slowest form of failure.

It doesn’t announce itself… it accumulates quietly, like rust.

First the build pipeline breaks, then the design system diverges, then the trust goes.

Soon you’re launching a “rebrand” or “platform rebuild” that’s really just an apology for all the years you stopped maintaining.

Explorers love to call this reinvention.

Settlers recognise it as déjà vu.

And users?

They just stop believing you’ll ever get it right.

Care as Creation

Explorers imagine the future. Settlers make sure there’s still one left to imagine.

We need both, but we also need respect between them.

Exploration without maintenance is chaos; maintenance without exploration is stagnation.

Maybe the real progress is learning to live in that loop - to build, tend, rebuild, and repeat.

The Guardian was right: the problem isn’t that we don’t invest enough in new things.

It’s that we’ve forgotten how to look after what we’ve already built.

And here’s the irony - the UK can maintain a national design system better than it maintains its train system.

Perhaps that’s where the explorers and settlers finally meet:

In the quiet, necessary art of care.

If you enjoyed this piece

Follow me for more articles about design-driven coding, usability, and the messy, wonderful middle ground between aesthetics and logic.

Author’s note:

I am currently deeply interested in using AI to generate both visual and text-based content. I am actively collaborating with AI on multiple platforms to explore my thoughts on what creativity is and is not.

My current approach is to collaborate with AI by using the output as a foundation upon which to build and modify.