Loading...
In 2018 and 2019, two Boeing 737 MAX aircraft crashed within five months of each other, killing 346 people. The root cause was a faulty automated system called MCAS that pushed the nose down based on a single sensor reading. But the deeper cause was organizational: after Boeing merged with McDonnell Douglas in 1997, the company's center of gravity shifted from engineers in Seattle to executives in Chicago. Leadership increasingly managed by spreadsheet, optimizing for production speed and stock price rather than walking the assembly line. Boeing's senior leaders made decisions about the 737 MAX based on filtered reports that traveled through layers of middle management. Engineers who raised concerns about MCAS were overruled or reassigned. The FAA, which had delegated much of its inspec...
Popular framing: Greedy McDonnell Douglas executives ruined a great engineering company.
Structural analysis: After the 1997 merger, Boeing's principal-agent geometry inverted: leaders managed by filtered spreadsheet from Chicago while the factory floor and engineering judgment lost direct sightlines to the C-suite. The FAA's delegation arrangement, compounded over decades of safe years, was never stress-tested. The compounding that worked in Boeing's favor reversed identically — each revelation amplified doubt about everything else — because trust, once a system property, doesn't rebuild at the rate it was built.
The popular framing implies the problem is solved once the software is fixed and the bad actors are penalized. The structural framing implies the problem persists until the feedback architecture is rebuilt — and that any organization with similar management abstraction and incentive misalignment is vulnerable to the same failure mode. The gap matters because it determines what 'fixing Boeing' actually requires, and because the structural pattern (financialization → management abstraction → feedback degradation → catastrophic failure) is not unique to Boeing.
