From Space to Software: Reliability Lessons 40 Years After Challenger

The Space Shuttle Challenger disaster is often explained as a technical failure, but the engineers knew something was wrong before launch. What failed was not their expertise - it was the system of decisions, incentives, and escalation paths that surrounded them. This talk reframes Challenger as a leadership and management case study, highly relevant to today’s engineering managers. Modern software organizations operate systems that are fast-moving, distributed, and business‑critical, under constant pressure to deliver. In those conditions, reliability rarely fails because of a missing alert or a bad design - it fails because risk becomes normalized, concerns stop escalating, and “acceptable” tradeoffs quietly stack up. By drawing deliberate parallels between NASA’s launch decisions and contemporary software organizations, this session examines how management structures, delivery metrics, and cultural signals shape technical outcomes. Attendees will explore how well‑intentioned decisions (schedule pressure, ownership ambiguity, optimistic reporting) create environments where teams do the “right thing” locally while producing system‑level failure. The core argument is simple: reliability is not owned by operations or enforced by tooling. It is a leadership responsibility, expressed through priorities, incentives, and how managers act when tradeoffs appear. Note - this session could be presented in the DevOps category too.