"Fail fast." Two words that have been repeated so often in startup culture that they've lost almost all of their meaning — and in some cases, have started causing real damage.
I've watched founders use "fail fast" as permission to give up on things prematurely. I've seen others interpret it as "throw things at the wall and see what sticks" — which is just expensive randomness. Neither of these is what the phrase was ever meant to mean.
What It Actually Means
The original idea, popularised by Eric Ries in The Lean Startup, is about learning efficiently. The goal is not to fail — it's to test assumptions as quickly and cheaply as possible, so that when you are wrong (and you will be wrong about something), you find out before you've spent two years and your life savings on it.
"Fail fast" is about the speed of learning — not the acceptance of defeat."
There is a massive difference between:
- Spending 18 months building a product in secret, launching, and discovering nobody wants it — that's failing slowly and expensively.
- Spending 2 weeks building a landing page, running £50 of ads, and discovering that nobody clicks — that's failing fast and cheaply.
The second is not failure. It's research. It's the most valuable kind of data you can get.
The Three Misuses I See Most Often
1. Using it to justify quitting too soon. Building anything worthwhile is hard and slow. Most businesses that eventually succeed went through a period where nothing seemed to be working. "Fail fast" is not a licence to abandon ship when the first wave hits.
2. Failing on the wrong things. If you're testing your logo, your colour scheme, or your company name — you're not failing fast on anything that matters. Test your core assumption: does anyone want this, and will they pay for it?
3. Failing without learning. The whole point of failing fast is to extract the lesson and apply it. If you shut something down and move on without understanding why it didn't work, you're just failing. Full stop.
How to Actually Apply It
Before you build anything, write down your three biggest assumptions about your business. Things like: "Busy parents will pay £30/month for this service." "Marketing managers at SMEs will respond to LinkedIn outreach." "Our customers prefer mobile over desktop."
Then ask: what is the cheapest and fastest way to test each of these? Often the answer is a conversation, a landing page, or a simple manual experiment — not a built product.
When you test, measure specifically. If it doesn't work, understand why before you move on. That's failing fast. That's how you build something that lasts.
