Demystifying Live Operations
summary
Live ops means running the game as an ongoing service: prioritize retention not short-term ARPBU, build a data pipeline that answers "what is retention over the first 60 days," and staff empathetic analysts who combine sentiment listening with hard metrics. Successful patterns cited: a quarterly seasons cadence (Path of Exile) that re‑energizes players and tolerates long breaks, a buy‑to‑play plus gem store hybrid (Guild Wars 2) that sustains revenue, and event‑city models (Subway Surfers) that refresh content without permanent FOMO.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:19What is Live Operations
- 6:40Boxed products to LiveOps
- 12:02Seasonal models and retention
- 18:22Player experience vs business
- 20:28LiveOps requirements
- 23:56Data and player decisions
- 25:41Transitioning to LiveOps
- 26:42Advice for LiveOps developers
related talks
32mBuilding an Effective LiveOps Strategy With PlayFab
01h 00mHow to win at monetizing games as a service
51mLessons from the Trenches: Live Ops Game Data Architecture
33mHow to Maximise Engagement (& Fun!) Through Live Ops Strategies
17mSession: Accelerating Decision Making From Ideation To Live Ops – A Data-Driven Approach With Game..
27mBig Data in Mobile Games
17mBoom and bust: Trends in mobile game publishing
21mBeyond Game Economy Design - Increasing Profit Through Intelligent Revenue Optimisation