From the Dot-Com Crash to the AI Era: How Builders Survive Waves of Disruption

Leaders from iconic infrastructure companies VMware and Cisco discuss the lifecycle of disruption, the challenges of transformation, and the strategies required to innovate at scale, especially in the current AI wave. They argue that large companies must consciously fight against complacency and operational inertia to rediscover their innovative soul.

The Duality of Disruption: From Disruptor to Disrupted

A company’s history can often be divided into two phases: a decade of disrupting and a decade of being disrupted. The “weapons of mass disruption” in infrastructure are identified as:

1. A new abstraction: A novel piece of software that changes how things are done (e.g., VMware’s virtual machine).
2. A new class of users: Unlocking a user base that was previously not a consumer of the technology (e.g., AWS enabling developers to access infrastructure without IT).
3. A new business model: Shifting how value is paid for (e.g., VMware moving from hardware to software-based pricing).

VMware initially succeeded by introducing a new abstraction (the VM) and a new business model (software). However, it was later disrupted by the cloud, which, while initially using the same VM abstraction, fundamentally changed the business model and, most importantly, brought in developers as a new class of user that VMware wasn’t equipped to serve.

Reinventing a Giant: The “World’s Largest Startup” Mindset

When a company becomes large, it often masters “the math of the business” but loses “the soul of the business,” which is the drive for impatient, high-velocity innovation. To combat this, Cisco initiated a “reset” by embedding a founder’s mentality throughout its leadership, often by placing former CEOs of acquired companies into key roles. This creates a productive tension between impatient innovators and seasoned operators who know how to navigate the corporate machinery.

The guiding mantra becomes to “operate like the world’s largest startup,” combining the speed of a startup with the scale of an enterprise. The goal is to create a repeatable engine for growth: developing a product from zero to market in nine months and scaling it to a billion-dollar business in three to four years.

Strategies for Innovation and Go-to-Market

Organic vs. Inorganic Innovation:

• Organic innovation works best for “close adjacencies” where a new product targets the same user or buyer. For example, VMware’s VSAN succeeded not by targeting storage buyers, but by expanding the purview of the existing compute buyer.
• Inorganic innovation (acquisition) is often necessary when targeting a new user or a fundamentally different operational model, as with VMware’s acquisition of Nicira for network virtualization.

Go-to-Market for New Products: A common failure mode in large companies is building a zero-to-one product that doesn’t align with the existing route to market. Success requires a disciplined, phased approach:

1. Ring-fence the Team: Protect a small, “two-pizza team” with air cover directly from the top, shielding them from internal antibodies that resist new ideas.
2. Define the Ideal Practitioner Profile (IPP): Don’t think about the ideal customer (e.g., a large bank); define the ideal practitioner and the ideal use case. The initial product is for them, not for your largest enterprise accounts.
3. Phased Rollout: The innovation team’s job is to build the product and find initial adoption within that narrow IPP. Once that niche is saturated, you systematically expand the customer profile, bringing in the broader sales force with new incentives over time. This avoids the “it’s not a complete product” rejection from a field organization trained to sell to the most demanding customers.

Leadership in Transformation: Storytelling and Truth-Seeking

Owner’s Mentality: While founders have unique authority, any leader can adopt an “owner’s mentality.” This involves being extremely impatient, thinking “market-in” rather than “company-out,” and refusing to tolerate mediocrity. It requires surrounding yourself with critics to get to the unvarnished truth, which is especially hard to find in large, compassionate cultures where direct, binary language (“we are failing”) can be uncomfortable.

The Story is the Strategy: In a large organization, the strategy is not a set of bullet points; it’s the story. A leader cannot delegate the storytelling. A single, consistent narrative, told by the person who owns the vision, is essential to galvanize tens of thousands of employees. When the story is fractured, the strategy fails.

The AI Wave: A Fundamental Infrastructure Shift

The current AI wave is not an incremental change; it is a fundamental disruption that requires thinking from first principles.

• Infrastructure Reimagined: AI changes every layer of infrastructure. The entire stack, from power generation to token output (“power to tokens”), is being re-architected. The workload dictates the infrastructure, and as AI models evolve, bottlenecks will continuously shift between compute, networking, and memory.
• A 100x-1000x Shift: The scale of this change is not 10x, but closer to 100x or 1000x. As autonomous agents become persistent, they will create sustained, not spiky, demand for inference, exponentially increasing the need for network bandwidth and compute.
• Vertical Integration and Horizontal Openness: Unlike previous waves that led to horizontal disaggregation, the AI era favors vertical integration (from custom silicon to the software stack) to optimize performance. However, this must be paired with a radically open, horizontal ecosystem. To succeed, companies must partner with their biggest competitors and integrate deeply. “When someone owns more than 20% share in the market and you don’t integrate with them, you’re just excluding yourself from the market.”

A Formula for Founders

A six-part formula for building a great company, in descending order of importance:

1. Timing: The mega-trend is paramount. Today, you must have AI as a tailwind.
2. Market: Go after a large total addressable market (TAM), but attack it a step at a time. Market always trumps team.
3. Team: Assemble the right people.
4. Product: Build something people love, that drives adoption, and is commercially relevant.
5. Brand: Create a clear, identifiable brand with a consistent message.
6. Scale Distribution: Build a scalable go-to-market engine.

• Tags:
• Infrastructure
• Go-to-Market
• Feature
• Leadership
• Innovation
• Cloud
• Disruption
• Enterprise Software