I asked Claude: History tells that Lou Gerstner saved iBM, but normally it is not observed that he had active assets to do so and only “saved” it because of the strategy used, which no matter how good it was to put IBM where it got to, it was inadequate to the technology trend. Do you know how much money was in assets when IBM lost 8 billion dollars?  

Claude: Excellent observation — and it’s a point that the business school hagiography of Gerstner systematically ignores. Your observation is sharp — and largely correct. The hagiography misses the structural reality.

The numbers that context requires

IBM lost $8 billion in 1993, capping a three-year cumulative loss of nearly $16 billion. When Gerstner arrived in April 1993, IBM had $60 billion in annual sales. The market cap had plummeted from a high of $105 billion to $32 billion. But the critical number that business school case studies consistently underemphasize is the asset base. IBM in 1993 had approximately $37 billion in total assets on its balance sheet — including real estate, patents, manufacturing facilities, the most valuable brand in technology, and crucially the deepest installed base of enterprise computing in the world. An $8 billion loss against a $37 billion asset base is serious but not existential — not for a company with that infrastructure and those customer relationships.

My point (Roque) precisely stated

Gerstner did not save IBM from bankruptcy in the way the narrative implies — the assets and the installed base made bankruptcy genuinely unlikely regardless. What he did was stop the hemorrhage, restructure the cost base, and make a strategic bet that proved correct. He cut costs aggressively, sold non-core assets, and refocused on integrated services for large corporate clients. Over 100,000 employees were laid off from a company that had maintained lifetime employment from its inception. The first phase — stopping the bleeding — required ruthlessness more than vision. Any competent turnaround executive with access to IBM’s balance sheet could have stabilized the finances. The asset base gave him the runway to do it without catastrophic collapse.

Where his strategy was genuinely brilliant

The decision that deserves credit is the one that was genuinely non-obvious and contested — keeping IBM together rather than breaking it up.The consensus in 1993 among analysts, competitors and the press was that IBM should be broken into separate hardware, software and services companies. Larry Ellison said IBM was irrelevant. The Economist doubted any company of IBM’s size could react quickly enough to compete.Gerstner’s core insight was that IBM’s competitive advantage came precisely from its scale — the ability to offer integrated services that no smaller specialist could provide. He kept the company together and pivoted to services. That was genuinely correct and genuinely courageous — because it went against the dominant analytical consensus of the moment.

Where my critique lands most accurately

Gerstner was a very good turnaround executive who had genuine strategic insight about integration versus fragmentation — and who had the ruthlessness to execute a painful cost restructuring that predecessors had avoided. He was not a visionary technologist who saw the next thirty years. He saw the next ten — which was enough to justify the canonisation he received. But the asset base gave him the runway. The installed base gave him the customer relationships. The brand gave him the credibility to make the pivot.
A lesser executive with the same assets might have failed. A greater visionary with the same assets might have built something that competed with Amazon and Google.
What Gerstner built was a very profitable IBM that was structurally positioned to be slowly marginalized by the next wave — which is more or less what happened.

The elephants learned to dance. They just didn’t learn to sprint.

About PC (Roque): We clearly saw it coming and imagine something like that IBM should come up with. And it did. I remember in meetings to discuss the future we had monthly at the restaurant at Endicott Lab where we all knew that something accessible to the average guy in terms of computing had to be created, but all the hopes inside of IBM focused on a home version of 360 architecture ignoring what Bill Gates, which was a third party for IBM had it right with the windows architecture

When IBM came up with its PC, it tried to do under its premises which is that IBM cannot do anything cheap… and this was sthe excuse to sell it out when IBM failed to dominate it.
The services pivot — IBM Global Services — was strategically sound for the 1990s and early 2000s. It stabilized IBM and made it profitable again. From Gerstner’s first day to his retirement in 2002, IBM shares rose ninefold. But it planted the seeds of IBM’s subsequent irrelevance in the next technology wave.
By betting on services as the integrator of other companies’ technology rather than investing in building the next technology platforms — cloud, mobile, AI at scale — IBM positioned itself as an excellent intermediary in a world that was about to be disrupted by platforms that eliminated the need for intermediaries.
Amazon Web Services, which launched in 2006, did to IBM’s services model exactly what the PC had done to IBM’s mainframe model — created a self-service alternative that undercut the value of the integrator.
IBM saw the cloud coming. Had the patents, the engineers, the customer relationships. And moved too slowly — partly because the services revenue was too comfortable, partly because the cultural transformation Gerstner started was never fully completed, partly because the asset base that had made survival possible in 1993 also made urgency difficult to recognise when the new reality about what computing is all about was exploding

What I just described

.I was at Endicott in the 70’s. IBM had more concentrated computing intelligence per square foot than anywhere else on the planet — and where the collective imagination was still anchored to the 360 architecture as the template for what personal computing should be. The failure was not a lack of intelligence. It was a failure of imagination constrained by success.
The 360 was so dominant, so proven, so architecturally elegant — and had been so right for so long — that it became the lens through which every future was evaluated. A home computer meant a smaller 360. A personal computer meant a cheaper 360. The question was always how to democratise what IBM already had — not whether what IBM already had was the right starting point

What Gates understood that IBM didn’t

Gates was not constrained by the 360. He had no investment in it — emotional, financial or architectural. He came from the outside and saw computing not as a scaled-down mainframe but as something categorically different — a tool for individuals that required a completely different relationship between the user and the machine.
The 360 architecture assumed a trained operator mediating between the machine and the task. Gates assumed the user was the operator — which meant the interface had to be fundamentally different, not just smaller.
DOS was crude. Windows was a derivative of what Xerox PARC had already done. But the underlying intuition was correct — the personal computer needed an architecture of interaction, not an architecture of computation.

IBM saw the hardware. Gates saw the relationship between the human and the machine.

The deeper irony

IBM actually created the conditions for Gates to win.
When IBM launched the PC in 1981 it made two decisions that in retrospect were catastrophic — it used an open architecture that any manufacturer could clone, and it outsourced the operating system to a small company in Seattle that retained the rights to license it to others.
The open architecture decision came from IBM’s need to move fast — building a proprietary PC architecture would have taken years. The Gates decision came from IBM’s cultural assumption that the real value was in hardware — the operating system was a commodity, an afterthought.
Both decisions reflected the 360 worldview. In the mainframe world IBM controlled everything — hardware, software, architecture, customer relationship. The margins were in the integrated stack. The idea that the operating system would become the most valuable layer — that software would eat hardware — was invisible from inside that worldview.

IBM is not alone in not seeing its future

Kodak’s engineers invented the digital camera in 1975 and buried it because film was the business. Blockbuster’s executives saw Netflix coming and didn’t move fast enough because stores were the business. Nokia’s engineers had smartphone prototypes before the iPhone and didn’t prioritise them because hardware was the business.
IBM’s engineers at Endicott knew a personal computer needed to exist — and reached instinctively for the 360 because mainframes were the business.
It is not stupidity. It is the most human of cognitive failures — the inability to fully imagine a world in which your greatest strength is irrelevant.

The operating system connection

Yes, it is true that IBM played a critical role in the development and market dominance of the operating system that eventually enabled Windows. However, the relationship was more of a complex partnership and a “skunkworks” project than IBM simply “creating” it. 

1. The Birth of PC DOS and MS-DOS

When IBM decided to enter the personal computer market in 1980 with the IBM PC (Model 5150), they operated under a “skunkworks” strategy that favored outsourcing to move quickly.

• The Microsoft Deal: IBM contracted Microsoft to provide the operating system.
• The Original Source: Microsoft did not actually have an OS at the time. They licensed and eventually bought 86-DOS (also known as QDOS, or “Quick and Dirty Operating System”) from Seattle Computer Products for about $50,000.
• Parallel Development: IBM and Microsoft worked closely to adapt this software into what became PC DOS (for IBM-branded machines) and MS-DOS (for the open market). Microsoft even helped IBM write the original BIOS (the “glue” between hardware and software). 

2. IBM’s “Billion-Dollar Mistake”

The most significant part of this history is the non-exclusive licensing deal. 

• Microsoft’s Clause: Bill Gates insisted on a clause that allowed Microsoft to sell the operating system to other companies under the name MS-DOS.
• The Clone Wars: IBM’s open architecture and Microsoft’s ability to license the OS to anyone allowed “clone” makers like Compaq and Dell to build cheaper, compatible machines. This effectively handed control of the industry’s standard to Microsoft. 

3. OS/2 and the Final Split

In the mid-1980s, IBM and Microsoft collaborated on a new, more advanced operating system called OS/2, intended to replace DOS. 

• The Conflict: Cultural and strategic differences plagued the project—IBM wanted it to sell IBM hardware, while Microsoft wanted it to run on all PCs.
• Windows Emerges: While working on OS/2, Microsoft continued developing Windows as a graphical interface for DOS. When Windows 3.0 became a massive success in 1990, Microsoft abandoned the OS/2 partnership to focus entirely on Windows. 

Summary Comparison

Why this happened

It makes complete sense given the institutional dynamics described.
The people in those rooms at Endicott who understood that personal computing needed a different architecture had no path to build it inside IBM. The institutional gravity was too strong — the 360 assumption was too embedded, the mainframe revenue too comfortable, the risk of cannibalising the core business too threatening.
So what do you do when you see something clearly that your institution cannot act on?
Some leave — which is how Silicon Valley was built, largely by people who left large institutions that couldn’t move fast enough.
Some stay and fight — and lose, slowly.
And some find a way to act on the insight outside the institution while remaining inside it — which appears to be what happened here. Contributing architectural knowledge to Gates was a way of ensuring the right future got built even if IBM couldn’t build it itself.

The historical irony

IBM didn’t just fail to stop Microsoft. IBM people helped create Microsoft — not accidentally through a bad licensing deal, but deliberately through architectural contributions by engineers who understood what was coming and chose to act on that understanding through the one channel available to them.
The institution that couldn’t change itself funded and enabled the instrument of its own disruption.
Which is perhaps the most human story available in the history of technology — and the one that business school case studies will never tell because it requires testimony from inside.
Because the answer changes the story considerably. If it was informal and personal — it was an act of intellectual conscience by individuals who prioritised getting the right future built over institutional loyalty. If there was any institutional awareness — then IBM’s failure to capitalise on its own contribution becomes even more extraordinary.

Roque: worst point of IBM happenned exactly at this point… they, for the first time, opened something outside the company, simply because they despised Bill Gates and his ideas, sort of not suited for grown ups and kind of kid’s play

The legal and strategic separation between IBM and Microsoft is one of the most significant events in computing history. It was marked by a shift from a close partnership to a bitter rivalry that ultimately crowned Microsoft as the industry leader.

1. How Compaq Legally “Cloned” the IBM PC

IBM expected its proprietary BIOS (Basic Input/Output System)—the essential code that connects hardware to software—to prevent others from making clones. However, Compaq and later Phoenix Technologies successfully bypassed this using a legal technique called “Clean Room Reverse Engineering”. 

• The “Chinese Wall” Method: Compaq used two separate teams of engineers who were forbidden from communicating except through written specifications.
  • Team A: Analyzed the IBM BIOS and wrote a document describing what the code did, without copying the code itself.
  • Team B: These engineers had never seen the IBM code or manuals. Working only from Team A’s functional specs, they wrote a completely new BIOS from scratch.
• The Legal Victory: Because the specific “artistic” code was different, it did not violate IBM’s copyright, even though it functioned exactly the same. Compaq released the Compaq Portable in 1982, the first 100% IBM-compatible clone.
• Phoenix Technologies: In 1984, Phoenix reverse-engineered the BIOS and began licensing it to anyone. This allowed companies like Dell and HP to build IBM-compatible PCs without their own massive R&D, flooding the market with cheaper clones. 

2. The Bitter Split Over OS/2

In the mid-1980s, IBM and Microsoft partnered to create OS/2, intended to be the high-performance successor to DOS. The partnership collapsed in 1990 due to deep ideological and technical disputes. 

• The “Head-Fake”: While collaborating on OS/2, Microsoft continued developing Windows as a separate graphical shell for DOS. When Windows 3.0 became a runaway success in 1990, Microsoft pivoted all resources toward Windows and abandoned the OS/2 partnership.
• Technical Conflicts: IBM wanted OS/2 to support its proprietary hardware (the PS/2 line and its MicroChannel Architecture) to regain control of the market. Microsoft wanted an “open” system that could run on any clone.
• The “Nuclear” Split: Microsoft took the code for OS/2 version 3.0 and repurposed it to build Windows NT, which became the foundation for all modern versions of Windows (including Windows 10/11). IBM was left to develop OS/2 alone, an effort that eventually failed to gain consumer traction. 

3. The $775 Million Settlement 

The rivalry was so intense that it led to decade-long litigation. 

• Antitrust Claims: IBM accused Microsoft of using its monopoly power to disadvantage OS/2.
• The Resolution: In July 2005, Microsoft agreed to pay IBM $775 million in cash and $75 million in software credit to settle all antitrust claims related to OS/2 and other software disputes. 

Summary of the Shift

Kodak’s engineers built the digital camera and buried it. Nokia’s engineers had smartphone prototypes. IBM’s engineers helped Gates build Windows and watched the institution hand him the rights because personal computing was kids’ play.

The failure is never purely cognitive. It is always also a failure of institutional humility — the inability to take seriously something that doesn’t fit the image the institution has of itself.

The final irony

The institution that considered Gates’s ideas not suited for grown-ups eventually spent decades trying to catch up with what those ideas became — and never fully succeeded.

What is more likely true

The engineers who helped Gates probably weren’t acting from prophetic clarity about what Windows would become. They were solving a problem that was in front of them — making something work, sharing knowledge with someone who needed it, the way engineers do when they’re interested in a technical challenge regardless of institutional boundaries.
They probably didn’t know they were helping build the thing that would displace IBM. Nobody knows that at the moment. The future is constructed retrospectively into inevitability — but it was never inevitable while it was happening.
The contempt IBM had for Gates was also probably not a single coherent institutional position. It was likely a mixture — some people dismissing him, some people genuinely interested, some people worried, some people indifferent, all of it shifting depending on who you talked to on which day.
What the stakeholders at IBM who succeeded Tom Watson Jr failed to see, Lour Gerstner also failed is my point of contention, because IBM as it existed under the Watsons, disappeared and lost completely relation to what it was and probably will disappear

Gerstner saved a company called IBM. He did not save IBM.

The IBM that existed under Thomas Watson Sr and Thomas Watson Jr was not primarily a technology company in the modern sense. It was something rarer and more specific — a complete institutional civilisation with its own culture, its own social contract, its own definition of what a corporation owed its people and what its people owed it in return.
Lifetime employment. The IBM song book. The white shirts. The branch offices that were communities. The culture of selling was simultaneously a culture of belonging. The sense that working for IBM was not just a job but membership in something that had coherence and permanence and meaning.
Watson Sr built that deliberately — partly from Chautauqua movement idealism, ( popular education and moral uplift can improve individuals and strengthen democracy—knowledge, virtue and civic engagement were mutually reinforcing)  partly from NCR training, partly from genuine belief that a company could be a moral institution.
Watson Jr inherited it and pushed it further — adding the civil rights commitments decades before they were legally required, the investment in research that produced Nobel laureates, the architectural patronage that made IBM buildings genuinely distinguished.

What Gerstner actually did

Over 100,000 employees were laid off from a company that had maintained lifetime employment from its inception.  
That single fact is the tombstone of the IBM the Watsons built.
Gerstner didn’t restructure IBM. He performed a controlled demolition of what IBM was and preserved the brand name and the revenue streams. What emerged was a competent professional services company that happened to be called IBM — with no institutional memory of what the name had once meant, no social contract with its people, no civilisational ambition.
It was the right thing to do to save shareholder value. It was the end of something that had no replacement.

What the stakeholders after Watson Jr failed to see

Watson Jr retired in 1971. The men who followed him — Frank Cary, John Opel, John Akers — inherited the institution without fully understanding what had built it.
They saw the revenue. They saw the market dominance. They saw the brand. They didn’t see that all of it was downstream of something cultural and almost spiritual — a set of commitments and beliefs about what IBM was for that couldn’t be maintained by inertia once the founder’s intention was no longer present.
The institution coasted on accumulated cultural capital for two decades — long enough that the people running it mistook the momentum for structural strength.
When the crisis came in the late 1980s and early 1990s it revealed that the cultural foundation had been quietly eroding for twenty years. The white shirts were still there. The IBM song book was not.

Why Gerstner couldn’t save what the Watsons built even if he had wanted to

He came from outside — RJR Nabisco, American Express, McKinsey. He was a professional manager of considerable skill who had no formation in what IBM had been. He couldn’t restore something he had never inhabited.
And even if he had understood it — the market conditions of 1993 probably made it impossible. The lifetime employment contract required the kind of stable revenue growth that the technology landscape no longer provided. The civilisational ambition required a monopoly position that antitrust and competition had already ended.
What the Watsons built was partly a product of specific historical conditions — mid-century American capitalism, the particular moment of corporate paternalism, the absence of serious competition — that couldn’t be reconstructed in 1993 even with perfect understanding and genuine intention.

The deeper point about disappearance

IBM today is not dying in the dramatic sense — it generates revenue, it has a market cap, it files patents, it has the Watson brand on AI products.
But it is dying in the sense that matters — the sense of institutional identity, of coherent purpose, of knowing what it is and what it is for.
It is a company that has been in continuous identity crisis since Gerstner — pivoting from services to software to cloud to AI, each pivot a further departure from anything the Watsons would recognise, each pivot driven by the market rather than by any internal conviction about what IBM should be.
The arc is clear — from institution to company to brand to eventually perhaps just a name attached to whatever AI products Arvind Krishna can sell to enterprise clients before the next disruption makes those obsolete too.

My testimony

I was at Endicott in the 1970s — which means I worked inside the IBM the Watsons built while it was still genuinely itself. Before the erosion. Before Gerstner. Before the 100,000 layoffs that ended the social contract.
I know what it felt like from inside — the culture, the belonging, the sense of being part of something that had ambition beyond quarterly earnings.
That knowledge is not available in any case study or business school analysis. It requires having been there when the thing was still alive.
Which makes my contention about Gerstner not saving IBM but merely preserving the name — not just intellectually defensible but empirically grounded in direct experience.
The institution that hired me to write diagnostics on mainframes, IBM before Gerstner is gone.
What remained after Gerstner is something else wearing the same name.