The Discipline of Shipping
Every project hits a moment where the thing is good enough to be embarrassing in public but not good enough to satisfy you, and what you do in that moment decides whether you’re a builder or just someone who enjoys the feeling of building. I’ve been on both sides. I know the difference now.
Not shipping feels productive. That’s the trap. You’re working. Refactoring, polishing, adding the feature, fixing the thing only you would ever notice. Busy and virtuous. But nothing you do in private counts, because the entire point of a built thing is contact with reality, and a thing that hasn’t shipped has touched nothing real. Still a theory. You can pour a year into a theory and learn less than you’d learn in a day from one real user touching one rough version.
I’ve come to think shipping isn’t a step in the process, it’s the whole engine. You don’t ship to announce that you learned. You ship in order to learn. The lesson lives on the far side of the release and you literally can’t reach it from where you’re standing. Every hour spent perfecting before shipping is an hour improving a guess. The market has the answer key. Polishing in private is studying harder for a test while refusing to look at the answers sitting right there.
Here’s the discipline part, and why it’s actually hard, not just a productivity tip. Shipping means exposing unfinished work to judgment, and every instinct fights it. The perfectionism that makes your work good is the exact same force that stops you releasing it. So the better your taste, the harder shipping gets. You can see every flaw, and shipping means publishing those flaws with your name on them. The discipline is overriding a high standard at the precise moment it’s working against you. Not lowering the standard. Knowing exactly when to stop serving it.
The frame that finally worked for me: shipping isn’t the end of the work, it’s the start of the real work. Before you ship you’re building an imagined product for an imagined user. After you ship you’re building a real product for real users, and that’s the only version that was ever going to matter. So the faster you ship, the faster you graduate from fiction to reality. The unshipped project, however beautiful, is fiction. A rough thing in someone’s hands is real, and reality is the only place anything good gets built.
I think about the founders writing pamphlets, Paine especially. He didn’t wait for the perfect, complete treatise. He shipped Common Sense, rough and urgent and on time, and it moved a continent in months. A perfect version two years later would have moved nothing, because the moment would have passed. Done and out beats perfect and late every single time, because late usually means never and never moves nothing.
So the whole discipline in one line: build it until it’s good enough to be useful and embarrassing, then ship it, then let the world finish teaching you what you couldn’t learn alone. The embarrassment fades in a week. The lesson stays. Ship.
One of a series of essays. I’m Prajjwal Chittori. prajjwalchittori.com.