Bones' First Law: Ship Broken

"The cost of not shipping always exceeds the cost of shipping broken."

This is the foundational law. The mother lode. The principle that separates builders from planners, doers from dreamers, and companies that win from companies that die with perfect pitch decks.

The Existential Truth

A broken thing that exists beats a perfect thing that doesn't. Period. Full stop. End of fucking discussion.

This isn't about lowering standards or celebrating mediocrity. It's about understanding a deeper truth: momentum is more valuable than perfection, and existence is the hardest problem to solve.

You can iterate on something that ships. You can fix something that's broken. You can improve something that users hate. But you cannot iterate on vapor. You cannot fix what doesn't exist. You cannot improve an idea that's still trapped in your head, polished to perfection but never released to the wild chaos of actual human contact.

Historical Precedent: Every Great Product Shipped Broken

Gmail launched as "beta" and kept that label for five years. Five fucking years. Google's email service, now used by billions, was literally telling users "this might not work properly" for half a decade. But it shipped. And because it shipped, Google learned what worked, what didn't, and how to make it better.

The original iPhone couldn't copy and paste text. Think about that. The device that revolutionized computing launched without one of the most basic functions we take for granted. It couldn't send MMS. It couldn't run background apps. It was, by any reasonable definition, incomplete.

But it shipped.

Facebook launched as "The Facebook" and was restricted to college students. The social network that would connect the world started as a broken, limited version of its ultimate vision. Zuckerberg didn't wait until he could solve global connectivity. He shipped to Harvard, then expanded.

Twitter was a side project that couldn't handle a few thousand users without crashing. The early days were defined by the "fail whale" — literally a branded error page that became part of Twitter's identity. The service that would become the global town square was broken from day one.

Amazon started as a bookstore run out of a garage, packaging books by hand. Bezos didn't wait until he could build the everything store. He shipped books first.

These aren't exceptions. They're the rule. Every transformative product launched broken.

The Hidden Cost of Waiting

While you're perfecting your product, three things are happening:

The market is moving. Customer needs change. Competitor dynamics shift. The window of opportunity narrows. What seemed like a brilliant idea six months ago might be table stakes today.

Motivation fades. The longer something stays unshipped, the more it feels like work and less like magic. The excitement that drives innovation requires feedback loops. Without users, without real-world testing, without the adrenaline of something live in the wild, projects become academic exercises.

Competitors ship. While you're adding that last feature, optimizing that final workflow, perfecting that edge case, someone else is shipping the 80% version. And guess what? 80% that exists beats 100% that doesn't.

This is the cruel arithmetic of innovation: the cost of not shipping compounds daily, while the cost of shipping broken is usually a one-time hit that can be fixed.

The Perfectionist's Trap

Perfectionism isn't about high standards. It's about fear. Fear of criticism, fear of failure, fear of being seen as anything less than flawless.

But here's the thing about criticism: you're going to get it anyway. Ship something broken and get actionable feedback from real users, or ship nothing and get theoretical criticism from people who wouldn't buy your product regardless.

The perfectionist says: "I can't ship this. What if people hate it?"

The builder says: "I can't not ship this. What if people love it?"

The perfectionist optimizes for avoiding negative outcomes. The builder optimizes for creating positive ones. One strategy is defensive. The other is generative.

Practical Application

This doesn't mean ship garbage. It means ship the minimum viable version that solves a real problem, then improve it based on real feedback from real users.

Ask yourself: Does this solve the core problem? If yes, ship it. The secondary features can wait. The polish can wait. The edge cases can wait.

Reed Hastings didn't wait for Netflix to perfect its recommendation algorithm before shipping DVDs by mail. He shipped the core value proposition — movies without late fees — and improved the technology later.

Drew Houston didn't wait for Dropbox to solve every file syncing edge case. He shipped a basic version that worked for most people most of the time, then addressed the complexity.

Brian Chesky didn't wait for Airbnb to have professional photography and seamless payments. He shipped the core insight — people will let strangers stay in their homes — and built the rest as they learned.

The Shipping Mindset

Shipping broken requires a mindset shift from "prevention" to "recovery." Instead of asking "What could go wrong?" ask "How quickly can we fix what goes wrong?"

Instead of building for every possible user, build for the most important users. Instead of solving every possible problem, solve the most important problem really well.

The goal isn't to ship something broken. The goal is to ship something that works well enough for some people, then make it work better for more people.

The Test

Here's the test: If you're not a little embarrassed by your first version, you waited too long to ship.

That flutter of anxiety when you hit "publish"? That's not a bug. That's a feature. It means you're shipping something real into the world before you've overthought it to death.

The cost of not shipping is always higher than the cost of shipping broken. Because broken things can be fixed. Non-existent things can't be iterated on.

Ship broken. Ship often. Ship now.

The world rewards action, not perfection.