The Great Molasses Flood of 1919 killed 21 people, injured 150 more, and was almost entirely preventable. The warning signs were there for years -- ignored, dismissed, or overruled by management. For continuous improvement practitioners, the disaster reads as a case study in everything a safety culture is supposed to prevent: untested designs, ignored frontline concerns, substandard materials, missing inspection, and a leadership team that confused absence of failure with proof of safety. Here are five lessons that translate directly to modern operations.

Like many other tragic disasters, this one was entirely preventable. As is often the case, no single decision of factor alone was responsible for the catastrophe that left Boston smelling like molasses on hot summer days for decades. 

A look at the circumstances leading up to the flood reveals that leaders at Purity Brewing Company made the same kinds of mistakes common in organizations today. 

The Tank

The Purity Distilling Company had two good reasons for building an enormous molasses storage tank. Molasses can be fermented to produce ethanol, a key ingredient in both alcoholic beverages and munitions. Demand for both was enormous. World War I increased the need for commercial alcohol, and prohibition was coming. (The 18th Amendment was passed the very next day after the accident.)

Built hastily in 1915, the tank stood 50 feet tall and 90 feet in diameter. It had problems from day one. The container groaned when operators added new molasses, the paint peeled, and the tank leaked onto the street with enough frequency that neighborhood residents treated it as a feature rather than a defect. Families came to the site to fill bottles for home use. Children scooped the leaked molasses to make their own candy. None of this triggered an investigation.

Although Purity had poured molasses into the container 29 times, only four of those refills came close to capacity. The fourth happened two days before the disaster when a ship arrived from Puerto Rico carrying 2.3 million gallons of molasses. At that point, the tank held enough molasses to fill three and a half Olympic-sized swimming pools.

The Flood

On January 15, 1919, the temperature rose above 40 °F, unusual for a Boston winter and much warmer than the previous days' frigid temperatures. The fresh shipment of molasses was warmed to lower its viscosity for transfer. Likely due to the older cold molasses' thermal expansion, the tank burst at approximately 12:30 pm. 

The collapse resulted in a 25-foot-high wave of molasses moving at 35 miles per hour. The force was sufficient that the Boston Globe reported that the molasses wave caused buildings to "cringe up as though they were made of pasteboard."

The Mistakes

While there was some initial speculation that a bomb had caused the explosion, modern analysis supports the conclusion that the incident resulted from thermodynamics and a series of bad decisions. There is a benefit for today's leaders in thinking about how their organization may be making similar mistakes.

Lesson 1: Test changes on a small scale before deploying them

When Purity first put the tank into use, engineers recommended filling it first with saltwater to ensure there were no leaks and that the tank would hold up under pressure. This advice was ignored due to the extra cost and time required. 

The same pattern shows up in modern organizations as skipped pilots. A new process is rolled out across all sites without testing it in one. A software change ships to all customers without a controlled release. A staffing model is deployed system-wide rather than in a trial. PDSA exists specifically because the alternative is the molasses tank scaled to a different industry.

Lesson 2: Treat early warning signs as data, not noise

The tank leaked almost from the beginning; rather than looking for the root cause or trying to eliminate the resulting waste, management at Purity calculated that the waste of molasses did not outweigh the cost of solving the problem. Instead of fixing the leaks, they painted the tower brown to make the problem less apparent. Visualization is a powerful tool, but it works both ways. It can either highlight issues or cover them up.

Modern equivalents are everywhere. The leaking pipe that maintenance keeps patching rather than replacing. The error message in the production logs that nobody investigates because the system stays up. The patient safety event was categorized as a "near miss" and filed away. Warning signs are data only when an organization has a system that treats them that way -- otherwise, they're just noise that everyone learns to ignore.

Lesson 3: Don't let cost pressure override material specifications

In 2014, an investigation using modern engineering analysis found that the steel was half as thick as it should have been for a tank of its size, even by the lax standards of the day. The tank also lacked manganese, making it more brittle. On top of that, the tank's rivets were also apparently flawed—the first cracks formed at the rivet holes. 

The Boeing 737 MAX MCAS failure, the Texas City refinery explosion, the Therac-25 radiation overdoses -- each had a thread of cost or schedule pressure overriding technical judgment. The molasses tank wasn't unique. It was an early entry in a long pattern.

Lesson 4: Build the psychological safety for frontline concerns to reach decision makers

Mark Rossow is a civil engineer and professor emeritus at Southern Illinois University in Edwardsville, who has written about the molasses flood. He writes that "When a laborer brought actual shards of steel from the tank's walls into the treasurer's office as evidence of the potential danger, he replied, 'I don't know what you want me to do. The tank still stands." 

The laborer in this story had the evidence in his hand. He brought it to the person who could act. Nothing changed. Modern equivalents play out every day in hospitals, factories, and offices where frontline workers can see a problem clearly, but the system above them isn't set up to receive what they're trying to say. Psychological safety isn't a soft skill -- it's the mechanism by which information about real risk reaches the people who can do something about it.

Lesson 5: Involve domain experts before the failure, not after

Speaking of the treasurer, the tank project was overseen by Arthur Jell, USIA's treasurer. He had no architectural or engineering experience. Financial concerns were prioritized over technical and safety ones. The results speak for themselves. 

Putting financial leadership in charge of technical decisions has a recognizable cadence. Decisions get made faster. Budgets stay tighter. Outcomes look better on paper -- right up until they don't. The fix isn't to keep technical experts from the budget; it's to make sure the people with technical authority have a voice that endures when they disagree with those with financial authority.

Following the disaster, the victims filed 119 lawsuits against Purity's parent company, United States Industrial Alcohol. The cases against USIA were combined into a single legal proceeding that ran for five years. In April 1925, state auditor Hugh W. Ogden ruled that United States Industrial Alcohol was responsible for the disaster, citing poor planning and lack of oversight. USIA was ordered to pay the victims and their families $628,000 in damages -- roughly $8 million in today's dollars. The settlement was, by every reasonable measure, smaller than what the company saved by skipping the saltwater test, ignoring the leaks, using cheaper steel, and overruling the laborers who tried to warn them.

What a Modern Management System Would Have Caught

Every failure in this disaster has a modern countermeasure. A standard inspection schedule with documented criteria would have made the tank's deterioration measurable. Regular Gemba walks would have surfaced the visible leaks long before they became routine. An idea management system would have given the laborer with the shards of steel a path to the right decision-maker, with a tracked response. A3 problem-solving on the early warning signs would have produced corrective action rather than a coat of brown paint.

None of this is hindsight. The tools to prevent disasters like the one in 1919 have existed in some form for decades. What's changed is that we now have the infrastructure to deploy them at scale -- to make sure that the next person who shows up at the treasurer's office with shards of steel doesn't get told: "The tank still stands."