Washington Mutual’s collapse wasn’t a surprise. The information was there. The system rejected it.
In April 2008, as Washington Mutual’s problems were becoming impossible to ignore, shareholders confronted the board directly. One investor challenged directors about what the company knew and when it knew it, pointing to evidence that concerns about the housing market and the bank’s exposure had been discussed years earlier.
It was an uncomfortable question. If the risks were known as early as 2005, why did nothing change?
The conventional answer is familiar. Washington Mutual took excessive risks. Executives chased growth. Compensation systems rewarded loan volume. The board failed to provide effective oversight.
All of that is true, but none of it fully explains what happened.
Because buried within most accounts of Washington Mutual’s collapse is a more important fact: the risk management function raised concerns. The warnings existed. The organization knew more than its eventual outcome would suggest.
That observation shifts the question entirely. The real question is not why nobody saw the danger, it’s why a system that saw the danger failed to respond to it.
The Information Existed
Washington Mutual’s failure was not a failure of information generation.
Risk professionals identified concerns about underwriting practices, loan quality, and exposure to a deteriorating housing market. The signals were present. The warning lights were functioning.
What failed was everything that happened after the information was produced.
This distinction matters because organizations rarely fail because nobody recognized the problem. More often, the problem was recognized, documented, discussed, and elevated. Failure occurs when the system surrounding that information is unable or unwilling to act on it.
Organizations spend enormous resources building mechanisms to identify risk. They create reporting structures, audit functions, compliance teams, dashboards, committees, and escalation processes.
Those mechanisms matter, but they are only half the system. The more important question is what happens after the information arrives.
What the System Was Actually Built to Do
Washington Mutual’s incentive structure was optimized for growth.
Compensation systems rewarded loan production. Performance metrics emphasized volume. Market expectations were tied to continued expansion.
This is often described as a culture problem, but it is more accurately understood as an organizational design problem.
The dynamic is easier to understand than to resist. When a system is built to reward one outcome, any information that threatens that outcome encounters friction. Not necessarily because people are dishonest. Not necessarily because leaders are reckless. Often because responding to the warning carries costs that continuing the strategy does not.
Slowing loan growth threatened compensation, market expectations, analyst forecasts, competitive positioning, and short-term financial results. In that environment, minimizing risk warnings can become the path of least resistance, not because the warnings are wrong, but because the system has made acting on them harder than explaining them away.
There is a further dynamic that makes this kind of organizational paralysis so durable. The psychologist Steven Pinker describes a condition he calls common knowledge: when everyone knows that everyone else knows something, but no one names it, silence becomes a shared performance rather than an individual choice. At Washington Mutual, the housing exposure was not a secret. The deteriorating loan quality was not invisible. It had been discussed in board committees. It was present in the risk reports.
What common knowledge explains is why that shared awareness produced no action. Once it becomes understood that the organization is leaning one way, the cost of dissent changes. Speaking up no longer feels like adding information to a discussion. It feels like defying a collective. And when defying the collective carries personal cost while staying quiet does not, the rational choice becomes silence, even for people who know better.
The warnings did not disappear. They were processed by a system that was structurally incapable of giving them the weight they deserved.
When the system is built to reward one thing and the risk function identifies a threat to that thing, the system does not neutralize itself.
It neutralizes the warning, and that is a very different failure than simple negligence. It is a systems failure.
The Board Question
Many postmortems ask where the board was during Washington Mutual’s downward spiral.
A more useful question is what information the board was receiving, in what form, from whom, and what the system made easy or difficult to say in that room.
Boards can only govern the reality they can see.
The challenge is that directors rarely encounter raw organizational reality. They encounter a filtered version of it. Dashboards, executive summaries, presentations, scorecards, and management reports all compress information. Every layer of reporting shapes the picture that ultimately reaches decision-makers.
The critical governance question is not whether directors are intelligent enough to recognize risk. It is whether the information reaching them still resembles reality by the time it arrives.
Common knowledge operates here too. When the board knows that management knows the numbers are optimistic, and management knows the board knows, and both parties continue operating within that shared understanding without naming it, the loop is complete. Governance becomes a performance rather than a function. The board is not failing to see the problem. It is participating, often without recognizing it, in a system that has made the problem unspeakable.
A leader’s role, in that moment, is to name what everyone knows but no one has said. Once a truth is on the table, the system can work on it. Until then, the system works around it.
Washington Mutual never had that moment until it was too late.
What This Means for Leaders Today
The lesson is not limited to banks.
Every leadership team should ask three questions:
First, when the risk function disagrees with the operating teams, what happens? Is there a mechanism that ensures those disagreements reach decision-makers? Or are they resolved below the level where meaningful decisions are made?
Second, what does the compensation structure reward? If the answer is volume, speed, growth, or short-term performance metrics, the organization may be systematically selecting against the people most likely to raise long-term concerns.
Third, what does it actually cost someone to deliver bad news? Not what the policy says. What has happened historically to people who challenged assumptions, questioned forecasts, or raised uncomfortable concerns? That history is the organization’s real policy. Employees learn far more from observed consequences than written values.
A fourth question sits beneath all three: does your organization have a mechanism for breaking the loop? Not a values statement. Not an open-door policy. A structural mechanism that makes it possible for someone to name what everyone already knows, without that act becoming a career-defining risk.
The Inside Advantage
Washington Mutual did not lack smart people. It did not lack a risk function. It did not lack information. It lacked the organizational infrastructure necessary to act on what it already knew.
The common knowledge loop that kept the warnings from gaining traction was not inevitable. It was a product of a system that made silence rational and dissent costly. That system was a design choice, even if no one made it deliberately.
The organizations that build a genuine inside advantage are not the ones that avoid bad news. They are the ones that design their systems so bad news can travel, so the loop can be broken before it closes completely, and so a leader can name what everyone knows without it feeling like an act of defiance.
By April 2008, the warning had finally reached a room where it could no longer be filtered. Unfortunately, that room was the shareholder meeting.

Leave a comment