Boeing 737 MAX: When Cost Pressure Changes the Quality Culture

Why the Boeing case is instructive for small businesses too

For decades, Boeing was the epitome of engineering care. The crashes of two 737 MAX aircraft in 2018 and 2019 and a blown-out fuselage panel in 2024 shook this image.

The guiding question of this case study is: how can time and cost pressure change an organization's quality culture, and what can a small business do to keep this from happening to it? To answer it, we first set out the publicly documented facts, then a model from safety research, then two readings of the causes, and finally safeguards for your own business.

Quality rarely disappears through a single decision. It disappears through many small compromises, each of which seemed reasonable on its own.

What happened? The documented facts

The 737 MAX is a revised version of an aircraft type built since the 1960s. New, larger engines changed the flight characteristics in certain situations. Boeing therefore introduced software, the Maneuvering Characteristics Augmentation System, MCAS for short, which automatically pushes the aircraft's nose down in such situations. According to the investigations, this software played a central role in both crashes.

1. October 29, 2018: Lion Air Flight 610

   A 737 MAX crashes into the sea shortly after takeoff from Jakarta. 189 people die.

2. March 10, 2019: Ethiopian Airlines Flight 302

   A 737 MAX crashes shortly after takeoff from Addis Ababa. 157 people die. Shortly afterward, authorities worldwide ground the type.

3. September 2020: Congressional report

   The transportation committee of the US House of Representatives presents its final report on the development and certification of the 737 MAX.

4. November 2020: Return to service

   The US Federal Aviation Administration (FAA) lifts the grounding after changes to software and training.

5. January 2021: Agreement with the Justice Department

   Boeing enters a deferred prosecution agreement and commits to payments of around 2.5 billion US dollars.

6. January 5, 2024: Alaska Airlines Flight 1282

   Shortly after takeoff, a door plug in the fuselage of an almost new 737 MAX 9 blows out. Nobody dies, and the aircraft lands safely.

7. November 2025: Criminal case dismissed

   A federal judge in Texas agrees to dismiss a criminal conspiracy-to-defraud charge after the Justice Department reached a new agreement with Boeing. An appeals court upholds this in March 2026.

On the 2024 incident, the NTSB presented its findings in June 2025. Four bolts meant to hold the door plug in place were missing when the aircraft left the factory. The plug had been opened for work at the Renton plant in September 2023 without the required documentation being completed. As the probable cause, the board named Boeing's failure to provide adequate training, guidance, and oversight. NTSB Chair Jennifer Homendy described this as an organizational problem, not a failure of individuals.

What the reports say about time and cost pressure

The final report of the House transportation committee from September 2020 is the most comprehensive congressional investigation into the development of the 737 MAX. It describes a series of factors that worked together. These include considerable pressure to bring the aircraft to market quickly and cheaply against a competing model, assumptions about pilot behavior that proved wrong, and a lack of transparency toward the regulator and the airlines, for example about how MCAS worked.

Part of these factors was economically motivated. One development goal was that pilots flying the predecessor model could switch to the MAX without extensive simulator training. That made the aircraft cheaper for airlines. Any change that would have required additional training would have jeopardized this advantage. This created an incentive to present the significance of new systems as small as possible.

One distinction matters, and the reports and courts make it themselves. A criminal case against Boeing for conspiracy to defraud the regulator never concluded with a verdict. After a judge rejected a planned plea agreement in December 2024, the Justice Department reached a new agreement in 2025, and the case was dismissed. A former Boeing chief technical pilot was acquitted in a separate trial in 2022. What follows therefore describes documented processes and findings, not criminally established guilt.

The Swiss cheese model: why big failures rarely have one cause

The best-known model in safety research comes from the British psychologist James Reason (1990). He compares an organization's protective layers to slices of Swiss cheese. Each layer, such as design, testing, certification, training, and maintenance, has holes. Usually these holes are in different places, so an error in one layer is caught by the next. An accident happens when the holes in all layers line up for a moment.

Reason distinguishes two kinds of holes. Active failures are actions by people at the scene, such as a forgotten work step. Latent conditions are weaknesses built into the organization long before, such as time pressure, unclear responsibilities, missing training, or a culture in which concerns are not heard. Latent conditions often remain invisible for years until an active failure meets them.

The case shows how cost pressure acts precisely on latent conditions. It rarely leads someone to make a dangerous decision deliberately. It leads to shorter checks, patchier documentation, and quieter concerns. Each of these changes seems justifiable on its own. Together they make the holes grow.

Two readings: corporate purpose or the way engineers work?

In research there are two readings of where the deeper cause lies. Both draw on the same reports but place the emphasis differently.

Clarke (2020) sees the cause in a narrow idea of the company's purpose, under which shareholder value takes precedence over all other goals. The priority of bringing the 737 MAX to market quickly rather than thoroughly safeguarding the software is, for him, an example of this. Dekker, Layson, and Woods (2022) look more closely at the work itself. They argue that engineers often internalize the pressure for cost, efficiency, and schedule themselves, out of pride in their work and the ambition to do more with less. Their pointed conclusion: if engineers need special protection and moral encouragement to raise concerns, then the core of their profession, namely testing, checking, and questioning, has already been lost.

I consider the second reading the more instructive one for small businesses. The first describes a problem of listed corporations. The second describes something that happens in every workshop: people who, out of loyalty and ambition, skip a check because the deadline is pressing.

Quality safeguards: what is non-negotiable under pressure

For a small business, the case does not imply a duty to build large quality systems. It implies something simpler: certain rules must be set in advance so that they are not negotiated in the moment of pressure. I call them safeguards. They are created in four steps.

1. Name the critical steps

   For each service, define which two or three work steps determine safety or function, such as a leak test, a torque setting, or an acceptance check.

2. Make them non-negotiable

   Put in writing that these steps are not dropped even under time pressure. Anyone who skips them breaks a rule, not a recommendation.

3. Grant a right to stop

   Give everyone who carries out a critical step the explicit right to halt the work if something is not right, without fear of disadvantage.

4. Document deviations

   If a part is opened, changed, or reworked, this is recorded and checked by a second person. The 2024 case shows what happens when such documentation is missing.

What good checklists look like and why they protect experienced professionals in particular from errors is described in Checklists in the business. Why recurring errors almost always go back to conditions in the process is shown in Errors as a process signal.

What follows beyond the individual case?

The case shows a second lesson that goes beyond technology: how information is handled toward customers and regulators helps determine how large the damage becomes. The reports describe that the regulator and airlines were inadequately informed about how MCAS worked. For a small business this means: if you keep quiet about a change to a product because it might raise questions, you only shift the problem to the customer.

A second conclusion concerns your own organization. Concerns need a way to be heard before they become reports from outside. What the law on whistleblower protection requires is described in Whistleblower protection. How companies should communicate after an incident is covered in Deny, justify, deflect. How similar patterns in handling bad news brought down a market leader is shown in the case study Nokia.

The limit of this transfer should be stated openly. An aircraft manufacturer works under conditions hardly comparable with a trade business. The mechanisms by which pressure acts on checks and documentation are the same, however.

How to get started

• Name the two or three critical checks for your business's most important service.
• Put in writing that these steps are not dropped even under deadline pressure.
• Tell the team explicitly that anyone may halt work if a critical step is not certain.
• Check whether rework and changes to parts are documented and confirmed by a second person.
• After the next error, don't first ask who made it but which protective layer should have caught it.

Conclusion: how cost pressure changes the quality culture

The guiding question was how time and cost pressure can change an organization's quality culture and what a small business can do about it. The public reports on the 737 MAX show no single act of misconduct but an interplay of schedule pressure, economic incentives, lack of transparency, and weakened controls, on the manufacturer's side as well as the regulator's. The Swiss cheese model explains why these latent conditions remained invisible for a long time until they met active failures.

For a small business the answer is simpler than for a corporation. Critical checks must be set in advance and be non-negotiable under pressure, and anyone who raises concerns must get thanks rather than trouble for it. Quality is not what a business delivers in quiet weeks but what it does not leave out even in its busiest week.