Skip to content
Lex Fridman PodcastLex Fridman Podcast

Jeff Kaplan on Lex Fridman: Why games have three fun types

By sorting fun into player, designer, and computer types to analyze game feel; Kaplan shows why Rust is the most pvp thing and legacy of steel raids shaped him.

Jeff KaplanguestLex Fridmanhost
Mar 11, 20265h 10mWatch on YouTube ↗

CHAPTERS

  1. Episode highlight: PvP, fun, and the emotional cost of leaving Blizzard

    A rapid-fire teaser sets the tone: Kaplan’s view of “three types of fun,” the extreme PvP ethos of Rust, and the deep personal impact of saying goodbye to Blizzard. It frames the episode as both design philosophy and a personal journey.

    • Three types of fun: for the player, the designer, and the computer
    • Rust as “the most PvP thing” and what that implies about stakes
    • Forum negativity vs. in-person fan love
    • Kaplan’s belief he’d retire at Blizzard
    • Leaving Blizzard as a breaking point
  2. Arcade-to-PC origins: Pac-Man, NES wonder, Zork imagination, Doom/Quake immersion

    Kaplan traces his love of games from coin-op arcades through early consoles and PC classics. He highlights the transition from simple mechanics to immersive worlds, especially through text adventures and early 3D shooters.

    • Arcade era memories: Pac-Man, Asteroids, arcade culture in the ’80s
    • Home systems: Intellivision, NES and the magic of secrets/exploration
    • Zork and the power of imagination in text-based worlds
    • Ultima as formative world-building and player freedom
    • Doom/Quake as the mind-blowing leap to networked play
  3. Why Carmack and id mattered: engines, feel, and the first-person threshold

    They dig into the technical and experiential breakthroughs of id Software and John Carmack. Kaplan emphasizes that the revolution wasn’t only visuals—it was responsiveness and the intimate feel of first-person play.

    • Wolfenstein 3D and Doom as world-transporting breakthroughs
    • “Realism threshold” and why early 3D felt ultra-real at the time
    • Gameplay ‘feel’ (smoothness, responsiveness) as the real leap
    • Carmack/Romero’s influence on all later FPS design
    • How tech and immersion become inseparable in shooter evolution
  4. Creative writing ambitions: influence, ego, isolation, and 170 rejection letters

    Kaplan recounts pursuing a writing career (NYU creative writing), enduring massive rejection, and the psychological toll of isolation. He reflects on the ego required to create—and the heartbreak that can end a dream.

    • Literary influences: Kerouac, Hemingway, Salinger, Bukowski, Orwell
    • Rejection cycle: 170+ rejection letters in a year
    • Loneliness after leaving a supportive NY writing circle
    • Depression and alcohol as the spiral deepens
    • Dumping manuscripts/journals as a necessary “closing the door” moment
  5. Finding direction: “What do you want to do?” and escaping identity pressure

    A broader life lesson emerges: society pressures young people to decide what they ‘are,’ but fulfillment comes from what they repeatedly choose to ‘do.’ Kaplan frames this as a practical compass during uncertainty and transition.

    • Critique of societal pressure: majors, careers, fixed identities
    • Advice: focus on what you want to do, not what you want to be
    • Habits and daily behavior reveal true motivation
    • Closing doors can enable new ones to open
    • Creativity as compulsion: you do it because you must
  6. EverQuest obsession: progression, raids, guild leadership, and meeting his wife

    EverQuest becomes Kaplan’s refuge and obsession, logging thousands of hours and rising from solo player to top guild leader. He explains why raiding felt emotionally intense—and how EQ shaped his career and family.

    • EverQuest as escapism and the addictive loop of progression
    • /played time: ~272 days in 3 years (6,000+ hours)
    • Raids, uber guilds, and coordination as “herding cats”
    • Community dynamics: anonymity, stigma, and loneliness
    • Met his wife in EverQuest; EQ as the foundation of his life trajectory
  7. From guild leader to Blizzard hire: Half-Life mods, secret Blizzard coworkers, and “One of Us”

    A unique origin story: Kaplan’s online guild included Blizzard developers, leading to interviews disguised as lunches and a job opening tailored to his background. The “One of Us” ethos becomes a theme—building games as a representative of players.

    • Creating Duke Nukem/Half-Life levels using shipped editors
    • Ariel revealed as Rob Pardo; other guildmates also Blizzard devs
    • Meeting Blizzard founder Allen Adham via an EQ rescue story
    • Job posting for WoW quest designer valuing creative writing
    • Kaplan’s “One of Us” post: player-first design intentions
  8. Early Blizzard culture and team dynamics: small teams, trust, and creative collaboration

    Kaplan describes Blizzard as a flat, gamer-led culture where small teams had loud voices and cross-discipline empathy. He breaks down how game teams work and why mutual trust between disciplines is critical to shipping quality.

    • Blizzard in 2002: <200 people, “dorm room” vibe, intense camaraderie
    • Disciplines of game dev: engineering, art, design, production, audio
    • Power of small teams: shared context, less compartmentalization
    • Leadership lesson: assume each hire is best-in-class; listen deeply
    • Ego/insecurity in leadership and how Pardo coached him to develop ideas
  9. Building World of Warcraft: crunch reality, world design, and quest-driven leveling

    WoW’s design leap is framed as making the ‘path of least resistance’ fun: quests become the main leveling engine, guiding solo-friendly progression through a living MMO world. Kaplan also recounts brutal but self-driven crunch and early production challenges.

    • Crunch culture: extreme hours, personal choice vs. forced crunch
    • Quest system origins: Allen Adham’s vision + Kaplan/Pat Nagle execution
    • Key discovery: players wanted continuous quests, not sparse questing
    • Design principle: reward XP via quests to steer exploration/story
    • WoW as “playable single-player inside an MMO” (directed but optional-feeling)
  10. Designing for fun: intrinsic vs extrinsic motivators and shooter vs MMO appeal

    Kaplan maps “elements of fun” (progression, mastery, creativity, customization) and explains how players shift among motivations. He contrasts the visceral skill of FPS with the broader, evolving motivational loops of RPG/MMO play.

    • Intrinsic vs extrinsic motivation (loot, mastery, exploration)
    • Why ‘opening’ loot feels good: psychology + audiovisual polish
    • Elements of fun: progression, mastery, creativity, customization
    • FPS fun: first-person intimacy, skill expression, PvP tension
    • Multiplayer as unpredictable “director leaves the room” storytelling
  11. Blizzard polish: QA excellence, hotfix architecture, and live-service urgency

    Kaplan argues polish is culture, not a feature: intolerance for bugs, tight QA-dev integration, and engineering built for rapid hotfixing. He explains why live games must respond quickly to crashes, exploits, and balance problems.

    • QA as systematic, specialized testing—not “playing all day”
    • Embedding QA with dev teams to build trust and speed
    • Compatibility labs and regression plans as hidden foundations
    • Hotfixing as critical live-game capability (server-side fixes)
    • Polish as “love you can feel”: stability, balance, and responsiveness
  12. From WoW dominance to Titan failure: vision vs ideas, over-hiring, and engine collapse

    Titan aimed to be Blizzard’s next mega-MMO: future Earth, secret agents, one-world tech, and huge scope. Kaplan details why it failed—lack of cohesive vision, premature scaling, tool instability, and leadership breakdown—then how parts of Titan’s tech lived on.

    • Titan concept: future Earth agents; day jobs + night missions; driving; massive world
    • Ambition: one-server world vs. WoW’s sharded realms
    • Core failure: ideas without executable vision; no art cohesion
    • Anticipatory hiring created idle-time chaos and demoralization
    • Engine/tooling instability: creators losing half their productive time
  13. Overwatch in six weeks: “50 classes,” hero identity, and focus as survival

    Given six weeks and a two-year ship constraint, Kaplan’s team pitched multiple concepts—then Overwatch clicked: many heroes with a few defining abilities, each with personality. The pivot required ruthless scope control and leveraging strengths from Titan’s remnants.

    • Three pitches: StarCraft Frontiers, Crossworlds, and “Monetized Shooter” → Overwatch
    • Key spark: Jeff Goodman’s desire for many simple, distinct classes
    • Tracer prototype distilled from Titan’s “Jumper”; McCree art repurposed from Frontiers
    • Crawl-walk-run plan: establish IP first, then PvE, then larger world ambitions
    • Early scope discipline: ship something great vs. build another Titan
  14. Heroes, matchmaking, and toxicity: why teams blame, how 50% win rates feel, and what Jeff would change

    Kaplan discusses why simple heroes (Tracer, McCree, Reinhardt) can be the most elegant designs and how competitive systems inevitably frustrate players. He also reflects on Overwatch’s team-centric framing and how it unintentionally amplified blame and toxicity.

    • Favorite heroes: Tracer, McCree, Reinhardt (and key design inspirations)
    • Arena-shooter DNA + Team Fortress 2 influence
    • Matchmaking reality: players say “fair,” but want “slightly favored”
    • Win/loss streak psychology and selective outrage (no posts about win streaks)
    • Regret: insufficient emphasis on individual contribution; medals weaponized
  15. Overwatch League, Overwatch 2 PvE, and why Jeff left Blizzard

    The live game’s success collided with escalating executive pressure, monetization demands, and the operational weight of Overwatch League. Kaplan describes a breaking point where financial threats replaced creative leadership—prompting his painful departure from Blizzard.

    • Early OW2 PvE planning began as early as 2015 (pre-OW1 launch)
    • Live events vs. OW2 development tension; “ride the wave” vs. future bets
    • Overwatch League: good intentions, over-promised economics, heavy delivery burden
    • CFO ultimatum framing layoffs as Kaplan’s responsibility
    • Leaving Blizzard as grief: identity, loyalty, and a shattered life plan
  16. Kintsugiyama and The Legend of California: rebuilding after scars, early access, and the future of games

    After leaving Blizzard, Kaplan and Tim Ford form Kintsugiyama and quietly build The Legend of California—an online open-world gold rush-era survival/action game with voxel terrain and world resets. He closes with thoughts on AI as a tool (with ethical boundaries) and on small studios as the engine of innovation.

    • Kintsugiyama meaning: kintsugi repairs—beauty in visible scars and imperfection
    • The Legend of California: mythical 1800s gold rush island, lonely/dangerous/beautiful tone
    • Procedural seeds + movable points of interest; tiered difficulty rather than levels
    • Release approach: Steam wishlist, public-ish alpha, then early access iteration
    • AI in games: useful for tedious tasks, but consent and human creativity are irreplaceable

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.