How to Launch LiveOps from Scratch. Pitfalls

What the talk is about

Alexander Shtachenko shares his experience launching LiveOps at different companies and explains why it rarely works from scratch. He covers three common problems: analytics that don't collect the needed data (such as session history), a "thin" server that can't segment and target each player (for example, finding their comfortable session for an offer), and a monolithic game where adding events or offers means rewriting code. Fixing all this after launch is slow and costly, so it should be planned during pre-production. His answer is a dedicated LiveOps department, universal tooling and dashboards reused across the whole game portfolio, and clearly defined roles, communication and goals. Useful for producers, game designers, analysts and studio owners planning LiveOps.