Boeing 737 MAX: Why 346 People Died. And It Wasn't the Software
Artikel konnten nicht hinzugefügt werden
Der Titel konnte nicht zum Warenkorb hinzugefügt werden.
Der Titel konnte nicht zum Merkzettel hinzugefügt werden.
„Von Wunschzettel entfernen“ fehlgeschlagen.
„Podcast folgen“ fehlgeschlagen
„Podcast nicht mehr folgen“ fehlgeschlagen
-
Gesprochen von:
-
Von:
Two crashes.
346 lives lost.
Investigators identified the technical cause within weeks.
So why was the aircraft still flying?
In this episode of Project Insider Asia, Ramesh Dixit examines the Boeing 737 MAX crisis through the lens of project governance, leadership, risk management, and decision-making.
This is not a story about software.
It is a story about incentives, deadlines, organisational pressure, regulatory oversight, and warning signs that were visible long before the crashes occurred.
Drawing on more than 20 years of experience managing complex projects across Asia Pacific, Ramesh breaks down the decisions, trade-offs, and governance failures that turned a technical problem into a global catastrophe.
Topics covered:
• Boeing 737 MAX • MCAS • Aviation Safety • Project Governance • Risk Management • Leadership Failures • Regulatory Oversight • Organizational Decision Making • Systems Thinking
Because projects rarely fail because of one mistake.
They fail because warning signs are ignored.
For Project Insider Asia specifically, this title fits the channel brand much better than focusing on software. Your channel's core promise is understanding why smart people approve bad decisions, not investigating technical failures alone.