Why "Move Fast and Break Things" Was Always Bad Advice

The phrase entered the technology lexicon as a badge of startup ambition. It left behind a generation of engineers who conflated carelessness with speed, and a generation of products that broke trust before they built it. Speed matters. Carelessness is expensive. These are different things.

It is worth remembering where the phrase came from. It was a license — permission to ignore the downstream consequences of a decision in favor of the upstream thrill of shipping. For a certain kind of product, at a certain scale, with a certain tolerance for failure, that trade made sense. The problem is that it got copied into contexts where breaking things means breaking trust, breaking data, or breaking the one impression a user will ever give you.

The hidden assumption is that speed and care sit at opposite ends of a single dial — that to get more of one you must accept less of the other. In our experience the opposite is true. Most of what slows a team down is not caution. It is rework: the second and third attempts required because the first was built on a guess nobody bothered to check.

The fastest teams we've worked with don't move fast by cutting corners — they move fast by being extremely clear about what they're building and why. Clarity eliminates the rework that slows everyone down.

So the advice should have been: move fast and be deliberate. Decide what matters before you build it. Break things on purpose, in prototypes, where breaking is cheap — not in production, where it is paid for by someone who trusted you.