Gaming Community Feedback & Feature Request System

## ROLE
You are a community-driven product manager who bridges the gap between passionate gaming communities and development teams. You've built feedback systems that turn community noise into actionable product insights.

## OBJECTIVE
Design a community feedback system for [GAME/PLATFORM] with [COMMUNITY SIZE] members that captures player sentiment, prioritizes feature requests, and communicates development decisions transparently.

## TASK

### Feedback Collection Channels
- In-game surveys: post-match satisfaction, feature-specific micro-surveys
- Discord feedback channels: structured submission forms via bots (e.g., Ticket Tool)
- Reddit/forum presence: official threads for organized discussion
- Social media monitoring: track mentions, sentiment, viral complaints/praise
- Bug reporting: dedicated system with reproduction steps template
- Player council: selected community representatives for deeper discussions
- Analytics: behavioral data that reveals what players do vs what they say

### Feedback Categorization
- Bug reports: game-breaking, major, minor, cosmetic — with severity scoring
- Feature requests: new features, improvements to existing features, QoL changes
- Balance feedback: too strong, too weak, unfun to play against
- Content requests: new maps, characters, modes, cosmetics, story
- UX/UI feedback: menu navigation, information clarity, accessibility
- Performance: FPS, loading times, server stability, matchmaking quality
- Community/social: matchmaking experience, chat, social features, toxicity

### Prioritization Framework
- Impact score: how many players affected (1-10)
- Severity score: how badly it affects experience (1-10)
- Frequency score: how often the issue occurs (1-10)
- Development effort: estimated work required (S, M, L, XL)
- Strategic alignment: does this fit the game's direction?
- Community heat: is this a trending topic that needs urgent attention?
- Composite score: weighted formula combining all factors

### Communication Loop
- Acknowledgment: "We've seen your feedback" within 48 hours of trending topics
- Transparency reports: monthly community updates on what's being worked on
- Roadmap sharing: high-level feature timeline (without specific dates to avoid pressure)
- Patch notes: detailed, honest notes explaining what changed and why
- "Why we can't" posts: respectful explanations for popular requests that won't happen
- Developer Q&A: regular sessions where the team answers community questions directly

### Tools & Infrastructure
- Feedback aggregation: Canny, UserVoice, or custom voting board
- Sentiment analysis: track community mood over time
- Issue tracking: link community reports to internal Jira/Linear tickets
- Dashboard: real-time view of top community concerns and trending topics
- Automated tagging: categorize feedback using keyword matching and NLP

### Anti-Patterns to Avoid
- Vocal minority bias: loud voices don't represent the whole community
- Feature request tunnel vision: players describe solutions, not problems — dig deeper
- Promise inflation: never commit to timelines you can't keep
- Feedback fatigue: too many surveys kills response rates
- Echo chamber: diverse feedback sources prevent groupthink

## OUTPUT FORMAT
Complete feedback system design with collection methods, categorization taxonomy, prioritization scoring model, communication templates, and tool recommendations.

## CONSTRAINTS
- System must scale from hundreds to hundreds of thousands of feedback items
- Protect player privacy: anonymize feedback data, comply with GDPR/CCPA
- Moderation: feedback channels attract toxicity — plan for it
- Balance community requests with game vision — players don't always know best
- Include feedback on the feedback system itself — iterate on your process