On Shipping
Shipping isn't a milestone. It's a reckoning. The moment the thing you built meets the world and the world doesn't care the way you thought it would.
There’s a particular kind of silence after you hit deploy.
You’ve been living inside this thing for months. It has consumed your evenings, your weekends, the space in your head that used to be for other things. You know every corner of it. You’ve defended it in conversations, refined it in showers, dreamed about it in the way you only dream about things you’re afraid of.
And then you ship it.
And the world is quiet.
Nobody tells you about this part. The before-shipping narrative is rich with mythology: the hustle, the pivots, the almost-running-out-of-money-but-making-it. The after-shipping narrative skips straight to either success or failure — the triumphant growth chart or the honest post-mortem.
Nobody writes about the forty-eight hours in between. When the thing is live and nobody has found it yet and you’re refreshing analytics like that will change something.
I’ve shipped things that worked. I’ve shipped things that didn’t. I’ve shipped things I couldn’t tell were working or not for months.
What I’ve learned is that shipping is not the event. It’s the beginning of a different kind of work — the work of listening instead of building. Of watching what people actually do instead of what you imagined they’d do.
The product you built is a hypothesis. Shipping is the moment you submit it for review.
Most hypotheses are wrong. That’s not failure. That’s how you find out what the right question was.
The silence after the deploy used to terrify me. Now I try to sit in it. Not in a meditative, peaceful way. More in the way you sit with something uncomfortable because you’ve learned that discomfort is usually where the information is.
The silence means you’ve left the comfort of building and entered the discomfort of being judged.
That’s exactly where you need to be.