Skip to content

The LiveOps Playbook

Distilled from the comprehensive internal guide: "THE LIVEOPS PLAYBOOK — The Definitive Guide to Running Live-Operated Digital Collectible Products."

Core Philosophy: LiveOps IS the Product

"You were not hired to support a product. You are the product." — THE LIVEOPS PLAYBOOK, Chapter 1

"The app is infrastructure. The marketplace is plumbing. The blockchain is a ledger. These are necessary — like a stadium is necessary for a basketball game. But nobody buys a ticket to see a stadium. They buy a ticket to see what happens inside it." — THE LIVEOPS PLAYBOOK, Chapter 1

The playbook reframes LiveOps from a maintenance function to the primary value creation layer.

"What happens inside your product — the drops, the campaigns, the challenges, the community moments, the stories you tell, the scarcity you design, the emotions you create — that is what collectors pay for." — THE LIVEOPS PLAYBOOK, Chapter 1

The Economic Case

Industry data cited in the playbook:

  • Games using live operations models received 84% of all in-app purchase revenue globally — $69 billion of an $82 billion market (2024).
  • Downloads declined 7%. Sessions grew 12%. Revenue grew 4%.
  • Of the top 1,000 live ops games by revenue, 78% saw revenue decline in H1 2025. The winners grew while the median declined.

"The math: growth is coming entirely from deeper engagement with existing players, not from new installs." — THE LIVEOPS PLAYBOOK, Chapter 1

"The difference is not 'doing live ops' — it is doing live ops well." — THE LIVEOPS PLAYBOOK, Chapter 1

The Three Layers

Every live product operates on three layers. The playbook defines the operational rhythm for each:

1. The Platform (changes quarterly or less)

"The marketplace, the wallet, the authentication system, the blockchain infrastructure, the content management tools. This is engineering's domain. It should be invisible to collectors — they should never think about it."

2. The Engine (changes monthly)

"The progression system, the challenge framework, the pack architecture, the economy parameters, the recommendation algorithms. These are the systems that make the content come alive."

3. The Content (changes daily or weekly)

"The drops, the campaigns, the social posts, the emails, the community events, the stories. This is your domain. It runs on the engine, which runs on the platform. Most of your waking hours should be spent here."

The playbook identifies the most common mistake:

"The most common mistake: spending 80% of team time debating engine and platform changes while content ships on autopilot. In a healthy live product, the ratio inverts."

Small Teams Compound

The playbook argues for small teams with systems that compensate for size.

"Communication overhead scales quadratically with team size. A 10-person team has 45 possible communication channels. A 100-person team has 4,950."

Supercell is the benchmark: 686 employees, $3 billion revenue in 2024 — $4.37 million per person, highest revenue-per-employee in gaming.

But the playbook also flags the nuance:

"In 2023, Supercell restructured. After five years without a new hit, they acknowledged that the same small-team model optimized for creating games was not optimized for operating them at scale. They split into two divisions: New Games (keeping the original cell structure) and Live Games (adding traditional hierarchy and growing teams). The Clash of Clans team doubled to 56 people."

"The lesson is not that small teams fail at live ops. The lesson is that small teams doing live ops must build systems that compensate for their size — templated drop pipelines, reusable campaign frameworks, AI-powered content generation, automated analytics. The system does the scaling. The people do the thinking."

Content Treadmill vs. Content Engine

Two operational modes. One is sustainable.

The Treadmill (what kills teams)

"Every drop is hand-crafted from scratch. Every campaign is a custom production. Every week requires the same effort as the week before, regardless of what you learned. Player expectations escalate while production costs stay fixed."

The Engine (what scales)

"Instead of hand-crafting every experience, you build systems and pipelines that generate variety efficiently. Not by cutting corners — by being smarter about where human creativity adds value and where systems can handle the rest."

Five strategies for building the engine:

  1. Other players as content. "In any product with a marketplace, other collectors ARE the content. Every listing, every sale, every collection showcase is something another collector experiences. The marketplace is not a feature — it is an infinite content generator."

  2. Strong metagames. "Challenges, leaderboards, set completion races, prediction games. These create engagement without requiring new collectible content."

  3. Modular production. "Reusable narrative modules — announcement frames, reward reveal structures, escalation moments, seasonal mood variants. Not templates that feel stale. Composition systems that preserve identity while enabling variation."

  4. Community participation. "Let collectors contribute to the product experience — voting on set compositions, competing to curate collections, creating content about their predictions and strategies."

  5. AI-powered variation. "AI can generate social content variations, personalize email campaigns, produce asset variations from base designs, and analyze post-drop data in minutes rather than days. The human decides what to say. AI decides how to say it a hundred different ways to a hundred different segments."

Story Is the Operating System

"People do not buy products. They buy the story they tell themselves about who they are when they use them." — THE LIVEOPS PLAYBOOK, Chapter 2

"A collector does not spend $500 on a digital LeBron James Moment because of its expected secondary market value, its on-chain provenance, or its scarcity tier. Those are the rational justifications. The purchase happens because of a story: 'I am the kind of person who owns a piece of NBA history. I was here when this happened. My collection says something about who I am.'"

The Tribal Framework

Seth Godin's framework, as applied in the playbook:

"'People like us' — a self-selected identity. Not demographics. Not income brackets. The tribe you choose. 'I am a collector.' 'I am an NBA obsessive.' 'I am a Disney fanatic.' This identity exists before the product. Your job is to activate it, not create it."

"'Do things like this' — the rituals, the markers, the behaviors of that tribe. 'We rip packs on drop day.' 'We flex our collections on Twitter.' 'We call the games before they happen.' 'We complete sets that prove our dedication.'"

"The product succeeds when using it becomes an expression of tribal identity."

The JC Penney Lesson

"Ron Johnson, the retail genius who built the Apple Store experience, became CEO and killed the coupons, the flash sales, the 'door-buster' discounts. He believed premium retail was objectively better. Sales fell 50% in a year. He failed to understand that JC Penney's tribe valued the hunt for deals — the discount WAS the product experience."

"For collectibles, the equivalent mistake is designing drops that are 'better' by some objective measure but fail to activate the collector identity."

The Emotional Subsidy

Research data cited in the playbook:

  • Highly identified sports fans show significantly lower price sensitivity for team-related merchandise (Kwon, Trail, and Anderson, 2007).
  • Fans of niche sports franchises pay an average premium of 68% over comparable alternatives.
  • Tribal brands produce 3x the customer lifetime value of non-tribal brands.
  • Limited-edition merchandise sees a 27% intent boost from the scarcity signal alone.

"This is the 'emotional subsidy' — the gap between what a product is worth rationally and what a collector will pay because of the meaning attached to it. Every product decision either increases or decreases this subsidy."

What increases the subsidy: - Drops tied to real moments (a player's career night) - Collections that tell a story (the complete set of a championship run) - Scarcity that feels authentic (mint caps that are honored, burns that are real) - Community celebration of collector achievements

What decreases the subsidy: - Drops that feel transactional ("buy this because it's available") - Broken scarcity promises (oversupply, re-releases of "limited" content) - Speculation-dominant messaging ("buy this because it'll go up in value") - Anything that makes the collector feel like a customer instead of a member

How Top Shot's Story Died — The Case Study

"At peak, in February 2021: $224 million in monthly transaction volume. 80,000 unique buyers."

"By December 2022: $5.4 million in monthly volume. 8,446 unique buyers. A 97.6% decline."

Three operational decisions drove the collapse:

  1. Oversupply. "Too many drops, too many Moments, too many packs. When everything is available all the time, nothing feels scarce, and the completion drive that makes collecting satisfying dies."

  2. The collecting experience atrophied. "The product stopped investing in the things that make collecting meaningful — set completion mechanics, community milestones, progression systems, the social rituals around building a collection."

  3. Price ran ahead of accessibility. "By the time mainstream collectors heard about Top Shot, prices were already through the roof."

The critical distinction on financial motivation:

"Celebrating big sales and price gains was not the problem. People want to make money with the things they spend time on — that is a feature, not a bug. The problem was that the financial story became the ONLY story, because the product gave collectors nothing else to celebrate. There were no set completion moments, no progression milestones, no collecting achievements worth sharing."

Monday Morning Test

"This week, look at your daily standup post. Does it describe tasks ('working on next pack,' 'reviewing creative assets,' 'sending emails') or outcomes ('shipped the drop that reactivated 200 lapsed collectors,' 'tested a new pack configuration that increased sell-through by 15%,' 'told the story that generated the most social shares this month')?"

"If it describes tasks, rewrite it in terms of outcomes. Not because your manager asked you to — because the way you describe your work shapes how you think about it. Tasks are a treadmill. Outcomes are an engine."

Operational Identity

"The engineers built the stadium. The designers made it beautiful. You run the show that fills it every night. Without you, the stadium is empty. Without you, there is no reason for anyone to come back tomorrow. Without you, the product is a static application that slowly bleeds users until it dies."

"You are not support. You are the show."

Key Principles Summary

Principle Core Insight
LiveOps IS the product The content layer is the primary value creation layer, not a maintenance function
Three layers, one priority Platform (quarterly), Engine (monthly), Content (daily/weekly) -- most time goes to Content
Content Engine > Content Treadmill Build systems that generate variety efficiently; marketplace, metagames, modular production, community, AI
Story is the operating system Every content decision starts with "What story are we telling?"
Emotional subsidy Tribal identity creates a price premium; product decisions either increase or decrease it
Small teams with big systems The system does the scaling; the people do the thinking
Outcomes, not tasks Frame standup posts and work in terms of what changed for collectors

Note: The full LiveOps Playbook is a 23-chapter document. This wiki page covers Part I (Philosophy). The full document is available at research-reports/LIVEOPS-PLAYBOOK-COMPLETE.md and as Google Doc ID 1hBhNAoq5n7_vfFfAXNJR-wBrCcYOz4Wlw-swreCXMoE. Additional operational playbooks for specific workflows (drops, pack cycles, Disney submission, partner approvals, tooling) are maintained as separate wiki pages in this directory.