He was Right on outsourcing, wrong on everything else.

Gerstner joined IBM in 1993 with the company in a very bad situation and immediately killed the "Baby Blues" breakup plan - no more independent product units for PCs, various servers, storage, semiconductors. Instead: one monolith optimized for selling professional services to enterprises. Outsourcing became the flagship.

This saved IBM then. It also set a ceiling on what IBM as a technology company could ever be again. The services pivot worked commercially. Outsourcing grew into a maybe 20 billion/year business, ironically eventually spun off as Kyndryl in 2021. But the cultural shift - from building systems/cutting edge-tech to managing other people's systems - hollowed out IBM's product DNA.

Consider that IBM's last major hardware win was the RS/6000, circa 1990. That's 35 years without a new product category victory. Meanwhile, IBM had countless pieces to own which is cumbersome -- and sad -- to list, and the list would be long. VMs invented in the 1970, running on every mainframe as an example: VMware ate the corporate market while the cloud hyperscalers built actual technology services based on it. You could probably get business consulting on it from IBM in the same time.

IBM Research remained well-funded throughout - still producing papers, still winning awards. But research was not focused to support a technology business any more, it even got pulled into service client engagements (!), subordinated to billable hours rather than productization. The research labs that gave us the bar code, DRAM, RISC, relational databases, and the scanning tunneling microscope became a presales asset.

The counterexample of large technology company in later trouble is Siemens: a conglomerate that actively manages distinct businesses as distinct businesses. Healthineers spun out and thrived. Energy spun out when it needed different go-to-market models. Industrial automation runs independently. No insistence on "one face to the enterprise customer", yet they can probably provided it if needed (don't know). They did their portfolio reshaping without strategic rigidity and the Gerstner betting on a single non-really-tech managed IT services anchored in shallowish business more than anything else horse and not the technology herd of horses.

Gerstner's legacy is complicated. He unquestionably prevented IBM's collapse financially then. But the rescue vehicle became a prison. A company with IBM's research depth, enterprise relationships, and installed base should have built the cloud, should have owned enterprise AI, should have been where AWS, VMware, TSMC even, and more low-hanging Salesforce are now.

Gerstner himself probably wouldn't be recognized as an IBMer by most who worked there before him. Brought in by a probably desperate board to save a company he then remade in a different image entirely. He saved IBM by making it something else he knew to be valuable from his prior work as a business leader. Whether that something else was the best available option, or merely an option he was familiar with: purchasing abstract solutions from a single source, is the open question his tenure leaves behind. This post argues it was the wrong one, dead wrong that is. In hindsight it was just good for the business strategic outsourcing (which is managed IT for large enterprises) side of things, wrong for much else.

Siemens as a company with similar issues of a collapsing core business ca. 2000, even much more so than the mainframe ever did, is the anti-thesis in terms of approach taken. It actively manage distinct businesses as distinct businesses, reshaping portfolios without insisting on a single face or a single model; an approach that turns out to work better looking at it now in comparison than trying to play seller of a single face to enterprise customer as a monolith. Most of the business are both technologically strong and financially in a good shape.

IBM under Gerstner set course on being a monolith optimized for selling and delivering professional services, stripped of the technology capabilities the company was built on. IBM evidently was saved then. Was it the only/best route to take? Probably not, as the low ceiling on what IBM as a technology company could be afterward turned out to be too low to stand or produce not a single major hardware win thereafter for over 35 years.

More bluntly: he transformed a legend into a fallen angel. IBM today is a shadow of what it was, what it stood for, and what it could have been. Gerstner himself fits the pattern of a business turnaround guy - an outside business consultant who saved IBM by remaking it in his own image. He never became an IBMer. But he did make IBM something else.