Should Discord prioritize new features for gamers or expand its appeal to non-gaming communities?

Introduction

The trade-off we're examining today is whether Discord should prioritize new features for gamers or expand its appeal to non-gaming communities. This decision is crucial for Discord's growth strategy and long-term positioning in the social communication space. I'll analyze this trade-off by considering user impact, business implications, and technical feasibility, ultimately providing a recommendation based on data-driven insights and strategic considerations.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Discord's current user base and market position. Could you share some insights on the current split between gaming and non-gaming users on the platform?

Why it matters: Helps understand the starting point and potential impact of shifting focus Expected answer: 70-80% gaming, 20-30% non-gaming Impact on approach: A higher non-gaming percentage might justify faster expansion

• Business Context: Based on Discord's revenue model, I'm curious about the monetization differences between gaming and non-gaming communities. How do these segments compare in terms of Nitro subscriptions and server boosts?

Why it matters: Informs the financial implications of focusing on either segment Expected answer: Gaming communities have higher monetization rates Impact on approach: If true, would need to consider how to maintain revenue while expanding

• User Impact: Considering Discord's core features, I'm wondering about the feature usage patterns between gaming and non-gaming users. Are there significant differences in how these groups use voice channels, screen sharing, or other key features?

Why it matters: Helps identify which features to prioritize or adapt for different user segments Expected answer: Gaming users likely use voice and screen sharing more frequently Impact on approach: Would influence feature development priorities for each segment

• Technical: Given Discord's current architecture, I'm thinking about the scalability of adding new features for different user types. Are there any major technical constraints or considerations we should be aware of?

Why it matters: Determines the feasibility and timeline of implementing new features Expected answer: Current architecture is flexible, but may require some refactoring Impact on approach: Would affect the timeline and resource allocation for new feature development

• Resource: Looking at our current team structure, I'm curious about our capacity to simultaneously develop features for both gaming and non-gaming users. Do we have dedicated teams for different user segments, or would this require a reorganization?

Why it matters: Influences the feasibility of pursuing both strategies concurrently Expected answer: Current teams are primarily focused on gaming features Impact on approach: Might need to consider team restructuring or hiring for non-gaming focus