The Challenge
In 2015, gamers had terrible communication options. TeamSpeak and Ventrilo were clunky and required self-hosting. Skype was laggy and designed for business calls. No platform was built specifically for gaming communities — persistent servers, low-latency voice, and text channels.
Citron had built a game called Fates Forever that failed commercially but had a passionate community. He noticed something: players loved the social experience more than the game itself.
The Approach — Tools in Action
- Technology: High latency, poor audio quality, no mobile support
- UX: Complex setup, ugly interfaces, required IP addresses to connect
- Community: No persistent servers, no text alongside voice, no roles/permissions
- Price: TeamSpeak required paid hosting; Skype was free but terrible for groups
Discord addressed every root cause: low-latency voice (technology), beautiful UI with one-click invite links (UX), persistent servers with channels and roles (community), and free for all users (price).
SCAMPER generated key features:- Combine: Voice chat + text chat + file sharing in one platform
- Eliminate: Self-hosting, IP addresses, paid servers
- Adapt: Slack's channel model for gaming communities
- Substitute: Server browser with invite links (frictionless growth)
The Outcome
Discord transcended gaming to become a general communication platform:
- 200M+ monthly active users
- 19M+ active servers across gaming, education, music, crypto, and more
- Valued at $15B (turned down a $12B Microsoft acquisition offer)
- Revenue growing through Nitro subscriptions and server boosts
- Became the de facto community platform for crypto projects, open-source, AI, and education
- Proved that the best products are often discovered when your original idea fails — if you pay attention to what users actually love
Key Takeaway
When your product fails, pay attention to which PART users loved. Citron's game failed, but the community features thrived. The successful product was hiding inside the failed one — you just have to see it.
Tools Used in This Story
Ishikawa Diagram
Problem SolvingIdentify root causes of problems
SCAMPER
Problem SolvingGenerate creative ideas using a structured checklist of provocations
Reinforcing Feedback Loop
Systems ThinkingUnderstand the force behind exponential changes