A Victim of Its Own Success
By the dawn of the 1960s, IBM was the undisputed king of business computing. But its kingdom was a chaotic mess. The company sold a sprawling portfolio of different computer models, and almost none of them could talk to each other. Each machine was a technological
island with its own unique software and peripherals. This created a nightmare for customers. Upgrading to a more powerful IBM machine meant throwing out all existing software—programs that were expensive and time-consuming to create—and starting from scratch. This incompatibility also created a massive internal headache, requiring IBM to support multiple, entirely separate product lines, a strategy that was becoming financially unsustainable. Watson Jr. recognized that this fragmented approach was a dead end. IBM was choking on its own success, and a revolutionary change was needed.
The All-or-Nothing Proposal
In 1961, a secret task force was formed to map out the future. The solution they proposed was radical: scrap everything. IBM would cease production of all its current, highly profitable computer lines and replace them with a single, unified family of machines. This new line, which would become the System/360, was built on a groundbreaking concept: compatibility. For the first time, a customer could buy a small, entry-level model and, as their needs grew, upgrade to a larger one without changing a single line of code. The name '360' was chosen to signify that it could cover the full circle of user needs, from scientific to commercial. It was a brilliant idea that addressed the biggest pain point for customers, but bringing it to life would require a feat of engineering and a level of investment never before seen in a private venture.
$5 Billion Gamble
Thomas Watson Jr. didn't just approve the System/360; he championed it. He committed an estimated $5 billion to its development—an astronomical sum equivalent to roughly $50 billion today. To put that in perspective, it was more than the cost of the Manhattan Project and, at the time, double IBM's annual revenue. Watson Jr. was literally betting the company. If the System/360 failed, there was no Plan B; IBM would be finished. The decision was met with fierce internal debate and what one expert called “tribal warfare” within the company. Many executives thought it was insane to kill off existing, profitable products for an unproven concept. The software development, in particular, became notoriously difficult, falling years behind schedule and inspiring Fred Brooks's famous book on project management, "The Mythical Man-Month."
A Legacy of Compatibility
On April 7, 1964, IBM announced the System/360 to the world. The response was immediate and overwhelming. Orders flooded in, far exceeding forecasts. Within the first month, more than 1,000 systems were purchased. Watson's gamble had paid off spectacularly. The System/360 didn't just save IBM; it transformed the entire industry. It established the 8-bit byte as a standard, separated software from hardware, and created the very idea of a computer 'platform' that third-party companies could build upon. It secured IBM's dominance in the mainframe market for the next two decades and became the backbone for everything from banking systems to airline reservations. The architecture was so robust that its direct descendants are still in use today, running code written over 60 years ago.
