“Move fast and break things” sounds bold. It sounds brave. It sounds like how progress happens. It carries the energy of risk-taking, ambition, and a refusal to be slowed down by doubt or bureaucracy. For a long time, it felt like a rallying cry for people who wanted to build the future instead of asking permission to do so. It’s also mostly wrong.
Have you ever noticed that you only hear about the companies that (allegedly) moved fast and broke things? You don’t hear about the companies that moved fast and died. This is because nobody talks about them, not because this doesn’t happen.
The phrase made sense in a very specific moment: small teams, experimental products, forgiving users, and problems that could be fixed with a rollback and an apology. The blast radius was limited, the stakes were low, and the people affected were often early adopters who expected things to break. That moment rewarded speed because the cost of mistakes was trivial compared to the upside of learning quickly…that moment is largely over.
Today, what you break tends to matter. Systems are bigger, platforms are interconnected, and the consequences of failure travel farther and faster than they used to. What once felt like harmless iteration can now trigger lasting damage.
Acknowledge What the Myth Gets Right
Speed does matter. Momentum matters. Indecision kills more startups than bad decisions, especially in competitive markets where timing can determine who survives and who fades into irrelevance. Waiting too long can turn a great idea into a historical footnote.
If you wait for perfect information, someone else will ship first. They’ll learn faster, attract users sooner, and set expectations before you ever enter the conversation. In many cases, moving quickly is the only way to stay relevant at all.
So yes—moving fast is often a competitive advantage. It creates learning loops, builds energy inside teams, and prevents fear from masquerading as prudence. Speed can be a sign of clarity and conviction when it’s paired with intention.
But that’s where the truth ends. Speed alone is not a strategy, and velocity without direction doesn’t guarantee progress. When speed becomes the goal instead of the tool, it starts to work against you.
Examine What the Myth Gets Wrong
The myth ignores what you’re breaking. It treats all damage as acceptable collateral and assumes that anything broken can simply be rebuilt later. That assumption is convenient, but it’s rarely true.
Breaking code is one thing. Code can be refactored, rewritten, or replaced entirely with enough time and effort. The cost is real, but it’s usually finite.
Breaking trust is another. Trust erodes quietly and rebuilds slowly, if it comes back at all. Customers don’t always complain when trust is broken—they just leave.
Breaking customers, partners, employees, or regulators is usually fatal. These relationships are not versioned assets that can be rolled back with a patch. Once they’re damaged, every future interaction becomes harder.
Many founders confuse urgency with recklessness. They ship before they understand their users, mistaking activity for insight. They scale before they earn loyalty, assuming growth will smooth over rough edges that never actually disappear. They optimize for short-term metrics while quietly eroding credibility.
You don’t notice the damage right away. Trust breaks silently, often behind a dashboard that still looks healthy. By the time it’s visible, it’s already gone—and fixing it costs far more than slowing down ever would have.
Observe What Actually Works
The best teams don’t “move fast and break things.” They move with intent, and they’re deliberate about where speed helps and where it harms. They understand that velocity is only valuable when it’s pointed in the right direction.
They:
Move fast and fix things
Move fast and learn
Move fast and protect what compounds
They treat speed as a way to reduce uncertainty, not as an excuse to ignore consequences. They know what’s fragile and what’s not, and they design their systems and decisions around that distinction.
But protect:
Your reputation
Your user’s time and data
Your team’s morale
These are assets that compound quietly over time. When they’re strong, everything else becomes easier. Once they’re broken, progress slows to a crawl, no matter how fast you try to move.
Adopt a Better Rule
If you need a replacement mantra, try this:
“Move fast where it’s cheap. Move carefully where it’s expensive.”
That framing forces judgment. It asks you to think about consequences before acting, instead of just celebrating speed for its own sake. It acknowledges that not all mistakes cost the same—and that some costs are permanent.
Speed without judgment isn’t courage. It’s laziness disguised as confidence, a refusal to do the harder work of thinking clearly about tradeoffs. Real courage is knowing when to slow down, even when everyone around you is celebrating momentum.
Progress doesn’t come from breaking things indiscriminately. It comes from knowing what not to break, and from building systems that can move quickly without sacrificing what matters most.
Mahalo,
Guy
The distinction between breaking code and breaking trust is the one that deserves far more attention than it gets. Code has version history. Trust doesn't.
What I find fascinating is that "move fast and break things" was never a universal instinct, it was a very specific psychological wiring that got handed a megaphone at exactly the right cultural moment. Through the lens of the STAR Framework, it's essentially Adventurer energy running unchecked, high on autonomy, novelty and momentum, with nobody in the room giving sufficient weight to the Realist voice asking "but what are we protecting here?"
The irony is that the most durable companies tend to be the ones where those two mindsets are in genuine dialogue rather than one drowning out the other. Speed is an Adventurer's superpower. Knowing what not to break is a Realist's.
Your replacement mantra is better. Though I'd add: make sure you've got both types of thinker in the room before you decide which category you're in.
Thanks for this!
I want to challenge something - I don't think it was ever something "that worked" - at least not in complexity. We are just reaching our tipping point where we're experiencing the impacts now of many micro-movements from an economy focused on one bottom line and now recognizing that, in complexity, the only guarantee is that there will be a LANDSCAPE of results, not just the result you are measuring. You can hyper focus, and "move fast" to try to get a school system to get better test scores - and actually achieve that result. But then later you may realize you have destroyed other systems results: the mental health of teachers and students, the students skills and mindsets related to social emotional learning and other un-tested things, etc. In other words, when we "move fast and break things" in complexity where we are only measuring ONE metric outcome, not the health of the whole, is where we contribute to the longer-term "problems" we are now seeing. So your "Move fast when it's cheap." needs a reconsideration of "cheap for WHO?" Cheap for YOU? Not a valid reasoning for collective healthy results if it's not also cheap for those who are impacted by the wider system you are contributing to shifting.
In linearity - or actions in the complicated realm - you can do some effective "think about consequences" before you take action. In complexity, the definition is that there will be impacts in other parts of the system that you could not have planned for. So yes, we need to "think about consequences" for the known potential externalities, but when we act in complexity, we need to know that the ONLY guarantee is that, no matter how hard we "planned" we can't get it "right" - in part because there isn't going to be one result, there is going to be a landscape of results and you and I might value those overall as "good/bad" or "cheap/expensive" differently.
Dave Snowden's use of the terms "probe, sense, respond" in complexity might be useful here. "Probe" vs "solve" or vs "act - in a BIG way." Probing KNOWING you can't get it right, so acting with both caution, a lens of looking at a landscape of results instead of just "your results", and a commitment to quick shifts. Not as sexy as "move fast and break stuff" but much better aligned at contributing to shifting the systems that are causing the "problems" we are worried about!