For Scopely's Star Trek Fleet Command, what's the optimal trade-off between introducing new content and maintaining game stability?

Introduction

The optimal trade-off between introducing new content and maintaining game stability for Scopely's Star Trek Fleet Command is a critical challenge in the mobile gaming industry. This scenario involves balancing user engagement through fresh content against the risk of technical issues that could harm the player experience. I'll analyze this trade-off by examining the product ecosystem, key metrics, and potential experiments to inform our decision-making process.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming Star Trek Fleet Command is a successful mobile game with a large, engaged player base. Could you confirm the game's current market position and player demographics?

Why it matters: Helps tailor the solution to the game's specific audience and competitive landscape. Expected answer: Top-grossing strategy game with a mix of casual and hardcore players, primarily 25-45 years old. Impact on approach: Would influence the balance between catering to different player segments.

• Business Context: Based on the mobile gaming model, I'm thinking in-app purchases are a primary revenue driver. How does new content typically impact revenue, and what's our current content release cadence?

Why it matters: Helps quantify the potential upside of new content against stability risks. Expected answer: New content drives 20-30% revenue spikes; current cadence is monthly major updates. Impact on approach: Would inform the frequency and scale of content updates we consider.

• User Impact: I'm guessing player retention is crucial for long-term success. How sensitive are our players to game instability, and what's our current churn rate?

Why it matters: Helps assess the potential downside of stability issues. Expected answer: Players are moderately sensitive; current monthly churn rate is around 5-7%. Impact on approach: Would influence how much we prioritize stability over new features.

• Technical: Considering the complexity of mobile game development, what's our current QA process, and how often do we encounter stability issues post-release?

Why it matters: Helps understand the technical constraints and risks involved. Expected answer: Two-week QA cycle; minor issues in 10% of releases, major issues in 1-2% of releases. Impact on approach: Would impact how we balance development time between new features and stability improvements.

• Resource: Given the ongoing nature of mobile game development, how is our team currently split between new content creation and maintenance/stability work?

Why it matters: Helps understand current resource allocation and potential for adjustment. Expected answer: 70% new content, 30% maintenance/stability. Impact on approach: Would inform recommendations on team structure and resource allocation.