Who Says Elephants Can't Dance?: Leading a Great Enterprise through Dramatic Change: Summary & Key Insights

When I walked into IBM’s Armonk headquarters in April 1993, the sense of paralysis was palpable. Once the undisputed leader of the computing world, IBM had become a relic of its own glory. Revenues were shrinking, morale was demoralizingly low, and factions within the company were preparing for dismemberment. For decades, IBM had thrived on its hardware dominance, but the world had moved on. The personal computer revolution and emerging client-server models had splintered traditional computing, and IBM was stuck defending its fortress of mainframes.

But the deeper problem lay inside—the culture. IBM had become consumed by process over purpose. Meetings about meetings, reports about reports—decisions lost in layers of bureaucracy. People spent more time protecting turf than serving customers. Financially, the numbers told the story: billions in losses, bloated costs, and product lines competing against one another. The planned breakup reflected the prevailing sentiment that the company was too big to manage.

I was warned repeatedly: no one could save it. Yet, as I studied the company, I realized IBM didn’t just make hardware. It had something priceless—deep relationships with the world’s largest corporations and unmatched technical expertise across systems, software, and services. The issue was not technology; it was a lack of direction. IBM was like a symphony with talented musicians but no conductor keeping tempo. That was the crisis I inherited—not just financial, but spiritual. And the only cure would be leadership that fused realism with optimism.

Within weeks of my arrival, I faced the decision that would define IBM’s future: should we follow the Wall Street blueprint and divide the company into autonomous units? To many insiders, this seemed inevitable. Investors argued that breaking IBM apart would unlock value. But as I studied the pieces, I saw the fatal flaw in that logic. The future of computing was moving toward integration—networks, software, and hardware all converging to solve real customer problems. To separate IBM would destroy the one thing that made it unique.

So, I made what many called a contrarian choice: I killed the breakup plan. My reasoning was rooted not in sentimentality but in strategic conviction. Customers didn’t want a fragmented vendor; they wanted a partner who could bring it all together. The irony was that IBM’s size—always portrayed as its weakness—would become its greatest strength if we could operate as one.

This decision sent shockwaves through the organization. It told employees: we’re staying together, and we’re going to fight. It required an entirely different leadership mindset. Instead of surrendering to market pressure, we focused on execution—restoring performance one business at a time, simplifying operations, and holding people accountable. That moment, rejecting the breakup, wasn’t just about structure; it was IBM rediscovering its self-belief.