The Space Shuttle Challenger disaster on January 28, 1986, remains one of the most tragic and analysed events in modern history. Often mistakenly viewed as a simple failure of technology or a rushed decision, its true lessons, meticulously uncovered by the Rogers Commission, cut to the heart of organisational bias, leadership pressure, and the perilous consequences of ignoring critical data. While the scale was monumental, the underlying principles of what went wrong offer a sobering and highly relevant warning for every business, including Small and Medium-Sized Businesses (SMBs) today.

At Stewart & Smith Advisory, we believe that understanding these pitfalls is not just for aerospace giants; it’s crucial for any leader striving for effective decision-making and sustainable growth.

The Warning Ignored: Data vs. Desire

The core of the Challenger tragedy was not a lack of data, but a failure to heed it. Engineers at Morton Thiokol, the contractor responsible for the solid rocket boosters, had clear evidence linking cold temperatures to the failure of critical O-ring seals. On the eve of the launch, in a now-infamous teleconference, they vehemently argued against launching in the unprecedented freezing conditions.

Their warnings were precise: the O-rings would lose their resiliency, failing to seal properly and risking a breach. This was the “precision” in the data, the critical insight derived from expertise and empirical evidence. Yet, under intense pressure from NASA management to maintain the launch schedule and public image, these engineering concerns were diluted, dismissed, and ultimately overruled.

The Peril of Organisational Bias

This is where the concept of organisational bias becomes chillingly apparent. What transpired was a dangerous cocktail of:

• “Go-Fever” / Confirmation Bias: NASA had an overwhelming desire to launch. Past successful launches, despite minor O-ring erosion, had led to a “normalisation of deviance.” Managers began to perceive minor damage as an acceptable risk, rather than a warning signal. This created an environment where data that supported a “go” decision was actively sought, while data that suggested “no-go” was scrutinised, doubted, or ignored.
• Pressure to Perform: Both NASA and Morton Thiokol were under immense pressure from politicians, the public, and internal schedules. This external pressure filtered down, turning engineering caution into an inconvenient hurdle rather than a vital safety check. For SMBs, this resonates deeply in the form of investor deadlines, client demands, or the need to meet sales targets.
• Authority Bias: The hierarchy within both organisations played a role. Engineers, initially resolute, felt compelled to present their data in a way that satisfied management’s demand for absolute proof of danger, rather than simply stating the evident risk. Ultimately, management’s authority overrode expert judgment.

The decision to launch was not made quickly out of agile necessity. It was a slow, agonising process where the desire for an outcome (launching on schedule) overpowered the objective data presented by experts.

Lessons for SMBs Today

While your business may not be launching rockets, the pressures and biases that afflicted NASA are present in every organization:

1. Prioritise Psychological Safety: Does your team feel safe enough to voice concerns, even if it means challenging the CEO or a popular initiative? If employees fear reprisal for bad news, critical information will be suppressed. Foster an environment where challenging assumptions is seen as a strength, not a weakness.
2. Actively Combat “Go-Fever”: Whether it’s launching a new product, onboarding a major client, or hitting a quarterly target, the desire to succeed can blind you to red flags. Implement processes for independent review or mandated “red team” challenges to force critical self-reflection before crucial decisions.
3. Respect Expertise, Even When Inconvenient: Listen to your domain experts, even if their findings contradict your desired outcome. They often have the deep knowledge that provides precision where generalists have only assumptions. For an SMB, this might be your lead developer warning about a rushed launch, or your marketing specialist advising against an untested campaign.
4. Define Clear “Stop” Criteria: Before embarking on high-stakes projects, clearly define what conditions would constitute a “no-go.” This allows for objective decision-making points that are less susceptible to emotional or organisational pressure.

The Challenger disaster stands as a stark reminder that even the most advanced organisations can fall victim to fundamental flaws in human and organisational decision-making. For Stewart & Smith Advisory clients, the message is clear: true leadership means cultivating a culture where objective data, critical thinking, and psychological safety always outweigh schedule pressure and collective bias. Ignoring the uncomfortable truth, no matter the scale of your operation, carries an unacceptable risk.

Did you find these insights valuable? Follow Stewart & Smith Advisory for more expert guidance on navigating the complexities of business finance.