Ship before you're ready — but be honest about which kind of ready
The advice is half right. Some readiness is vanity. Some of it is the only thing between you and a mess you can't undo.
“Ship before you’re ready” is good advice given badly. It gets repeated as though every kind of not-being-ready were the same, and they aren’t.
There are two.
Vanity readiness
The polish you want before strangers see your work: the landing page copy, the fourth logo revision, the empty-state illustration, the settings screen nobody asked for. It exists to protect you from judgment, not to protect anyone from anything.
Vanity readiness is infinite. You will never run out of it, which is exactly what makes it such a comfortable place to hide. Ship without it, every time.
Structural readiness
Different animal. This is the work that is cheap now and ruinous later:
- Can you tell what happened when something goes wrong?
- If a user’s data is wrong, can you fix it without a database surgeon?
- Can you undo the thing you’re about to do?
- Does anyone other than you know how it works?
None of that is polish. It’s the difference between a bad week and a bad quarter. Shipping without it isn’t courage, it’s a loan whose terms you didn’t read.
The sorting question
When I’m arguing with myself about launching, I ask: if this goes badly, is the damage embarrassment or is it wreckage?
Embarrassment is survivable and usually instructive. Ship into it.
Wreckage — lost data, broken trust, something you cannot roll back — is not the same category of risk, and no amount of bias-to-action makes it so.
Most of the time the answer is embarrassment. That’s why the advice caught on. But the reason it’s worth two minutes to check is that the rare time it is wreckage, those two minutes were the cheapest thing you ever bought.
