An ex-Google CEO argues teams should deliberately try to kill their projects by testing the hardest risks first. The goal is to invalidate the project early, and if you can't kill it after repeated attempts, you know it's viable.
Let's not build a prototype and do all the easy stuff first so that it looks like we're making progress every week. I don't want that because we're in danger of building a ladder to the moon, where we're closer to the moon every week, but we're never really going to get there. Let's work on the hardest part. First, we discuss, for the project that you're going to work on, what are the things that are most likely to kill the project? And I say, your job is not to cause the project to succeed. Your job is to kill your project. You won't be fired. We're just going to keep doing this. And it is only the process of failing to kill your project that will eventually cause it to succeed. You're thinking, does he really mean that? When you do that the first couple of times and you try an experiment with functionally what these things are, maybe it works and we take that risk. Off the list. We de risked your project. We try a few more and we find the fatal flaw. Yes, indeed, this was going to be a ladder to the moon.
Remember me? Subscribe To My Channel For More Free Business Systems Content 📈
