The Infinite Game

For a period of about ten years, a particular phrase circulated through gaming press cycles with the reliability of a seasonal allergy. It appeared in preview coverage and forum threads and the comment sections of every major gaming outlet. It followed each new massively multiplayer online game to market with the confidence of a campaign slogan.

WoW killer.

The term carried a theory of competition embedded in it – the idea that the correct objective for any new entry into the MMORPG market was to defeat World of Warcraft. To take its players, collapse its subscriber numbers, and claim the throne. Lord of the Rings Online launched with the Tolkien legendarium as its entire value proposition and a player base hungry to walk the Shire. Age of Conan arrived with a darker, more visceral aesthetic and the full weight of Robert E. Howard's source material behind it. Star Wars: The Old Republic came backed by BioWare's storytelling reputation and one of the most beloved franchises in the history of popular culture. Wildstar – developed by a team that included former Blizzard employees who knew exactly how the machine worked – arrived swinging hard at WoW's casual-to-hardcore spectrum and missing both.

None of them killed anything. Most of them aren't even around anymore.

And then, against the odds, and without declaring its intentions³³, Final Fantasy XIV found a permanent home in the market.

Simon Sinek didn't invent the distinction between finite and infinite games³⁴ – that credit belongs to the philosopher James Carse, whose 1986 book put the framework on paper – but Sinek popularized it, sharpened it into a business lens, and made it useful in contexts Carse hadn't fully explored. The core concepts are simple enough to state in a paragraph, and worth stating clearly before going further.

A finite game has fixed rules, a known set of players, a defined timeframe, and a clear winning condition. You play to win, and when someone wins, the game is over. Chess. Football. A sales quarter.

An infinite game has none of those constraints. The players are known and unknown – competitors you can see and ones you can't anticipate. The rules shift. Players can enter or exit at any time. There is no winning condition, no terminal state, no final whistle. You play to keep playing. And the only way to lose an infinite game is to exhaust your will, your resources, or both, and drop out.

The critical implication – the one that explains a lot of corporate failure – is what happens when a player built for an infinite game starts treating it as finite instead. When they stop asking “how do we continue to improve and compete” and start asking “how do we win?” The target changes. The strategy narrows. And the narrowed strategy, optimized for a finishing line that doesn't exist, slowly undermines the capacity to sustain the actual game being played.

Every game on that list of WoW killers made this mistake. Not because they were poorly made – some of them were genuinely good – but because the objective they organized around was the wrong one. Beat World of Warcraft is a finite objective. It implies a scoreboard, a threshold, a moment at which victory could be declared and the game concluded. The MMORPG market is not a finite game. It never was. And playing it as one – optimizing for the kill shot rather than for long-term viability – produced exactly the outcome you'd expect.

They ran out of resources, or will, or both. And they stopped playing.

World of Warcraft has been running for over twenty years. It has survived expansion cycles that ranged from generational highs to periods that even its most devoted players will acknowledge were not its finest hours. It has weathered corporate turbulence, public controversy, a global pandemic, and the sustained structural pressure of a gaming landscape that looks almost nothing like the one it launched into in 2004. It is still here.

Part of that longevity is the game itself – the accumulated weight of twenty years of lore, the embedded social infrastructure of guilds and communities and friendships that exist nowhere else, the sheer inertia of a world that millions of people have called home across multiple chapters of their lives. But part of it is something more deliberate.

World of Warcraft is a subscription product. It has always been a subscription product. The business model is structurally an infinite game: the objective is not to sell the most copies at launch, but to give players a reason to stay subscribed month after month, year after year, expansion after expansion. Every design decision that improves the long-term experience – and every decision that sacrifices it for short-term engagement metrics – shows up eventually in the subscriber numbers. The feedback loop is real, and it runs in both directions. Blizzard has occasionally felt that pressure in ways that weren't comfortable.

But the model itself is honest about what the game actually is. You are not playing to finish. You are playing to keep playing.

The players understand this, even if they've never read Sinek. The ones who have been there since Vanilla don't talk about beating World of Warcraft. They talk about living in it. The goal was never the end boss. The goal was the world.

Here is where Final Fantasy XIV becomes instructive, and where Sinek's framework adds something specific.

In The Infinite Game, Sinek argues that a worthy rival is not a threat to be neutralized – it is a necessary feature of a healthy competitive environment. The right competitor forces you to improve. It reveals your gaps. It keeps you from becoming complacent atop a position you've stopped having to defend. The worthy rival is not your enemy. It is, in a meaningful sense, part of what keeps you in the game.

FF14 is that rival now, and it got there by refusing to be a WoW killer.

The early history of FF14 is not something I'll dwell on – it launched in a state that its own developers later acknowledged was indefensible, and the story of how it was rebuilt into A Realm Reborn is well documented and not the point here. The point is what it became after the rebuild, and why.

FF14 did not set out to take WoW's players. It set out to be the best version of a Final Fantasy MMO that it could be. The design philosophy, the narrative sensibility, the community culture that formed around it – none of it is optimized to appeal to lapsed WoW players who are angry about their current subscription. It is optimized to be FF14. And the audience it found is, to a substantial degree, an audience that might never have been comfortable in Azeroth in the first place.

The two games borrow from each other occasionally, as any healthy competitors do. WoW recently implemented player housing, a feature FF14 has offered for years³⁵. The cross-pollination is real, and it's evidence of exactly the dynamic Sinek describes: two players in an infinite game, each improved by the presence of the other, neither trying to deliver a finishing blow. If FF14 shut down tomorrow, Blizzard would not issue a press release declaring victory. They would keep telling the Worldsoul Saga. If WoW went dark, FF14 would not expand to absorb the displaced population as a strategic maneuver. It would keep being FF14.

That is what a healthy infinite game looks like from the outside: two players, occasionally ahead and occasionally behind, focused on their own capacity to continue rather than on eliminating the other.

The earlier competitors – LOTRO, AoC, Wildstar, the others – had the raw material to play the same game. They had intellectual property, talented teams, and genuine audiences who wanted what they were offering. What they didn't have, or didn't hold onto, was a clear answer to the question why do we exist, independent of our position relative to World of Warcraft? Without that answer, the competitive pressure collapsed their strategy inward, and they found themselves optimizing for a kill they couldn't land rather than a game they could sustain.

The worthy rival survived. The WoW killers didn't.

Blizzard is not immune to finite thinking. It would be dishonest to suggest otherwise, and this essay isn't a brief for hagiography.

Heroes of the Storm was, at least in my own accounting, the best MOBA ever made. The design philosophy was genuinely distinctive: no items, no last-hitting, an emphasis on teamfight and macro strategy over individual mechanical expression that made it more accessible to casual players without sacrificing depth for the dedicated ones. The community that formed around it was passionate. The esports scene was ambitious.

And in 2018, Blizzard significantly scaled back development and shut down the HGC – the Heroes Global Championship – with two weeks' notice, mid-season, devastating a professional scene that had organized their lives around it. It was a decision executed badly, and the people hurt by the abrupt shutdown deserved better handling.

But, strip away the execution and look at the underlying logic: a product that was beloved but commercially underperforming, competing in an esports ecosystem dominated by League of Legends and DOTA 2 – two games with years of established infrastructure, massive viewership, and network effects that Heroes was unlikely to overcome regardless of design merit. The resources allocated to the HGC were finite. The question was whether they were better deployed sustaining a losing competitive position, or redirected toward Overwatch 2 and Diablo IV.

From an infinite game perspective, that is actually a coherent decision. Sometimes stewardship of the whole means accepting a local loss. Sometimes the right move is to release one piece in order to strengthen the board, like sacrificing a bishop to capture a queen. The mistake was not in cutting; it was in how the cut was made. The obligation to the people who had built their professional lives around the HGC deserved more than two weeks' notice – and that's a legitimate criticism that exists independently of whether the underlying resource decision was right.

Diablo Immortal was rightly criticized. Warcraft Rumble came and has largely gone. These are not nothing. But they are also not structural failures – they are the variance you'd expect from an organization willing to experiment, run through a portfolio diversified enough to absorb the weight of individual misses. The overall health of the enterprise, and the goodwill of its community, remained intact because the aberrations were legible as aberrations. They stood out precisely because they weren't the norm.

The risk, and it's worth naming clearly, is cumulative. Finite-game thinking doesn't usually announce itself. It accretes. A decision to optimize this quarter's engagement metric. A feature designed to drive retention numbers rather than player experience. A roadmap shaped more by competitive anxiety than by genuine creative vision. None of these look like much in isolation. Stacked together over years, they are how you wake up atop a lonely throne, having gradually displaced the thing that earned you the throne in the first place.

Blizzard knows this. The return of Chris Metzen, the explicit recommitment to the Worldsoul Saga, the careful stewardship of the WoW Classic ecosystem – these are not the moves of an organization that has forgotten what game it's playing. They read, to me, like someone consciously pulling the organization back toward the long view. And I think that read is correct.

I am aware that I have just spent several pages applying the frameworks of a business author to a video game company, and I want to be direct about why.

The work I would do at Blizzard – whatever its specific shape – would be played in the same register. Not the infinite game of the MMORPG market, but the infinite game of a game studio committed to worlds it intends to inhabit for decades. The Worldsoul Saga is not a three-year roadmap; it is a generational creative commitment. The Classic ecosystem is not a feature; it is a parallel timeline being maintained alongside the living game. These are infinite game decisions, and they create an infinite game context for every producer, every program manager, every person responsible for keeping the delivery machine running.

In that context, optimizing for a sprint at the cost of a saga is not discipline. It is the wrong game.

This connects to something the systems thinking essay tried to establish: that finite objectives are often embedded inside infinite games, and that the skill is in knowing which level you're operating on at any given moment. An individual raid tier is a finite game – a beginning, a middle, a clearance, a conclusion. The expansion is a longer finite game, with its own arc. The franchise is something else. It doesn't end. It evolves. And the question at that level is never did we win this release but did we leave the game healthier than we found it.

That is the question I would carry into every room.

Not did we ship on time – though we would, because that matters too. Not did we hit the quarterly engagement numbers – though we'd track those as signal, because they are. The first question, always, underneath all of it: did we do something today that makes the long game more possible?

You play the infinite game well by refusing to lose sight of what it actually is. The point isn’t to win, the point is to keep playing.