The $5 Million Napkin

In 1980, a young entrepreneur named Richard Branson was preparing to launch Virgin Atlantic’s predecessor airline operations, but decades later, another airline story would illustrate the power of a simple question. In 1987, Southwest Airlines was preparing to compete with major American carriers that had far greater resources. Its advantage was not a fleet of luxurious aircraft or an extensive network of international destinations. It was a relentless focus on keeping flying simple and inexpensive. One of the most revealing decisions in its history concerned something that many airlines considered essential: the elaborate services and extras offered to passengers.

Southwest’s founders, Herb Kelleher and Rollin King, had built the airline around a relatively straightforward idea: make short-distance air travel affordable and convenient. Rather than attempting to imitate established carriers in every respect, Southwest concentrated on what its target customers valued most. Its operations relied on a simplified fleet, quick aircraft turnarounds, and a route network designed around relatively short flights. These decisions were not glamorous, but they helped the airline control costs and keep fares competitive.

The strategy challenged a common assumption in business: that a company must offer more to be worth more. Airlines traditionally competed through amenities, elaborate service classes, and increasingly complex networks. Southwest took a different approach. It recognized that many passengers were not choosing an airline because they wanted a more elaborate flying experience. They wanted to reach their destination reliably without paying more than necessary. Every additional service had to justify the expense it introduced. If a feature did not contribute enough value to the customer, the company had reason to question whether it belonged in the business at all.

This philosophy extended beyond individual services. By standardizing much of its fleet around one aircraft family, Southwest reduced the complexity associated with training pilots, maintaining different aircraft types, and managing spare parts. By emphasizing short-haul travel and rapid turnarounds, it sought to keep its aircraft productive rather than allowing them to spend excessive time on the ground. These decisions reinforced one another. The airline was not simply cutting costs wherever possible; it was designing an operating system in which many of its choices supported the same objective.

The important distinction is between reducing costs and eliminating waste. Cutting an expense that customers genuinely value can weaken a business. Removing complexity that contributes little to the customer experience can make the business both cheaper and better. The challenge is knowing which is which. A company that blindly reduces spending may damage its product, while a company that adds features without considering their costs may create something impressive but commercially unsustainable. The most effective decisions begin with a clear understanding of what customers actually need.

This principle applies far beyond aviation. A software company does not necessarily need dozens of features if most users depend on only a handful. A university course does not become better simply because it contains more assignments. An engineering design does not become superior merely because it uses more components. In each case, complexity can disguise a failure to identify the real objective. The question is not how much a company can provide, but how much of what it provides genuinely matters.

Southwest’s history demonstrates the competitive value of making deliberate choices about what not to do. Its success was not built on offering every service its rivals offered, but on developing an operating model suited to a specific promise: affordable, straightforward air travel. That promise shaped decisions about aircraft, routes, schedules, and costs. The broader lesson is that a business becomes more effective when its decisions reinforce a clear purpose rather than attempting to satisfy every possible expectation. Before adding another feature, service, or layer of complexity, an organization should ask a simple question: Does this make us better at what we are actually trying to do, or does it merely give us more to do?