Company culture - Influencing live operations
summary
Panelists from Lockwood Publishing, EA Tracktwenty, Oktagon Games and Wooga describe live ops as continuous player service that needs fast feedback, tooling and clear roles: reactive on-call engineers, campaign teams, and separate feature teams; examples include 10 people on Magic the Gathering Puzzle Quest and a June's Journey core team of 34. Teams recycle staff between development and live, build tools after soft launch, use an integrated help shift for direct player contact, and value thoughtful communication, ownership and speed over perfectionism.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:33Meet the speakers
- 1:44What is life ops
- 3:22Life ops teams
- 5:19Company culture influencing life ops
- 8:45Game development vs live service
- 17:40Team size
- 28:09Learning by doing
- 30:35Most influential company value
related talks
21mManaging live operations game design
22mWhat does live ops mean for your indie game?
52mLet's Talk About LiveOps
25mChallenges of opportunities of operating live games
38mPanel: Interaction & Iteration: Best Practices for Getting the Most out of Your Live Ops Strategy.
59mShaking Up Publishing For Living Games
46mLive ops and their importance for your game
47mWhat are the Challenges of Running Live Ops Across Different Game Genres?
