Phase 1. Stakeholder discovery & problem framing
Phase 1. Stakeholder discovery & problem framing
From Communication Chaos to Structured Growth
From Communication Chaos to Structured Growth
From Communication Chaos to Structured Growth
From Communication Chaos to Structured Growth
Context: Before designing, I needed to understand why a successful Discord community required a dedicated web platform. My goal was to define the core problems a website should solve that Discord couldn't.
Context: Before designing, I needed to understand why a successful Discord community required a dedicated web platform. My goal was to define the core problems a website should solve that Discord couldn't.
Context: Before designing, I needed to understand why a successful Discord community required a dedicated web platform. My goal was to define the core problems a website should solve that Discord couldn't.
Why Discord was no longer enough
Why Discord was no longer enough
Why Discord was no longer enough
The Approach: Stakeholder Interviews
The Approach: Stakeholder Interviews
I prepared a structured set of questions to align the vision:
I prepared a structured set of questions to align the vision:
Product Goals: What is the product vision?
Product Goals: What is the product vision?
Community Dynamics: How do users interact today?
Community Dynamics: How do users interact today?
Success Criteria: What metrics define a win?
Success Criteria: What metrics define a win?
Constraints: What are the technical and resource limits?
Constraints: What are the technical and resource limits?
Key insight:
Key insight:
The team had a strong technical vision, but less clarity around user motivation — what would actually make developers return to the platform and use it long-term.
The team had a strong technical vision, but less clarity around user motivation — what would actually make developers return to the platform and use it long-term.
Igrovary Level-Up
Igrovary Level-Up
Feature
Discord Limitation
Platform Opportunity
Searchability
Info is scattered and lost in chat history.
Centralized, searchable knowledge base.
Showcasing
No permanent space for project visibility.
Dedicated gallery for projects and portfolios.
Navigation
Poor structure for resources or events.
Structured hubs for Jams and Collaboration.
Feature
Discord Limitation
Platform Opportunity
Searchability
Info is scattered and lost in chat history.
Centralized, searchable knowledge base.
Showcasing
No permanent space for project visibility.
Dedicated gallery for projects and portfolios.
Navigation
Poor structure for resources or events.
Structured hubs for Jams and Collaboration.
Design question
Design question
How might we build a web platform that complements the existing Discord community while solving its limitations and supporting long-term growth for indie game developers?
How might we build a web platform that complements the existing Discord community while solving its limitations and supporting long-term growth for indie game developers?
Why This Phase Mattered
Why This Phase Mattered
This phase helped me align the project around a shared understanding:
This phase helped me align the project around a shared understanding:
Integration over Replacement:
Integration over Replacement:
Discord is being extended, not replaced.
Discord is being extended, not replaced.
Value over Complexity
Value over Complexity
The challenge is user motivation, not just building features.
The challenge is user motivation, not just building features.
Scalability:
Scalability:
The platform must support multiple roles (Indie Devs, Artists, Publishers) without clutter.
The platform must support multiple roles (Indie Devs, Artists, Publishers) without clutter.