"Fail fast" has become one of the most repeated phrases in modern business — and one of the most misused.
It shows up in leadership talks, startup lore, LinkedIn memes, and pitch decks promising agility and innovation. The concept has value, but the way it's often applied is far too broad, far too casual, and — ironically — far too risky for organisations that actually want to grow. Failing fast is useful, but only when it's done with intention, discipline, and a clear understanding of what success looks like. Without that, it's not failing fast. It's just failing.
"Fail fast" has become a shortcut for not thinking
In many organisations, "fail fast" has drifted away from its roots in lean manufacturing and agile development. It's now used as a blanket justification for rapid pivots, rushed decisions, and poorly planned initiatives.
We've entered what feels like an "agile bubble" — where everything is branded as agile, regardless of whether the underlying behaviours reflect true agility. The phrase becomes a shield for skipping the hard work of defining value, planning properly, and aligning teams around measurable outcomes.
And that's where the danger lies.
Tactical failure is cheap. Strategic failure isn't.
Tactical: fail fast works
Failing fast works beautifully in small-batch, tactical environments — prototyping, early-stage product development, experimentation, and innovation labs. At that scale, the cost of failure is low, the learning is immediate, and the feedback loop is tight.
Strategic: fail fast can be catastrophic
Large programmes, strategic initiatives, enterprise transformations, and customer-facing delivery carry real consequences:
- Loss of scarce resources
- Erosion of customer trust
- Delays that ripple across multiple teams
- Strategic drift
- Reduced organisational capacity to execute
Short-term thinking can eliminate long-term options. Mature organisations understand this distinction.
Learning is the point — not the failure
The most important part of "fail fast" is the part most people skip: learning. Eric Ries makes this clear in The Lean Startup: failure is only useful when it produces validated learning. Without learning, failure is just waste.
- A clear definition of success
- Meaningful metrics (not vanity metrics)
- A hypothesis to test
- A disciplined review of what happened and why
- A willingness to adjust based on evidence
This is the same rigor required to plan and deliver a successful project or programme. The maturity is the same. The discipline is the same.
Pivoting is a response — not a strategy
Pivoting is essential when data shows the current direction is no longer valid. Mature organisations pivot when:
- The strategy is not producing the expected outcomes
- The market has shifted
- Customer needs have changed
- Assumptions have been disproven
- Risks outweigh benefits
If an organisation is constantly pivoting, it's not agile — it's lost.
Flailing fast — the immature alternative
Many teams claim they "fail fast" when what they're actually doing is flailing fast. You can spot it easily: failure occurs, and instead of analysing it, leadership launches a new project with the same missing foundations, promising that "this one will fix it."
- Initiating new projects without defining value
- Skipping planning because "we're agile"
- Repeating the same mistakes because no learning occurred
- Abandoning initiatives prematurely
- Starting new ones with the same lack of clarity
- Trading quality and value for speed
That's not agility. It's churn.
Mature organisations don't worship failure — they learn from it
A mature organisation embraces experimentation, but it does so with:
- Clear goals
- Defined value
- Measurable success criteria
- Disciplined delivery
- Thoughtful governance
- A willingness to stop when the data says stop
Fail fast is not the strategy. Learning fast is.
Fail fast has its place. Pivoting has its place. Experimentation has its place. But none of these are long-term strategies for organisational success.
They are tools — useful, powerful, and necessary when applied correctly. Dangerous when used as excuses for poor planning, unclear strategy, or a lack of delivery maturity. If someone says they "fail fast" but doesn't immediately follow with "and we learn fast", then they're not failing fast. They're just failing.
Related insights
- The Premortem: A Smarter Way to Surface the Risks That Actually Matter
Most projects carry hundreds of assumptions. The premortem is a practical technique for finding the 5–10 risks that genuinely threaten delivery.
- AI Isn’t Changing What Project Managers Do — It’s Revealing What They’ve Always Done
AI is exposing the gap between what leaders thought PMs do and what they actually do: clarifying value, structuring delivery, leading people, and ensuring the right outcome.
- AI Can’t Do PM: Why Project Leadership Will Always Be Human Work
AI can accelerate the first 80% of project delivery, but the last 20% — judgement, influence, and leadership — is irreducibly human work.