I’ve been thinking a lot about how to improve velocity and operational efficiency: how to take something from an idea to a successful product faster. That led me to search for patterns that increase the success rate of initiatives. But then another question came up: What actually defines failure?

I’ve seen initiatives that didn’t hit their original goals and were labeled failures. But later, they led to something else—capabilities, insights, or spin-off projects—that became a huge success. So maybe the whole fail fast mindset needs a tweak. It’s not just about failing quickly, but about minimizing waste and making failure useful.

Here’s how I think about it:

1. Fail Fast = Time-Box with an Outcome
   Set clear, desirable outcomes within a defined timeframe. If you don’t hit the goal, don’t just drift forward—make a call:
   • Double down and keep executing?
   • Recalibrate and fire again?
   • Stop and move on?
2. Feedback First, Always
   External or internal, get feedback fast. Without it, you’re working in the dark.
   • Get to real-world feedback as quickly as possible.
   • Keep investment minimal while ensuring you’re not compromising critical foundations.
3. Unknown Unknowns Will Hit You—Plan for That
   No matter how much prep you do, some things will only surface once you’re in motion. Execution reveals blind spots—you can’t anticipate everything up front.
4. Leverage Failures
   If you need to pivot, extract value from what you’ve already built.
   • Tech, insights, processes—there’s always something reusable.
   • Failure is learning, and learning is leverage.