Complexity catastrophes help explain why bureaucracy seems to grow with the tenacity of weeds. Many companies go through bureaucracy-clearing exercises only to find it has sprung back a few years later. No one ever sits down to deliberately design a bureaucratic muddle. Instead, bureaucracy springs up as people just try to optimize their local patch of the network: finance is just trying to ensure that the numbers add up, legal wants to keep us out of jail, and marketing is trying to promote the brand. The problem isn’t dumb people or evil intentions. Rather, network growth creates interdependencies, interdependencies create conflicting constraints, and conflicting constraints create slow decision making and, ultimately, bureaucratic gridlock. ... How could one of the world’s greatest corporations, a company with billions of dollars in assets, with hundreds of thousands of talented employees around the world, and with Nobel Prize–winning technical research, lose out to a teenager with pocket money from his stamp collection? We can speculate that as Dell began eating into IBM’s PC market share in the early 1990s, some smart person in IBM must have said, “Customers seem to like buying computers through the mail and Dell is growing fast—why don’t we sell computers through the mail?” Selling computers through the mail was certainly not beyond the capabilities of IBM; it could buy boxes and bubble wrap and put things in the mail as well as anyone else. So why did the company wait until several years after Dell had passed it in market share to begin selling computers directly to its customers? The reason is that IBM fell prey to a complexity catastrophe.