Do you remember that moment, as a developer, when you realized that the code you were writing was ACTUALLY going to production? That there wouldn’t always be someone behind you checking that what’s about to be shipped is perfectly reliable?
Usually, that realization comes hand-in-hand with a nice big bug you introduced, the kind that makes you want to hide under your desk for the rest of your life.
Sure, you survive it by swallowing your pride, but let’s be honest: it never feels great. And the real issue is… we’re going to make more mistakes.

So how are we supposed to handle that, at our own small scale? At the scale of a team? Of an organization?
That’s exactly what “Failure MUST be an option” is all about: accepting this reality and turning it into an opportunity for everyone to grow from each failure.
We’ll talk psychological safety with Amy Edmondson, “perverse incentives” with our British friends, and even NASA’s space shuttles!

In this talk, we laugh, we learn, and above all, we take a step back from failure so it stops being a blame-fest or something we sweep under the rug.
We show up as adults, and we face it — with the right culture and the right tools.