Why do smart teams still deliver failed projects? Most project failures don't begin with a catastrophic mistake. Instead, they begin with small deviations—minor compromises that seem harmless in the moment. A warning sign gets ignored. A shortcut becomes acceptable. A risk is acknowledged but tolerated because "nothing bad happened last time." Over time, those deviations quietly become the new normal. In this episode of Project Management Happy Hour, Kim Essendrup and Kate Anderson sit down with Dr. Bill Brantley to explore one of the most dangerous patterns in project leadership: normalization of deviance. The concept comes from sociologist Diane Vaughan's analysis of the Challenger space shuttle disaster. Engineers had long observed problems with the shuttle's O-ring seals. But earlier launches survived those anomalies. Each successful launch reinforced the belief that the risk was acceptable. Gradually, what began as an abnormal warning became accepted behavior. As Dr. Brantley explains: "We survived that near miss. It's okay. Next time we'll be okay." Project teams fall into this pattern all the time. A design review is skipped because the team is behind schedule. A test failure gets dismissed because it hasn't caused a real problem yet. A risk gets documented—but never truly addressed. Nothing breaks immediately. So the project keeps moving. The conversation explores how this slow drift toward failure mirrors patterns seen in aviation, engineering disasters, and even mountaineering expeditions. Experienced professionals—people who know better—gradually normalize increasingly risky decisions until the system finally breaks. But the episode goes further than just diagnosing the problem. Dr. Brantley and the hosts dive into the decision dynamics inside projects. A typical project team makes dozens—or even hundreds—of decisions every week. Some have immediate consequences, while others take months or years to reveal their impact. One story from the Apollo program illustrates this perfectly: a weld defect made years earlier ultimately contributed to the crisis of Apollo 13. This delay between decision and consequence creates a dangerous blind spot. Dr. Brantley jokingly calls it the "White Castle effect." "White Castle burgers are great going down… and then at three in the morning you realize you made a bad decision." The same thing happens in project management. Decisions that seem harmless in the moment can produce painful consequences much later. One of the most powerful insights from the discussion is that organizations often fail to reflect on their decisions. Teams act, move forward, and stay busy—but rarely pause to ask whether their decisions are actually improving outcomes. That reflection step is critical. "Reflection really helps you break that normalization of deviance." Without it, teams never notice when small compromises start compounding into systemic risk. The episode also explores practical techniques for improving project decision-making. One of Dr. Brantley's favorites is red teaming—a method borrowed from military strategy and cybersecurity. In a red-team exercise, someone deliberately challenges the plan and tries to break it. Their job is to expose weaknesses before reality does. It's a powerful way to counter groupthink and create psychological safety for dissent. Another theme throughout the conversation is something many project managers intuitively know but rarely articulate: Every action—or inaction—on a project is ultimately a decision. "Everything is a decision. Nobody is going to come after you around anything other than decisions." Whether it's changing scope, delaying work, ignoring a risk, or choosing not to act at all, project leaders are constantly making decisions that shape the outcome of the project. The real question isn't whether decisions are happening. It's whether those decisions are intentional, visible, and thoughtfully examined. Because in many projects, failure doesn't arrive suddenly. It arrives slowly—one accepted deviation at a time. Love our content? Then join the PM Happy Hour membership at pmhappyhour.com/membership

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related