Generate Feature Ideas

How do you come up with a new feature idea for a live-service game product? Describe a structured process for identifying opportunities, selecting the right user problem, and turning that into a feature concept. ### Constraints & Assumptions - Feature ideas should come from user/player pain, business goals, and feasible execution, not random brainstorming alone. - Consider live-service constraints such as retention, monetization health, player fairness, economy balance, event cadence, and production capacity. - Use evidence before prioritizing a concept. - Include metrics and guardrails. ### Clarifying Questions to Ask - What is the goal: new-player activation, returning-player reactivation, engagement, monetization, social play, or retention? - Which player segment is in scope? - What recent data or player feedback triggered the need for new ideas? - Are we designing a temporary event, permanent feature, or experiment? ### Part 1 - Identify The Opportunity How would you find the right player problem? #### What This Part Should Cover - Inputs from cohort data, funnel analysis, telemetry, player research, reviews, support, community channels, competitive analysis, and strategy. - Clear player segment and job to be done. ### Part 2 - Generate Feature Concepts How would you translate the problem into candidate features? #### What This Part Should Cover - Multiple options before choosing one. - Examples such as returner questline, catch-up pass, build recommendation, social re-entry prompt, or live event. - Player value and business value. ### Part 3 - Prioritize And Validate How would you select the right idea? #### What This Part Should Cover - RICE or impact/effort/confidence framework. - Prototype, beta, A/B test, or limited event rollout. - Risks such as economy inflation, pay-to-win sentiment, veteran-player resentment, or production cost. ### Part 4 - Define Success What metrics would show whether the feature worked? #### What This Part Should Cover - Retention, session count, feature completion, conversion to regular play, satisfaction, revenue quality, and guardrails. ### What a Strong Answer Covers - Shows a repeatable ideation process. - Grounds ideas in evidence and player segments. - Prioritizes with tradeoffs, not taste. - Protects long-term game health. ### Follow-up Questions - How would you avoid copying competitors blindly? - What if whales love the feature but casual users hate it? - How would you test without disrupting the game economy? - What guardrail would make you stop the feature? - How would you involve design and live-ops teams?