Freakonomics Radio - Failure Is Your Friend (Rebroadcast)

Episode Date: May 21, 2015

In which we argue that failure should not only be tolerated but celebrated.

Hey, podcast listeners. This is Stephen Dubner, your host. This episode is about failure. We originally put it out last year, but in case you failed to listen then, see what I did there, we are giving you another chance. And if you did hear it before, I hope you'll find something new this time around. You'll hear about GoFever and how the Challenger space tragedy could have been avoided. You'll learn how to use a pre-mortem and you might even come to think of failure as your friend. Hope you enjoy. So, Levitt, you're a fairly successful fellow. Thank you.

I'm just curious, have you succeeded at everything you've ever done? No, I've mostly failed at everything I've ever done. Particulars, please. Well, definitely golf. Golf has been a lifelong failure. You know, when I was a kid, all I wanted to be was a professional golfer. And thank God that I was so bad at golf that I couldn't even imagine trying to be a pro golfer. I think one of the worst lives you can have in some sense in a modern world is thinking you're good enough to play pro golf, not being good enough to play pro golf, struggling for a decade or 20 years, and then you got nothing to show for it. But

luckily, I was so bad, I couldn't even pretend to follow that path. Now, you also failed at becoming the kind of economist that you thought you should become when you first started studying economics, right? Yeah, I started out as a macroeconomist wannabe. And very quickly, I realized that modern macro was all about solving dynamic optimization models that were hopeless. Then I wanted to be an economic theorist. And I actually, that was more dangerous because I... You were closer. I was closer.

I actually was able to publish some papers that were pretty good in pretty good journals. But the thing that saved me on being a microeconomist is actually a funny story, which is that one of my advisors at MIT, I walked into his office and he said, so what have you been working on, Dave? Now, any normal person would have said, oh, actually, my name is Steve. But I didn't do it. And he called me Dave for literally weeks and months. It got so bad that at the annual party of the faculty and students, I gathered around all of my friends. I said, look, he's going to call me Dave.

Just don't worry about it. And finally, it was not that I thought I couldn't be a theorist. It was that I was so embarrassed and traumatized by the idea that at some point I was going to have to say to my main advisor that my name was actually Steve, not Dave, after six months of pretending, that I decided I should just forget about theory and go do something different. From WNYC, this is Freakonomics Radio, the podcast that explores the hidden side of everything. Here's your host, Stephen Dupner.

We've talked before on this show about quitting, specifically the upside of quitting. We ask, why are so many people so reluctant to quit? One reason is that we tend to equate quitting with failure. And there's a huge stigma attached to failure. But should there be? Perhaps we're not thinking clearly about failure. Maybe failure can be your friend. I always tell my students, fail quickly.

The quicker you fail, the more chances you have to fail at something else before you eventually maybe find the thing that you don't fail at. Here's the thing. When failure is stigmatized, demonized, people will try to avoid it at all costs, even when it represents nothing more than a temporary setback. Steve Levitt, my Freakonomics friend and co-author, he does some consulting on the side. He tells a story about one of his earliest consulting jobs with a big multinational retailer. This was a firm, like many firms, that had a very particular culture. And this was a culture in which if you ever said anything bad about the firm or the prospects of the firm, you were a culprit.

You were not a team player. This firm was about to open its first store in China, in Shanghai. It was a pretty big deal. And for all kinds of reasons, it was really important that the store open on time. So about two months before the scheduled opening, the CEO summoned the leaders of the seven teams that were involved in the store's opening, and he asked each of them for a detailed status report. All the reports were positive. Then the CEO asked all seven team leaders to pick one of three signals, green light, yellow light, or red light, to show how confident they were that the Shanghai store would indeed open on time. All seven went with the green light. Everyone was so excited.

They were completely on track for this opening two months later. Now, there was a very smart set of people at this firm who completely understood how this culture, while helpful in some ways, was potentially detrimental in others. So they had set up an internal prediction market, and they wanted people to be able to express their true opinions. And the market, this sort of prediction market, is a great way to get people to tell you the truth because it's anonymous and because there are actual incentives, money incentives tied to it. And it's fun because people like to win.

It was a competition to see who could amass the most money by buying and selling securities that were tied to the outcome of the firm. And unlike a stock market, which is not supposed to allow insider knowledge, this is actually the opposite, right? In a firm, you're trying to get the best knowledge you can from people who actually are working on the project. Exactly. The firm had put this internal prediction market into place exactly with the hope that

they could learn the truth about what was going on because they weren't sure they were learning it otherwise. This prediction market offered one bet on whether the Chinese store would open on time. Now, considering that all seven team leaders involved in the opening had given it the green light, you might think that everybody at the company would be bullish. They weren't. The company's internal prediction market showed a 92% chance that the store wouldn't open on time. So guess who was right? The anonymous bettors in the prediction market or the team leaders who had to stand in front of their bosses?

So even though the seven teams that all said we're sure we're on track, everybody basically knew almost for sure that there was almost no chance the store would open on time. And indeed, the store did not open on time. What does that say about these seven team leaders who had to present to the CEO and their fear of failure? Was it fear of failure or was it just fear of appearing that they're not doing their job well? How does failure factor in? Well, you know, it's funny because in this case, value can be defined in different ways. I mean, ultimately, they failed. The store did not open.

Could you pin that failure on any individual? Not really. But it's tricky because of the incentive. I mean, we've talked so much about incentives over the years and what kind of incentives. I mean, obviously, there were some financial incentives associated with their jobs. So it wasn't yet. I think that what really was most costly is for you to stand up in the room and be the only one willing to say, I'm really sorry. And I know we've been planning this launch for five years, but we botched it and we're not going to make it.

But there was no place for that. So it's easy, especially from a distance, to criticize the seven team leaders who told their CEO that they were sure the store would open on time. From the sound of it, this CEO had what is called go fever. You ever heard of go fever? That is a phrase associated with NASA having to do with rocket launches. When a boss catches go fever, it can take a lot of courage to focus on potential failures. Just think of all the factors working against you. There's momentum, institutional politics, ego. And the consequences of go fever can be far more tragic than the delayed opening of a retail shop in Shanghai. This is shuttle launch control at T-minus two hours, 28 minutes and counting.

Here comes the 51L flight crew boarding the elevator, ready to depart the ONC building for the launch pad. On January 28, 1986, NASA was planning to launch the Space Shuttle Challenger from Kennedy Space Center in Cape Canaveral, Florida. The mission had drawn massive public interest, largely because the crew included a civilian, a schoolteacher from New Hampshire named Krista McAuliffe. Well, I am so excited to be here. I don't think any teacher has ever been more ready to have two lessons in my life.

The launch had already been delayed a few times. On the night before the new launch date, NASA held a long teleconference call with engineers from Morton Thiokol. That's the contractor that built the Challenger's solid rocket motors. Okay, well, I'm Alan McDonald.

McDonald was one of the Thiokol engineers on site in Cape Canaveral. At the time, I was the director of the Space Shuttle solid rocket motor project for my company, Morton Thiokol. on site in Cape Canaveral. At the time, I was the director of the Space Shuttle Solid Rocket Motor Project for my company, Morton Thiokol. It was unusually cold in Florida. There is a meteorologist in Orlando that's saying that the strong winds we saw today are being followed by extreme cold front moving toward the Cape,

and they're expecting to see temperatures maybe as low as 18 degrees Fahrenheit by tomorrow morning at the opening of our launch window. And I says, good grief. I says, I'm really concerned that our O-ring seals and these big joints will operate properly at those kind of temperatures. These O-ring seals kept the extremely hot gases, like 6,000 degrees hot, from escaping the shuttle boosters. You do not want those gases to escape the shuttle boosters. But as McDonald later described in his book, Truth, Lies, and O-Rings, the boosters had never been tested below 53 degrees. And the forecast for launch morning was calling for temperatures much lower than that. So on that teleconference call the night before the launch, McDonald and his team

recommended that the launch be postponed again. And NASA immediately challenged the basis for such a recommendation, which really surprised me. Because prior to that time, I had given every flight readiness review for every flight since I was put on the program. And I was challenged at every one of them of making sure that I could say it was safe enough to flight. And here, all of a sudden, we recommended not flying, and they challenged the basis for that. McDonald couldn't believe that NASA wanted to launch despite what he saw as an obvious risk. I was amazed that they made such statements because we always erred on the side of safety.

In fact, the engineers got put into a position to prove that it would fail, and they could not do that. That's a whole different question. According to McDonald, his boss back at Morton Thiokol headquarters in Utah got off the NASA conference call for about 30 minutes to talk about the situation with other Thiokol executives. When he got back on the line, McDonald says,

the recommendation to postpone the launch had been reversed. McDonald was angry, but he'd been overruled. The launch was back on. Now, NASA requested that the responsible Morton Thiokol official sign off on the decision to launch. I knew who that responsible Thiokol official was. That was me. That was my job. That was my responsibility. That's where I was at. And I did the smartest thing I ever did in my entire lifetime. And that was I refused to sign the launch recommendation. As a result of that, my boss had to sign it and send it down to me. Which he did by fax machine.

As the engineers were waiting for the fax, McDonald spoke up again. So then I got more frustrated, and I said, well, let me tell you something. I certainly hope nothing happens tomorrow, but if it does, I'm not going to be the person to stand before a board of inquiry and explain why I gave you permission to fly these solid rocket motors in a condition

that I knew they were never qualified to do. Coming up on Freakonomics Radio, you know what happens the next morning, don't you? Flight controllers here looking very carefully at the situation. Obviously a major malfunction. The only thing I saw flying were the solid rocket boosters. They were still going. Everything else had disappeared

in this huge explosion cloud in teeny pieces. And what if you could learn how you might fail without going to the trouble of actually failing. So lean back in your chair, get yourself calm and just a little bit dreamy. I don't want any daydreaming, but I just want you ready to be thinking about things. From WNYC, this is Freakonomics Radio.

Here's your host, Stephen Dubner. So Alan McDonald was the director of the Space Shuttle Solid Rocket Motor Project for Morton Thiokol, the company working with NASA on the Challenger shuttle launch. The night before the launch, McDonald recommended the launch be delayed out of concern that the shuttle's O-ring seals might fail in the unseasonably cold Florida weather. But McDonald was overruled. The next morning, he walked to launch control. Carrying my briefcase in one hand, my headset in the other,

and it was like 22 degrees, and I saw these icicles hanging all over the place, and I said to myself, they obviously aren't going to launch this thing today. And I was amazed they finally came on and obviously aren't going to launch this thing today. And I was amazed they finally came on and said they were going to send a team, an ice team out to see if they could knock the ice down as much as possible to reduce the debris risk, and they did that. They ended up doing that actually twice before they finally went into the terminal account

and launched the Challenger. 10, 9, 8, seven, six. We have main engine start. And I remember I held my breath. Three, two, one, and liftoff. Liftoff of the 25th Space Shuttle mission, and it has cleared the tower. Velocity 2,900 feet per second. Altitude 9 nautical miles.

Downrange distance 7 nautical miles. 73 seconds later to see this thing blow up in the sky. I was in shock. I said, it blew up. My heart sank just like everybody in that control room, and I could hear people sobbing in the background. Flight controllers here looking very carefully at the situation.

Obviously a major malfunction. And I kept hearing this voice over the network saying, RTLS, RTLS, which is return to launch site, and not getting response back from the orbiter. The only thing I saw flying were the solid rocket boosters. They were still going. Everything else had disappeared in this huge explosion cloud, in teeny pieces.

We have a report from the flight dynamics officer that the vehicle has exploded. Flight director confirms that we are looking at checking with the recovery forces to see what can be done at this point. No way they could have survived that, in my opinion. And they didn't, obviously. At that point, McDonald says, the cause of the explosion was unknown. We were told to not copy anything off the screen. They were all frozen. They locked the doors. They cut all the telephone lines so nobody could talk to anybody.

I held the meeting saying that all the data would be considered secret. And it really wasn't until the next day that I really realized what had happened. In the days after the accident, McDonald says, a review of the data showed the cause of the explosion to be what he had feared might happen. The O-rings failed to hold their seal in the cold temperature.

That's exactly what happened. This cause was later made official by a the O-rings into some ice water. I took this stuff that I got out of your seal and I put it in ice water. And I discovered that when you put some pressure on it for a while and then undo it, it maintains, it doesn't stretch back, it stays the same dimension. In other words, for a few seconds at least, and more seconds than that, there's no resilience in this particular material when it's at a temperature of 32 degrees. I believe that has some significance for our problem. Now, of course, Alan McDonald already knew that, or at least that's what he was worried might happen. And that's what makes the Challenger explosion so remarkable and even

more tragic than it was. The people in the know, at least some of them, had foreseen the exact cause of the failure. So why, even with that warning, did NASA push on? What really happened was typical, I think, in large bureaucratic organizations and any big organization, where you're frankly trying to be a hero in doing your job. And NASA had two strikes against it from the start, which one of those is they were too successful. They had gotten by for a quarter of a century now and never lost a single person going to space, which was considered a very hazardous thing to do. And they had rescued the Apollo 13 halfway to the moon when part of the vehicle blew up. Seemed like it was an impossible task, but they did it.

So how could this cold O-ring cause a problem when they had done so much over the past years to be successful? So it gives you a little bit of arrogance you shouldn't have and huge amount of money involved. But they hadn't stumbled yet and they just pressed on. So you really had to, quote, prove that it would fail. And nobody could do that. You might think it's a rare case when a group of decision makers know with such precision just what will go wrong with a project. But is it? What if there were a way to peek around the corner on any project to see if it's destined to fail. That is, if you could learn how you might fail without going to the trouble of actually failing.

I'd like you to meet Gary Klein. I'm a cognitive psychologist. I got my PhD back in 1969 in experimental psychology. Klein's most recent book is Seeing What Others Don't, The Remarkable Ways We Gain Insights. He studies decision-making, especially how people make decisions in real settings, like the Challenger launch. The Challenger incident has been intensely studied

and serves as a wonderful object lesson. And what we saw here was repression of consequences that you didn't want to have to deal with because it would have been so inconvenient. So we make the argument in our book that there's a general reluctance to quit or to untangle ourself from projects or relationships or whatnot. And that that's in part because failure is seen as such a stigma. No one wants to, we don't want to quit because we don't want to be seen as having failed. And so let's talk first of all about the stigma of failure. Do you think it deserves it? Or do you think we should rethink the way we consider failure generally? Well, the standard line is that you fail often to get smarter and you fail in productive ways.

And it's a way of building mental models. And all of those things are true. So how can failure be made more fruitful? Gary Klein has one idea, which I think is pretty brilliant. It's called the premortem. You have surely heard of a postmortem. That's the process by which you figure out what exactly killed, say, a hospital patient or maybe a big project. Theoretically, everybody benefits from the knowledge you gather during a postmortem. Everybody except the patient because the patient is dead.

The idea of a pre-mortem is to try to run through that process before the patient dies. But the patient in this case, we should say, is not a human, but it's a project or a product or something like that, correct? Exactly, exactly. With a pre-mortem, you try to find out what might go wrong before it goes wrong. How does this work?

Gary Klein will walk us through it. Imagine you work for a company that's about to launch some big project that you and a lot of others have been working on for months, maybe years. But before you launch, Klein gathers all the important team members in a room. I need you to be in a relaxed state of mind. So lean back in your chair, get yourself calm and just a little bit dreamy. I don't want any daydreaming, but I just want you ready to be thinking about things.

And I'm looking in a crystal ball and, oh, oh gosh, the image in the crystal ball is a really ugly image. This is a six-month effort. We are now three months into the effort, and it's clear this project has failed. There's no doubt about it. There's no way that it's going to succeed. Oh, and I'm looking at another scene a few months later.

The project is over over and we don't even want to talk about it. And when we pass each other in the hall, we don't even make eye contact. It's that painful. Okay, so this project has failed, no doubt about it. Now, for the next two minutes, and I'm going to time this, for the next two minutes, and I'm going to time this, for the next two minutes, I want each of you to write down all the reasons why this project has failed. We know it failed, no doubts. Write down why it failed. I keep a strict clock because we don't want to chew up too much time on this.

And I see everybody is writing, and I say there's 20 seconds to go, and they're writing faster because they're trying to get everything in. And now five seconds, and then, okay, finish this sentence, and then pencils up. Now Klein would go around the room and ask for one item from each person's list, and they compile a catalog of all the ways the project might fail. Klein calls this perspective hindsight. And what does it accomplish?

It really reduces overconfidence, and people are usually way too confident at the beginning of a project. So the premortem tempers that overconfidence. Now Klein would ask everyone in the room to think up one thing they could do to help the project. And then we go around the room to see what people are planning to do that they hadn't thought of before to try to make it more successful. So you put a happy ending on a potentially sad story. Exactly. That's what we're trying to do without sugarcoating the problems that that faces. Now, here's an obvious question.

If you are running a premortem and everybody involved with the project is able to come up with a few ways in which the project might fail, why are these potential problems only coming up now when the project is about to launch? Gary Klein says that's because the pre-mortem liberates people who might otherwise be afraid of looking like they're not a team player, because now everybody's being asked to think

about failure. So instead of looking like a bad teammate, you are pulling in the same direction as everybody else. Now the demand characteristic is, show me how smart you are. Show me how clever you are and how experienced you are by identifying things that we need to worry about. I'm curious to know how well the premortem is catching on because I feel like whenever I describe it to a group of people, small or large, they're blown away by it.

They love the idea. And very few of them have heard of it. So I'm curious, for an idea that sounds so great and sounds so practical, why hasn't it taken over the world a bit more? That's very kind of you. I'm not entirely sure. I think one reason is we have not gone out of our way to publicize it. This was just a kind of activity that grew up out of our own practice, and we were just doing it internally. And after we would do it with a few project managers and sponsors, and they said, can you use it with some of our other projects,

even though you're not involved? So I sort of see it the other way. I'm surprised at how many people are using it. I hear about people using it, and nobody ever mentioned it to me. So I'm impressed that it's gotten as much mileage as it has. I went back to Steve Levitt with a couple of questions. Why do you think there's such a stigma associated with failure generally? I think to be willing to accept failure, you have to have self-confidence. That you have to be accepting of the idea that failing doesn't define who you are. Failing gets something out of the way that keeps you from finding the thing that you're actually going to be good at.

And, I mean, look, we're spoiled, right? You and I both have stumbled onto a lot of success and it's so much easier to be terrible at things and to admit you're terrible when in other parts of your life you get rewarded and people, you know, write you letters and say you're great. So I think it's easy for us to accept failure. And honestly, you know, I think I've gotten much better as I've gotten older at being able to laugh at myself. I was really insecure for a long time. I didn't want to show people I was bad. But now I think I've actually gotten, I mean, I often will laugh the hardest. When I do stupid things, I laugh the hardest. So what's the strategy if you're the CEO or if you're another CEO,

even if you're the CEO of a two-person operation listening to this, what is the strategy to encourage people to acknowledge that failure may happen and that we'd be much better off dealing with the failure beforehand than after. I think the only credible way to make failure acceptable is to celebrate failure. I know at my little firm, TGG, The Greatest Good, we had our greatest failure actually turned out to be our greatest success, I think, in terms of morale building when I got asked to give a speech to one of our clients. And I told the truth in that speech. And it led to our being fired the very next day. The executives of the company, it turned out, weren't that interested in hearing the truth.

And unceremoniously, through email, we were fired from one of our biggest accounts. And the thing was that we celebrated it. Not just pretend celebrated. We really celebrated it because our view was there's no point in staying up all night working on projects for clients if they don't appreciate it. If they don't want to hear the truth, then how in the world do we want to spend our life doing this work? And what happened was that people at our little firm, I think they would have thought we'd be upset. And it wasn't just me. The other people who ran the firm, we couldn't have been happier. And we broke out beer and wine and we celebrated the fact that one of the biggest companies in the world had decided to fire us because we told the truth. And I think, you know, one of the things that you and I have really come to believe over time is

that it's really not for most people about money. There's something bigger that if you're going to work hard and do something, it's about the pride and the joy of feeling like you're part of something bigger, something exciting. And the folks who worked at our little consulting room actually felt that day that it was about something bigger, that we were about the truth. We were about doing good work. And that's hard to do in a business setting. But it was, you know, I don't know, I don't want to get all misty- of anybody, but it's kind of magical. Hey, podcast listeners. Next week, you'll hear a brand new episode in which one of our producers tries to live his life as prescribed by the rules of economics.

This mythical creature is called Homo economicus. I call them econs for short. And, you know, none of us know any econs. And you'll hear what normal people think of this mythical creature come to life. I'm tired. I came from work. Go away. Okay, thanks. Just like some random jerk. Promise to never act like this again. A day in the life of Homo economicus.

That's next time on Freakonomics Radio. Thank you. by David Herman. If you want more Freakonomics Radio, you can subscribe to our podcast on iTunes or go to Freakonomics.com, where you'll find lots of radio, a blog, the books, and more.