Why Good Companies Break Under Pressure

Capable organizations rarely fail from weakness. They fail when pressure gets misread, and the break runs along the grain of their strengths.

Corporate failure has a standard story shape. The company got complacent. Leadership stopped listening. Somebody cut corners because they stopped caring about the work. The story is satisfying because it locates the failure in a defect, and defects can be avoided by not having them. Read the actual record of the most instructive corporate breakdowns of the last two decades, though, and the story stops holding. The companies that produce the most spectacular failures are rarely the mediocre ones. They are disciplined, admired, and full of people trying hard, right up to the moment the damage becomes public.

So let me state the position plainly:

Good companies do not usually break because pressure exceeds their strength. They break because pressure enters the organization carrying real information, gets translated into internal demands that no longer carry that information, and then gets routed through whatever the company does best.

The strength executes. The signal is gone. What breaks is not the weakest part of the company but the part that was working hardest.

That claim needs evidence, because on its face it sounds like a consultant’s paradox. So let me walk through two of the best-documented corporate failures on record, not as morality tales but as mechanism. Both have something rare: thorough, public, independent investigations that let us see what the pressure actually did on its way through the building.

1. The bank that sold itself apart

For two decades, Wells Fargo was the bank other banks were told to emulate, and the center of its reputation was cross-selling: the discipline of deepening each customer relationship by adding products, checking to savings, savings to credit card, credit card to mortgage. The ambition had a slogan, “going for gr-eight,” eight products per household, and the company’s ability to execute on it was treated by analysts as evidence of a superior sales culture.^[1]

Then, in September 2016, regulators announced $185 million in fines because employees had opened millions of accounts customers never asked for. The bank’s own later review put the number of potentially unauthorized accounts at roughly 3.5 million.^[2] Thousands of employees had been fired over sales integrity issues across the preceding years, which means the behavior was not hidden from the company. It was being processed by the company, as a disciplinary matter, one employee at a time.

Now look at where the pressure came from and what happened to it in transit. The external signal was real: retail banking margins were compressing, and deepening existing relationships was a legitimate strategic answer. At the top of the company, that is what the pressure meant. But by the time it reached a branch in Phoenix or Newark, it had been translated into a daily sales quota, tracked on scorecards, read out on conference calls, with district managers ringing branches multiple times a day for numbers. The board’s investigators were precise about this: the problem was not that goals existed but that the goals were, in their words, unattainable in many markets, and that the culture treated missing them as a personal failing rather than as information about the goal.^[3]

A teller opening a phantom savings account was not confused about ethics. She was responding accurately to the pressure that actually reached her, which was no longer “deepen customer relationships” but “produce eight by Friday or explain yourself.” The original signal, margin compression and a strategy to answer it, had been stripped somewhere around the regional level. What remained was demand with no meaning attached, and demand with no meaning attached gets satisfied by whatever means the local environment permits.

And notice the channel it ran through. Wells Fargo’s sales machine was not a flaw that ethics training failed to catch. It was the company’s crown jewel, the most developed, most measured, most celebrated capability in the building. The pressure did not find the weak spot. It found the strong one, because the strong one is what an organization reaches for when it is told to produce.

2. The airplane the schedule built

The Boeing case runs on the same mechanism at higher stakes.

In late 2010, Airbus launched the A320neo, a re-engined version of its bestselling narrow-body, and began taking orders at a pace that threatened the 737’s franchise, including at American Airlines, a customer Boeing had held for decades. Boeing faced a genuine strategic fork: spend roughly a decade designing a clean-sheet aircraft, or re-engine the 737 and get to market fast. It chose the 737 MAX, and with that choice came a constraint that shaped everything downstream: the new plane needed to fly like the old one, so that airlines would not need to put pilots through expensive simulator retraining.^[4]

The larger engines changed the aircraft’s aerodynamics in certain conditions, and the engineering answer was MCAS, software that would adjust the plane’s pitch behavior so it handled like its predecessor. Along the way, MCAS’s authority was expanded, its reliance on a single angle-of-attack sensor was retained, and references to it were minimized in materials pilots would see, all in service of the governing constraint: no new type rating, no schedule slip. The House investigation documented the internal weather this produced, including a program culture employees described as schedule-driven, countdown clocks in meeting rooms, and engineers reporting pressure not to raise issues that could slow certification.^[5] Two crashes, Lion Air Flight 610 in October 2018 and Ethiopian Airlines Flight 302 in March 2019, killed 346 people and grounded the fleet worldwide.

It matters that Boeing was, by any reasonable account, one of the finest engineering organizations in the world. The people who built the MAX were not careless, and the investigations do not describe carelessness. They describe an organization faithfully executing the constraint that had been handed down, long after the constraint had detached from the signal that justified it. The external pressure said: Airbus is taking the market, respond or lose it. By the time it reached the engineering floors, it said: the schedule and the no-retraining commitment are fixed, fit everything else around them. Engineers optimized brilliantly inside a frame nobody at their level had the standing to question. The excellence was real. It was pointed at the wrong invariant.

The same signature appears in the General Motors ignition switch record, where the Valukas investigation found engineers categorizing a stalling defect as a customer convenience issue for years, inside a culture famous for cost discipline and for meetings where everyone nodded and nothing moved.^[6] Different industry, same translation failure.

3. The mechanism, stated plainly

Strip the details and the pattern repeats in three segments:

• First, the pressure is real and external, and at the top of the organization it is legible. Wells Fargo’s leadership could read margin compression. Boeing’s could read the A320neo order book. The failure never begins with a false signal. It begins with a true one.

• Second, the signal gets converted into an internal proxy, a quota, a schedule, a fixed constraint, and the proxy travels down the hierarchy while the reasoning stays at the top. Each layer passes on the demand and, usually without intending to, strips a little more of the meaning. Three or four levels down, people are no longer responding to the market. They are responding to the artifact, and the artifact has stopped being information and become weather.

• Third, the organization routes the demand through its most developed capability, because that is what capabilities are for. A sales culture sells its way to the number. An engineering culture engineers its way to the deadline. A cost culture categorizes its way around the expense. Danny Miller documented this trajectory across dozens of firms three decades ago and called it the Icarus paradox: outstanding companies extend their defining strength until it becomes the instrument of their failure.^[7] What Miller framed as strategic momentum, the investigation records let us see at ground level, as thousands of individually reasonable responses to pressure that no longer said what it meant.

This is why the break runs along the grain of the strength. A capable organization under misread pressure does not stop executing. It executes the misreading.

4. What it looks like from the inside

I want to bring this down from the scale of congressional reports, because the mechanism does not require a Fortune 500 balance sheet. I have run it myself.

Years ago I led an engineering organization with a shipping discipline I was proud of. We hit dates. It was our identity, the thing new hires were told about in their first week, and for a long time it served us, because our dates were promises to real customers with real integration schedules. Then a year arrived that carried a different kind of pressure: a strategic partner wavering, a competitive announcement we had not expected, revenue math that suddenly had our product in the load-bearing column. I did what the mechanism predicts. I translated all of that into the one language my organization spoke fluently: the date holds.

We hit the date. We also shipped a release I spent the next two quarters apologizing for, burned out two of my best engineers, and taught the team a lesson I then had to spend a year unteaching, which is that raising a risk near a deadline was an act of disloyalty. Nobody in that building lacked skill or commitment. They executed my translation flawlessly. The failure was mine, and it was specifically a reading failure: I passed down the weight of the pressure and kept the meaning in my own head, where it helped no one.

The postmortem we wrote at the time blamed estimation. Most postmortems in most companies blame the equivalent. It took me years to see that we had misdiagnosed our own incident, and that the real sequence was the same one the investigators found at Wells Fargo: true signal in, proxy down, strength executes, break.

5. The incentive objection

There is a tidy takeaway available at this point in the argument, and it is worth pausing to decline it. The tidy version says: these are incentive stories. Wells Fargo paid people against a bad quota; Boeing’s program rewarded schedule; fix the incentive design and the mechanism dies. Incentives were implicated in both records, and no serious reading absolves them. But the incentive frame, taken as the whole explanation, misses the part of the mechanism that will actually recur in your organization in three ways:

1. First, the incentive structures in these cases were not exotic. Sales targets with scorecards and consequences exist in essentially every retail bank on earth, and schedule commitments with careers attached exist in every engineering program. Thousands of organizations run comparable incentive machinery without producing comparable disasters. The differentiating variable in the documented cases was not the existence of the pressure but what happened when the target collided with reality: whether the collision produced information that traveled, or silence that compounded. The board report’s most damning Wells Fargo finding is not that goals existed but that years of evidence about their unattainability failed to move them.^[8] The incentive was the engine. The failed feedback path was the crash.

Second, the incentive frame implicitly predicts that people without incentive exposure would have behaved differently, and the records say otherwise. Boeing’s engineers were not on commission. GM’s engineers had no bonus riding on the ignition switch classification. What they had was an accurate reading of what their organizations wanted to hear, which is a stronger and subtler force than any payout table, because it operates on everyone, including the people designing the payout tables.

Third, and most practically: organizations that respond to these cautionary tales by re-engineering compensation, as Wells Fargo did when it eliminated retail sales goals outright in late 2016, have fixed the last failure’s proxy without touching the proxy-generating machine. New pressure will arrive next year, be translated into some new internal artifact, and travel down the same meaning-stripping pipeline, unless the pipeline itself is rebuilt. The incentive is a parameter. The translation layer is the system.

Translation autopsy

The test I now apply, and recommend, is a translation autopsy on your own near misses. Find a recent case where a target and reality came into conflict anywhere in your organization, a date that could not hold, a number that could not be hit, a commitment that turned out to be wrong. Then trace, person by person, what happened to the information. Where did it surface first? How many levels did it climb before someone acted on it, and how long did each hop take? Was the eventual resolution driven by the information arriving, or by the failure arriving? You will learn more about your company’s real pressure system from one honest autopsy than from a year of engagement surveys, because you will be watching the exact machinery that decides, when your turn comes, whether you get the Wells Fargo trajectory or a Tuesday-afternoon course correction.

6. Reading before routing

If the mechanism is translation failure, the countermeasures are about preserving meaning in transit, and they are unglamorous.

Pass the why with the what. Every time a demand moves down a level, the source travels with it or the signal dies. This is not a communications nicety. At Wells Fargo, the difference between “margins are compressing, and deeper relationships are our answer” and “eight products per household” turned out to be worth about three billion dollars in fines and settlements, and a fair amount of the difference lived in that gap.

Treat widespread misses as data about the target. The Wells Fargo board report is unsparing on this point: when thousands of people fail or cheat against the same goal, the goal is the finding.^[9] An organization that reads mass shortfall as mass weakness has turned off its own ears.

Watch the cost of dissent as pressure rises. In every record cited above, the information needed to prevent the failure existed inside the company years before the public ever heard of it. What failed was the path that information needed to travel upward, because the price of carrying bad news climbs exactly when the news matters most. The practical question for a leader is not “do people feel comfortable speaking up,” which is easy to answer optimistically, but “when did someone last change my mind at a moment when changing my mind was expensive.”

Name what you are best at, and audit what you are asking it to do. Your strongest capability is your default router. When new pressure arrives, it will be handled by that capability unless you deliberately decide otherwise, and the decision has to be deliberate because the routing is automatic.

None of this reduces the pressure, which is worth being clear about because pressure reduction is what most organizations reach for and it addresses the wrong variable. Wells Fargo’s margin problem and Boeing’s Airbus problem were not removable. The variable that was actually in play, at every level of both companies, was whether the pressure stayed readable as it moved.

That question, what pressure does as it travels through a system of people, and what determines whether it arrives as information or as raw force, is the one I keep returning to. The record says capable organizations fail at it routinely, which suggests the capability involved is neither obvious nor natural. It has to be noticed, named, and built, which is the work Pressure Intelligence™ exists to do. Naming what the pressure is carrying is where it starts.

Mark D. Benson