Every system I’ve built had a flaw on day one.
Not because it was badly designed. Because it met reality.
For a long time I thought that was my failure. If I thought harder, mapped more edge cases, waited one more week, I’d get it right. The clean version. The one that covers everything.
It doesn’t exist.
The perfect system is a design-time illusion. It lives in the doc, in the diagram, in the meeting where everyone nods. Then real people touch it. A customer does something nobody predicted. A field gets left empty. Someone finds a shortcut you never imagined. The rules that looked airtight on paper start leaking on the first Monday.
That’s not the system breaking. That’s the system learning what the world actually looks like.
So the question was never “is this perfect?” The question is “is this the best we can build with what we know today?”
Those are very different standards. One you can meet. The other just keeps you from shipping.
I’ve seen what chasing perfection costs. Weeks of design for a workflow that changes the moment it goes live. Edge cases handled for scenarios that happen once a year, while the thing that happens fifty times a day stays manual. Teams afraid to launch because something might go wrong.
Something will go wrong. That’s the one guarantee.
So here’s what I try to do instead.
Build the best version I can. Honestly the best — not lazy, not “good enough” as an excuse. Then assume it’s wrong somewhere and design for that. Make the failures visible. Make them cheap to fix. Put a human where the system isn’t sure. Leave room to change it without tearing it down.
A good system isn’t one that never fails. It’s one that fails in a way you notice, and recovers without drama.
There’s also a quieter trap. When you believe your system is perfect, you stop looking at it. You defend it instead of improving it. Every complaint becomes “user error.” Every exception becomes someone else’s problem.
The best operators I know are a little suspicious of their own systems. Proud of them, but suspicious. They keep asking where it breaks.
Perfection is a direction, not a destination.
You aim for it. You never arrive. And that’s fine — because the version that’s running, imperfect and improving, beats the perfect one that never shipped.
Build the best system you can.
Then go find out what’s wrong with it.
