Most of what we build is designed to be replaced. We know it and we plan for it. The business world measures in quarters. Technology measures in sprints. Politics measures in cycles. Even our personal ambitions tend to stop at retirement, maybe a generation if we're thinking long.
But the most important things humans have ever built — the ones that actually shaped civilization — were built on a different timescale entirely.
There's a question that changes how you work if you let it.
Will this still be working when I'm gone?
Not "will this work." That's a low bar. Anything works on launch day. The demo always works. The question is whether it works on the day you're no longer around to explain it, fix it, or hold it together with your presence.
When "will this work" is the filter, you optimize for the present. You pick the fastest tool, the cheapest option, the solution that gets you through the quarter. You build for the demo, the launch, the deliverable. And then you move on, because the question was answered.
When the filter is whether it'll outlast you, you optimize differently. You choose the tool someone else can maintain. You document not just what you built, but why. You pick the boring option over the clever one, because boring survives personnel changes and clever doesn't. You build in redundancy, because single points of failure are acceptable in projects but catastrophic in legacies.
This isn't about grand ambition. You don't have to be building a cathedral. The filter applies to a small business, a nonprofit, a codebase, a family tradition, a local institution. Will the process I'm building still work when I'm not here to run it? Will the system I'm designing still make sense to someone who's never met me?
The technology industry is particularly bad at this. We celebrate the new and discard the old with a speed that would horrify anyone who builds physical things. A framework that's three years old is "legacy." A system that's been running for a decade is something to replace, not revere.
But the systems that actually run the world are old. Boring old. The infrastructure you depend on every day without thinking about it has been running for decades — not because it's exciting, but because someone designed it to last, and someone else has been maintaining it ever since. The people who do that work see themselves as stewards, not creators.
Stewardship is an unfashionable word. It implies you're taking care of something you didn't build, that your job is preservation rather than innovation, that the highest calling might be handing something off in better condition than you found it.
In a culture that worships founders and disruptors, stewardship sounds like settling. Like you couldn't build your own thing, so you maintain someone else's.
I think it's the opposite. I think stewardship requires more discipline than creation. Anyone can start something. Maintaining it across years, adapting it without breaking it, improving it while preserving what works — that's harder. And rarer.
Here's what I believe, and I think the evidence supports it even if the culture doesn't reward it.
The most valuable things you can build are the ones that don't need you. Not because you don't matter, but because the measure of what you built is what happens after you leave.
Durability is a design choice. Things don't last by accident. They last because someone decided, at every fork in the road, to choose the option that served the future over the option that served the moment.
That choice won't make you famous. It won't get you funded. It won't trend.
But it might mean that something you built is still standing long after you've moved on. And someone, walking through it, might think about the person who decided to build it right instead of building it fast.
They won't know your name.
That's the point.