Getting it right the last time
Iteration isn't a failure to get it right — it's the actual method.
Yesterday I spent a long stretch on a single website's hero section. Not the architecture. Not the strategy. The headline. The spacing around a date. The weight and color of two words.
From the outside that looks like perfectionism run amok. From the inside it felt like something else — like circling a thing until it finally holds still.
There's a quote I keep returning to: it's not at all important to get it right the first time; it's vitally important to get it right the last time. I used to read that as permission to be sloppy early. Now I read it differently. It's a description of how the work actually moves. You don't discover the right version by thinking harder before you start. You discover it by making a version, looking at it, and making another one.
The problem for founders is that this process is expensive when you're doing it alone. Every pass costs time that could be revenue. Every revision is you, not a team. So you develop a complicated relationship with iteration — part of you knows it's the method, the other part resents it as proof you didn't know what you were doing.
But not knowing at the start isn't a character flaw. It's the baseline condition. You're inventing the answer at the same time as the question. The customer-facing site I was refining yesterday didn't have a clear identity when I first put it up. It does now, or closer to it. That clarity came from passes, not from forethought.
The discipline is knowing when you've reached the last time
What separates productive iteration from spinning is the ability to recognize the moment the thing is done — not perfect, but settled. Settled means: the next change would be lateral, not better. It would trade one tradeoff for another without improving the whole.
I reached that moment yesterday. The headline sat where it needed to sit. The spacing stopped feeling wrong. I moved on.
On the proposal work I did alongside it, I did the same thing — repriced, restructured, simplified. First version: too many line items. Last version: one clear number with the discount visible, the logic obvious, the ask easy to say yes to.
Neither of these things was right on the first pass. Both of them needed to be right on the last one.
That's the only standard that actually matters. You don't ship the draft you wished you'd written first. You ship the draft that finally works.