What is “Move fast and break things”?
“Move fast and break things” was the famous Facebook engineering mantra coined by Mark Zuckerberg in the company’s early years. The principle: shipping speed matters more than avoiding occasional production bugs because (a) competitors are also moving fast, and (b) most bugs can be fixed faster than competitive advantages can be regained. The mantra was painted on the walls of Facebook’s headquarters until 2014.
The 2014 revision
At Facebook’s 2014 F8 conference, Zuckerberg announced the mantra was retired in favour of “Move fast with stable infrastructure.” The change reflected scaling realities: Facebook’s 2014 user base couldn’t tolerate the bug rate that worked at 2004 scale. The principle behind both versions remained — velocity matters — but the constraints around what you can break shift dramatically with company size.
Why the original worked early
Three contextual factors. (1) Small user base — bugs affected fewer people; reputation damage was contained. (2) No regulatory exposure — pre-2010 social products faced minimal regulatory oversight. (3) No incumbent competition — Facebook’s competitors couldn’t exploit Facebook’s mistakes because they were equally fragile. None of these conditions hold for mature companies.
When the mantra fails
Three failure scenarios. (1) Regulated industries — fintech, healthcare, and education have compliance constraints where “breaking things” can mean license loss or criminal exposure. (2) Trust-dependent businesses — payment infrastructure, healthcare records, identity verification — break-things culture destroys the foundational trust on which the business operates. (3) B2B enterprise — enterprise buyers explicitly evaluate vendor stability; break-things culture extends sales cycles dramatically.
What founders should take from this
The useful principle isn’t “break things”; it’s “ship velocity matters more than perfection at early stages.” The dangerous misreading is using “move fast and break things” as license for irresponsibility. Modern best practice: ship fast within bounded risk envelopes, instrument heavily to detect problems, and explicitly increase rigour as user base, regulatory exposure, and competitive dynamics evolve.
Türkiye context
Türk regulated markets (KVKK personal data, BDDK fintech, SPK securities) particularly punish “break things” culture. A KVKK violation in production can trigger administrative fines of 2-4% of group revenue. Türk founders should explicitly calibrate their velocity-vs-stability balance against regulatory exposure: ship-fast culture appropriate for B2C content app may be catastrophic for KVKK-regulated SaaS or BDDK-licensed payment processing.
Related: Build-Measure-Learn, Strong Opinions, Weakly Held, Founder Mode, Disagree and Commit.