Leadership Styles of Legends

Virginia "Ginni" Rometty joined IBM as a systems engineer in Detroit in 1981, straight out of Northwestern University with a degree in computer science and electrical engineering. She rose through global services and sales, eventually running IBM's global sales, marketing, and strategy before being named CEO in January 2012, the first woman to lead the company in its 100-year history. Her full background is documented in her Wikipedia entry.

She inherited a business model that the market was already walking away from. IBM's hardware and legacy services revenues were declining. She bet on Watson AI and cloud before most competitors had made the call. The comparison to Satya Nadella is unavoidable: both inherited legacy-software giants and made foundational AI and cloud bets at roughly the same moment, but Microsoft's transformation velocity significantly outpaced IBM's. The Watson brand launched commercially in 2013. But IBM's revenue fell from $104.5 billion in 2012 to $79.6 billion in 2017, a stretch of 22 consecutive quarters of year-on-year decline.

In October 2018, she announced the acquisition of Red Hat for $34 billion, IBM's largest ever, to accelerate hybrid cloud. She handed the CEO role to Arvind Krishna in April 2020.

The honest read of her tenure is a leader who correctly identified the destination and couldn't get there fast enough. That's not a small thing to understand, because it describes the situation a lot of executives find themselves in.

Leadership Style Breakdown

Style	Weight	How it showed up
Deliberate Transformation Leader	65%	Rometty operated with long-horizon conviction. She articulated the "Strategic Imperatives" framework (cloud, analytics, mobile, social, security) in 2013 and didn't abandon it when revenue kept falling. By 2017, those imperatives had grown from 22% to 46% of IBM's revenue. She made foundational bets (Watson, Red Hat) that weren't designed to show results in a single earnings cycle. That takes a specific kind of executive nerve that most boards wouldn't have sustained.
Client-Relationship Anchor	35%	Rometty built her career in IBM's services and sales organizations, and it showed in how she managed IBM's largest enterprise clients. She believed IBM's hundred-year relationship infrastructure, the trust that enterprise CIOs and Fortune 500 technology leaders placed in IBM, was a genuine competitive asset, even as cloud-native competitors were building faster. Her personal engagement with major account clients remained a priority throughout her tenure.

The 65/35 split captures the central tension in her leadership. The transformation leader instinct required disrupting the very client relationships that the anchor instinct was protecting. IBM's clients weren't moving to cloud as fast as the market was, which meant Rometty was managing two different time horizons simultaneously: the long-run pivot and the near-term client relationship economics.

Key Leadership Traits

Trait	Rating	What it means in practice
Long-horizon strategic bets	Very High	The Watson commercial platform, launched in 2013, was a genuine early bet on AI before most technology companies had committed to it publicly. The Red Hat acquisition in 2018 was designed around a hybrid cloud thesis that only became consensus industry view several years later. Rometty made both calls before the market gave her credit for them, which is either courageous or costly depending on when you're measuring. In IBM's case it was probably both.
Client-centricity built over 30 years	High	She spent her career at IBM understanding how large enterprises buy technology: slowly, with enormous institutional caution, through relationships built over years. That understanding gave IBM's transformation messaging credibility with existing clients even when the product portfolio was still catching up to the vision. The limitation is that this relationship infrastructure created institutional drag: IBM's transformation pace was partly constrained by the pace at which its largest clients were willing to move.
Tolerance for sustained short-term pain	High	Twenty-two quarters of revenue decline is a long time to hold a strategic conviction against analyst pressure, falling stock price, and board scrutiny. Rometty held it. That's a real trait. The question the failure forces is whether sustained tolerance for pain is a virtue or a delayed signal that the strategy needs to adapt faster. Both can be true.
Personal resilience in a contested CEO role	Strong	She held the CEO position for eight years with a falling stock, persistent analyst skepticism, and a transformation thesis that was right directionally but slow in execution. Her experience as an operator-inheritor who had to justify every quarter to a skeptical market echoes Tim Cook's early Apple tenure, though Cook inherited a growth engine rather than a declining one. And the legacy-CEO lineage she sits within — CEOs who shaped culture through long tenures on legacy businesses — runs directly through Jack Welch, whose GE transformation set the benchmark Rometty's tenure was inevitably measured against. In Good Power, her 2023 memoir, she's reflective about what she'd do differently. That kind of honest retrospection, not defensive, not revisionist, is its own leadership quality.

The 3 Decisions That Defined Rometty

1. Commercializing Watson as IBM's AI Brand (2013)

IBM's Watson system had beaten human champions on Jeopardy! in February 2011, under Sam Palmisano. When Rometty took over, she made commercializing Watson her centerpiece move. She created the Watson division, built a commercial platform, and put Watson's branding at the center of IBM's marketing for the next several years.

The bet was directionally right. AI would become one of the most important enterprise technology categories of the next decade, and IBM had a genuine early lead in the natural language processing and reasoning systems that underpinned Watson.

But the execution was expensive and uneven. Watson Health, created in 2015, acquired Merge Healthcare, Explorys, and Phytel, then signed a high-profile partnership with Memorial Sloan-Kettering and a $62 million contract with MD Anderson. Both of those medical partnerships failed publicly. MD Anderson cancelled the contract in 2017 after reporting cost overruns and unmet expectations. Watson Health was eventually wound down by Arvind Krishna.

The Watson story shows a leader who understood the strategic direction and overestimated the speed at which AI systems could be made production-ready in complex clinical and enterprise environments. The brand commitment was so large that when individual implementations failed, the reputational damage was amplified. Rometty's willingness to make a large public bet on AI was the right call. The execution of Watson Health specifically was a $1 billion+ write-off lesson in the gap between AI capability in controlled demonstrations and AI reliability in real-world enterprise deployments.

For today's leaders: when you're making a large strategic bet on an emerging technology, the public branding commitment and the product reality need to stay calibrated to each other. Getting ahead of your product's actual reliability can cost you the credibility you need to sustain the long-term bet.

2. Not Acquiring Cloud Assets at Competitors' Pace (2013-2017)

This is the decision that's hardest to evaluate fairly, because it's defined by what Rometty didn't do rather than what she did.

AWS grew 47% in 2016. Azure was scaling rapidly. Google Cloud was investing aggressively. IBM's cloud revenue, while growing, wasn't growing at a pace that closed the gap with the hyperscalers. Analysts and investors pushed for Rometty to acquire cloud-native assets, invest more aggressively in infrastructure, or make the price concessions necessary to compete with AWS pricing.

She chose a different positioning: IBM would compete on hybrid cloud and enterprise AI, not on raw infrastructure. The logic was that IBM's enterprise clients didn't want to put everything on a public cloud, and that IBM's security and compliance infrastructure gave it a defensible position in regulated industries.

That logic wasn't wrong. It just wasn't right enough, fast enough. AWS and Azure built their own enterprise compliance and security capabilities. The hybrid cloud opportunity that IBM was positioning for materialized, but Microsoft Azure captured most of it with a combination of enterprise relationships (from Office365 and Active Directory) and infrastructure investment that IBM couldn't match.

The leadership lesson is uncomfortable: the right strategy, executed at a pace below the market's velocity, can still fail. Deliberate transformation is a legitimate approach. But the deliberateness has to be calibrated against the speed at which the competitive context is moving, not just against the internal capacity for change.

3. Acquiring Red Hat for $34 Billion (October 2018)

The Red Hat acquisition was announced on October 28, 2018, and at the time it was IBM's largest acquisition in 107 years of corporate history. Red Hat was the leading open-source enterprise software company, best known for Red Hat Enterprise Linux, OpenShift (its Kubernetes platform), and Ansible (automation).

The strategic logic was clear: open-source and container-based hybrid cloud were becoming the enterprise standard, and Red Hat gave IBM a credible position in that stack. OpenShift in particular was becoming the preferred Kubernetes distribution for enterprises that needed support and compliance guarantees.

It closed in July 2019 for $34 billion. Arvind Krishna, the IBM executive who had overseen the acquisition, succeeded Rometty as CEO nine months later. Krishna ran IBM's post-separation strategy around the Red Hat bet Rometty made, spinning off IBM's legacy managed infrastructure services as Kyndryl in 2021.

The Red Hat acquisition is Rometty's clearest vindication. It was IBM's most valuable strategic asset in the post-2020 period, and the hybrid cloud thesis it embodied is now central to IBM's identity. But it arrived at the end of her tenure rather than the beginning of it. The question that remains unanswerable is whether an earlier Red Hat-equivalent move, or several smaller ones, would have prevented the revenue decline and changed the trajectory of her tenure.

For executives: a transformative bet made in year seven of a transformation is better than not making it, but the value it creates accrues to the successor. If you're running a multi-year transformation and you haven't made the definitional move yet, ask yourself honestly whether you're waiting for the right moment or avoiding the organizational disruption the move requires.

What Rometty Would Do in Your Role

If you're a CEO running a legacy transformation, the Strategic Imperatives framework has direct applicability. Rometty grouped IBM's growth bets into a single category, tracked them as a percentage of revenue, and communicated the trend to investors consistently. This gave stakeholders a way to track transformation progress even while total revenue declined. If you're running a transformation where legacy revenues are declining and new business is growing, separating those two signals in your reporting and communication lets you tell a more honest and more legible story.

If you're a COO building a services organization, Rometty's client-centricity has a real lesson about relationship assets. IBM's enterprise client relationships were genuine competitive moats. But moats only protect you if the thing you're defending is still valuable. As your industry or product category shifts, ask which of your client relationships are assets and which have become constraints. The enterprise clients who stay longest with a vendor in a transitioning category are sometimes the ones keeping the vendor from moving fast enough.

If you're leading a product team launching in an emerging technology category, the Watson Health story has a hard lesson. The gap between "this technology works in a controlled environment" and "this technology is reliable enough for enterprise production" is larger than it looks. When Rometty committed IBM's brand to Watson Health's clinical AI promise, the product wasn't ready for the commitment. The result was public failures at high-profile institutions that set back the entire category's credibility, not just IBM's. Ship proof of value before you ship the brand commitment.

If you're a sales or revenue leader managing enterprise accounts through a product transition, Rometty's tenure illustrates the tension between protecting existing revenue and building new. IBM's sales compensation and account management structures were calibrated to protect legacy services revenue for longer than the market warranted. If your comp structures and account prioritization are still optimized for the product you're transitioning away from, they'll work against your transformation regardless of what the CEO says at the all-hands.

Notable Quotes and Lessons Beyond the Boardroom

In "Good Power," Rometty reflects on power as something you use in service of others rather than for your own advancement. "Good power is about building," she writes, "not about having." That framing is worth examining. She ran IBM for eight years through a period when the external definition of success (revenue growth, stock price) was pointing in the wrong direction. Her internal definition of what she was building, a repositioned IBM with AI and hybrid cloud at its center, sustained her through that pressure.

She's also spoken honestly about the IBM transformation pace. "We had to move faster. I know that now. But you don't always know how fast you need to move until you can see where the market landed." That kind of retrospective honesty, not defensive, not trying to reframe failure as success, is genuinely rare in CEO memoirs.

On AI ethics, she was early to advocate for what IBM called "responsible AI": explainability, bias auditing, and human oversight. As one of the few women to lead a Fortune 50 technology company, her position alongside Sheryl Sandberg in that generation of female technology executives shaped how the industry thought about female leadership at scale. This positioned IBM in the AI governance conversation before it became mainstream. Her Cornell University AI ethics work post-IBM reflects a genuine conviction about the governance of systems she spent her CEO years trying to build.

Where This Style Breaks

Rometty's deliberate transformation approach was appropriate for a company with IBM's institutional complexity. But cloud computing wasn't a slow-moving opportunity. AWS and Azure were compressing the window available to catch up every quarter, and Rometty's pace was calibrated to IBM's internal change capacity rather than to the market's speed.

The 22 consecutive quarters of revenue decline had a real human cost. Morale inside IBM suffered. The company's reputation as an innovation leader, built over decades, eroded during her tenure in ways that the Red Hat acquisition couldn't fully repair. Watson Health's public failures specifically damaged IBM's credibility in the AI market it was trying to lead.

The deeper break in her style: transformation leaders who tolerate sustained short-term pain need faster internal feedback loops than Rometty built. When Watson Health's clinical AI failures were becoming apparent in 2016, the course-correction took too long. Leaders who bet on long horizons still need short-cycle signals to know if the execution is on track.

Learn More

Victor Hoang

Co-Founder & CMO, Rework