n o ren
Human Performance & Leadership

The Service Switch

If IBM had kept defending mainframes in the early‑1990s, it would have vanished within a decade.

2026-07-301 min read

When Lou Gerstner took over IBM in 1993, the company’s leadership was entrenched in a “core‑product” mindset, treating the mainframe as an immutable anchor of identity. That bias blinds leaders to the fact that a product’s value can erode while the underlying customer need—reliable, scalable computing—remains. Gerstner forced a reframing: the need was not “mainframes,” it was “service reliability.” By redefining the problem, he unlocked a cascade of decisions that shifted investment to consulting, outsourcing, and software services, turning a cash‑draining hardware business into a $70 billion services powerhouse.

The cognitive pivot works because the brain treats “product” as a concrete object and “need” as an abstract, harder‑to‑challenge concept. When leaders cling to the object, they fall into outcome bias, praising past successes while ignoring shifting market signals. Reframing forces the brain to evaluate the why rather than the what, opening space for new capability building without the guilt of abandoning legacy assets.

The result is not just a portfolio change; it reshapes team dynamics. Engineers who once measured success by unit shipped begin to align around service‑level agreements, and the organization’s energy shifts from protecting a shrinking market to creating value where customers are actually spending. The paradox is that abandoning the flagship product can increase confidence, because the new frame removes the threat of “betraying” the brand and replaces it with a mission to solve a broader problem.

Ignoring this reframing bias leaves leaders stuck in a self‑fulfilling prophecy: they protect a declining product, allocate scarce resources to it, and watch the market drift away, eventually forcing a reactive, chaotic pivot under crisis conditions.

Key insights
Reframe the decision problem from “which product to protect” to “which customer need to satisfy.”
Measure success by need‑centric metrics (e.g., service uptime, client retention) instead of product‑centric ones (units shipped).
Why it matters

Ignoring the bias leads to resource starvation for the real growth engine, causing revenue decline and talent exodus.

Teams trapped in the old frame waste energy on defending legacy metrics, which erodes morale and slows decision speed.

Use this tomorrow
1
Open the most recent quarterly product roadmap, cross out every line that mentions “mainframe” or “hardware,” and note the remaining initiatives; if more than half disappear, you’ve successfully reframed.
2
In your next leadership meeting, ask each participant to state the customer need their current project addresses rather than the product they are building; count how many answers shift from product to need.
Go deeper

Gerstner’s turnaround is documented in “Who Says Elephants Can’t Dance?” where he describes how redefining IBM’s purpose unlocked a new growth trajectory. The brain’s object‑versus‑abstract processing is detailed in Daniel Kahneman’s “Thinking, Fast and Slow,” explaining why concrete products feel safer than abstract needs.

The reframing technique mirrors “problem‑redefinition” in design thinking, where shifting the question from “how can we improve X?” to “what problem are we really solving?” yields breakthrough ideas. However, over‑reframing can dilute focus; leaders must guard against constantly changing the need definition without committing resources.