 That talks about failure, so it's fitting. Ooh, we'll be good here. Let me start over. And let's go. In the book, The Phoenix Project, there's a guru character named Derek that introduces the three ways. It's a novel that's both entertaining and at times hard to read since it's about the lives that we all lead. So to review, the first way is flow or system thinking. You'll see many talks at this conference about this concept and how to move things out of your development business and into your customers through operations. The second way is regular feedback into the system. The goal is to incorporate as much intelligent feedback as possible sooner, faster, and cheaper. The third way may be the hardest, but it's also the most important. It's to create a culture of continuous learning. Words like collaboration are a lot easier said than done, though. Sydney Decker believes that you can either have a culture that blames or a culture that learns, but you cannot have both, so you must choose one. So in a retribution culture, we meet hurt with hurt, and we ask these common questions. Which rule was broken? How bad were the consequences? What should the consequences be to the person that broke the rule? Does that sound familiar to anyone? In a restorative culture, we meet hurt with healing, and we ask the questions, who is hurt? What are their needs, and whose obligation is it to meet their needs? If you have one takeaway from my talk, it should be to Google Sydney Decker, Just Culture, and to watch the four short courses online, totaling one hour with your team or manager, and discuss them. They're about 15 minutes each. You want to work regularly to build a restorative culture. When will you tell your account, as opposed to paying or settling accounts? When will you have forward-looking accountability? And you look at what is responsible as opposed to who is responsible. And you have to make it safe to fail. Here you see me on a Sharpies many years ago when I was 23. That picture on the right, I did not make the connection after a flip, and I totally ate it. But I had a safety harness, so it was fine, and it was actually a lot of fun. Only two days ago, I got my presale copy of the DevOps Handbook. So between this coming out and helping to organize this conference, I haven't slept that much. But in this book, there's an example, and it's from Netflix. It's always Netflix, right? The DevOps Conference. So from that example, a massive outage was caused by an engineer that had taken Netflix down twice in the last 18 months. What would happen at your job if you took your site down? This engineer was not fired. That engineer was moving Netflix forward by miles, not by miles, but by light years. Mistakes will be made, but trust is what's needed. So what happens when it's not safe to fail? There's hiding, there's secrecy, there's evasion, there's self-protection, there's finger pointing, and worst of all, there's repetitions of errors that we could learn from. If you've not yet read Blameless Postmortems on Etsy's Code as Craft, this is your next assignment. We need an environment without fear of punishment or retribution, or we are doomed to repeat those failures over and over. It's also an important point that I've used in Postmortems in the past is that everyone should be empowered to raise their hand, signaling it could have, should have, or would have. These are hindsight bias, and they are not productive in a Postmortem meeting. Remember that it's too easy to place the blame on the sharp end when in fact it's the entire system that produced the failure. Often this may be policy on the blunt end that needs updating, and that has to be an option in a working system. My personal experience with Postmortems is that we had a monitoring system that was going down on average multiple times a week. We did Postmortems for every issue over four months to finally uncover an issue with the sand driver configuration that should have been updated months earlier. I can tell you for a fact that Postmortems work and help you work to root cause, but a culture of hiding does not work. So for review, check out Sydney Decker Just Culture, make it safe to fail, hold blameless Postmortems, and I know what you're gonna say to me, but my culture isn't restorative yet. So work to change that, or find a place where you have a restorative culture. There are many. You guys are too good to live in a bad culture. So thank you.