DiscussionStory

World of Warcraft explained by WoW lead game designer | Jeff Kaplan and Lex Fridman

Lex Clips

Jeff Kaplan discusses the early development of World of Warcraft, emphasizing how the game's success stemmed from a diverse, inexperienced team working intensely on a passion project. He reflects on the controversial Horde-Alliance faction system, the team's composition of veterans and newcomers, and the grueling crunch periods that characterized WoW's development, while contextualizing the distinction between forced and voluntary overtime.

Summary

In this conversation with Lex Fridman, Jeff Kaplan provides an in-depth account of World of Warcraft's development. He begins by defining WoW not just as a game mechanic but fundamentally as a world—a place where people live out fantasies together. Chris Metzen's vision that "the lead character of World of Warcraft is the world" became a guiding principle for the entire team.

A major point of discussion is the Horde-Alliance faction split. This was a controversial decision championed by co-founder Allen Adham, inspired by Dark Age of Camelot's three-faction system. Kaplan and Rob Pardo initially opposed it, coming from EverQuest where races could intermix, but Allen's reasoning about creating instant team identity convinced them pre-launch. When Adham retired nine months before WoW shipped, Pardo took over as lead designer and doubled down on the faction system, which became so central to players' identities that people got tattoos reflecting their allegiance.

Kaplan characterizes the WoW team as "the Bad News Bears"—a hodgepodge mix of Blizzard veterans and relative unknowns. The team pulled talent from unexpected sources: dungeon designers from the Quake community, and people like Kaplan himself who were primarily qualified by passionate EverQuest fandom. Early versions even used the Quake engine before transitioning to a proprietary one. Kaplan argues that this inexperience was actually crucial to WoW's success, contrasting it with the later failure of Titan, where the team was too expert and over-confident.

The transcript extensively covers the crunch culture during WoW's development. Kaplan worked 30-hour shifts during Warcraft III gold-mastering, watching cinematics repeatedly to trigger a bug. He describes the WoW development as an "endless death march," with catered dinners (particularly Newport Rib) becoming synonymous with late-night work sessions. Mark Kern promised early crunch would prevent later crunch, but uncontrollable date slips created prolonged overtime. Kaplan emphasizes he never felt forced and actually chose to work on holidays with sand still on his feet from the beach.

Kaplan makes an important distinction about crunch: he opposes forced, unnecessary overtime and executives working 40-hour weeks while demanding others stay late—which he calls "immoral." However, he defends his personal work ethic (typically 10+ hours daily) as voluntary and fulfilling, producing some of his fondest memories. He frames this not as something to impose on others but as core to his identity as a creator producing joy for millions of players.

Key Insights

  • Kaplan argues that WoW's success was significantly enabled by the team's inexperience and lack of MMO expertise, contrasting this with Titan, where the team was too expert and over-confident in their ability to create a groundbreaking MMO, which led to failure.
  • Allen Adham championed the Horde-Alliance faction system inspired by Dark Age of Camelot's approach to create instant team identity, believing players shouldn't be 'loners in the world,' which contradicted EverQuest's mixed-race approach that Kaplan and Pardo initially preferred.
  • Kaplan worked a continuous 30-hour shift watching the same cinematic to trigger a crash during Warcraft III gold-mastering, observing team members cycling in and out while he remained stationary with bloodshot eyes.
  • Kaplan distinguishes between crunch he opposes—forced, unnecessary overtime imposed by executives working fewer hours—and voluntary overtime driven by personal passion, which he describes as morally different and personally fulfilling.
  • WoW's dungeon designers were hired from the Quake community rather than MMO backgrounds, initially building Quake-style levels as dungeons, and early WoW development even used the Quake engine before transitioning to a proprietary engine.

Topics

World of Warcraft's core design philosophyHorde-Alliance faction system origins and controversyWoW development team composition and hiring from non-MMO communitiesCrunch culture and overtime during game developmentDistinction between voluntary passion-driven work and forced mandatory overtimeImpact of inexperience and diversity on creative success

Transcript

[0:03] let's talk about WoW. Let's talk about World of Warcraft. Tell me what the early days of developing WoW was like. Maybe we should talk about what World of Warcraft, WoW is, going to Perplexity here. World of Warcraft is a massively multiplayer online RPG where you create a character, level it up doing quests and dungeons, and progress your gear and power in an open fantasy world called Azeroth. At a basic level, you move, use abilities from your [0:33] action bar, follow quests, and gradually learn a combat rotation that fits your class. And there's all kinds of characters and roles and classes. You pick a race, appearance, starting zone, small racial bonuses. In a class, how…

Full transcript available for MurmurCast members

Sign Up to Access

More from Lex Clips

Get AI summaries like this delivered to your inbox daily

Get AI summaries delivered to your inbox

MurmurCast summarizes your YouTube channels, podcasts, and newsletters into one daily email digest.