Human Performance & Leadership
The Service Switch
Gerstner's most consequential move at IBM was refusing to do the thing everyone expected: break the company apart.
2026-07-301 min read
Lou Gerstner arrived at IBM in April 1993, the year the company posted a loss of roughly eight billion dollars — the largest in American corporate history to that point. The plan he inherited was to break IBM into independent units, each competing on its own product merits. He killed it. He had spent years on the other side of the table as an IBM customer, and what he had wanted from IBM was never a better disk drive; it was someone who could make a tangle of incompatible vendors work together.
That shift — from which products should we defend to what are customers actually paying to solve — changed what counted as an asset. A sprawling, expensive portfolio reads as dead weight if the question is product excellence. The same portfolio reads as the only credible integration offer on the market if the question is customer complexity. IBM's balance sheet did not change; the frame did, and the frame decided which facts mattered.
The follow-through cuts against how the story usually gets told. Gerstner slashed mainframe prices and moved the line onto cheaper CMOS processors, reviving a business everyone had written off rather than walking away from it. Services meanwhile grew into IBM's largest segment, over thirty billion dollars a year by the end of his tenure. He did not abandon the flagship to fund the pivot — he stopped the flagship from bleeding, then let a different business become the growth engine.
The trap this reframe avoids is treating what we sell and why they buy as one question. They drift apart quietly, and by the time the gap shows up in revenue, the reframing happens under crisis terms instead of by choice.
Key insights
Define the business by the customer problem, not the product; the product is a temporary answer to it.
Reframing changes which assets look valuable without changing a single line on the balance sheet.
Fixing the legacy line's economics and building the new engine are two separate jobs, not a trade-off.
Why it matters
A product-defined identity makes a shrinking market look like an execution problem, so leaders spend harder on the thing that is already failing.
Teams inherit the frame: engineers optimizing units shipped will not notice that customers started buying an outcome instead.
Use this tomorrow
1In your next team meeting, ask each person to finish the sentence "customers pay us to ___" without naming a product or feature, and count how many cannot do it.
2Open your last ten closed-won deals and count how many the customer could have solved with a competitor's product plus some glue work; that number is your integration gap.
Go deeper
Gerstner tells this himself in Who Says Elephants Can't Dance?, published in 2002, where the decision not to break up IBM is treated as the pivot everything else depended on. The book is unusually candid about culture rather than strategy being the binding constraint. The chapters worth the most are the ones on compensation, where he describes tying executive pay to company-wide results, which is what actually stopped the units from optimizing against each other.
The counter-case matters as much as the example. Defining yourself by a customer need rather than a product can widen the mandate until nothing is out of scope, and a company that will solve any problem tends to build no distinctive capability. The useful version of the reframe is narrow enough that some obvious adjacent work clearly fails the test. Theodore Levitt's 1960 Harvard Business Review essay Marketing Myopia is the canonical argument for reframing product as need, and it has drawn criticism ever since for encouraging exactly this over-broad failure mode.