The NASA Go/No-Go Metric for Boardroom Decisions | Ep #124

Zoran explains the NASA "Go/No-Go" protocol and how to apply it to high-stakes business decisions. Learn how to eliminate Groupthink by establishing pre-defined "Hard Constraints" and creating a culture of psychological safety where any team member can stop a failing mission.

 🎙️ Built for Pressure is a short-form podcast for high performers, leaders, and decision-makers who thrive under pressure. Hosted and produced by Zoran Stojković.

🔗 Learn more: www.kizo.ca
📩 Contact: zoran@kizo.ca
📱 Follow on LinkedIn: https://www.linkedin.com/in/zoranstojkovic/
🎧 Subscribe for more episodes on your favorite podcast platform. 

Transcript

0:00

Welcome to the Build for Pressure podcast, episode 124. I'm Zoran Stojkovic. Today, we look at the NASA launch control protocol to ensure your next big decision isn't a challenger waiting to happen. In the final minutes before a multi-billion dollar rocket leaves the pad, NASA performs the go-no-go poll. The flight director calls out every station. Propulsion, guidance, weather, surgeon, and each must answer with a single word. If a single station says no-go, the mission stops. This is the ultimate framework for psychological safety and risk mitigation. But it only works because of one thing. The criteria for no-go were decided months ago in a cold room without the adrenaline of launch day. In the boardroom, we often suffer from groupthink, right? Or maybe the corporate nod is what you've heard it called. We want the project to launch. We want the deal to close. We've weighed it. We've spent so much opportunity cost that we've poured so much time into it essentially that we begin to ignore the weak signals telling us that the o-rings are about to fail if you will we convince ourselves that it'll it'll probably be fine nasa calls this the normalization of deviance it's when you see a small problem so often that you stop seeing it as a risk to prevent this you need to implement a formal go no go metric this means defining your heart constraints before the pressure hits. Most leaders wait until they're in the heat of the moment to decide if a risk is acceptable. That's a mistake. Your brain is biologically biased towards go when the stakes are high and the internal flame is burning. Now, NASA survives because they decide what no-go looks like when their heart rates are at 60 beats per minute, and not 160. For example, if the temperature is below 36 degrees, we do not launch. There is no debate on the pad. The metric is the master. In your business, what are your cold room metrics? Is there a specific burn rate? Is it a lack of a signed contract? Is it a pre-mortem finding that hasn't been addressed? If you haven't defined these, you aren't making a decision. You're making a guess. And guesses under pressure lead to catastrophes. The NASA secret is that every person on the loop has the authority and the obligation to stop the rocket. This requires a level of operational courage, if you will, that many corporate cultures lack. It's simply not built into them. We reward the yes men who push through even when the data says no. But true high performance requires the discipline to call a no-go when the criteria aren't met. When you establish these metrics, you offload the decision stress you aren't choosing to stop the project. The data is stopping the project, right? You aren't choosing to stop the project. It's the data that's stopping the project. And so this allows you to maintain your composure because you aren't fighting an emotional battle against your team's momentum. You're simply following the protocol that you all agreed upon when you were thinking clearly. If you want to handle the pressure of a big launch, you must be willing to stay on the ground if the metrics aren't met. Right? Integrity to the metric is the only thing that keeps the mission alive in the long run. So your mission today, for your most important current project, define three no-go metrics. What are the three specific data points? If hit, would mean you must stop the project immediately. Share them with your team today and establish your cold room baseline. I'll see you next time.