Player Feedback Analysis & Prioritization Framework

## ROLE

You are a senior community insights manager and player research lead with 10+ years of experience translating player sentiment into actionable product decisions. You have managed feedback pipelines for games with millions of players, working across Reddit, Discord, Steam reviews, social media, in-game surveys, customer support tickets, and focus groups. You understand the critical distinction between vocal minority complaints and genuine widespread issues, and you know how to triangulate qualitative feedback with quantitative telemetry to build a complete picture of player needs. You have successfully influenced roadmap priorities by presenting player insights to executive stakeholders.

## OBJECTIVE

Create a comprehensive player feedback analysis and prioritization framework for [GAME TITLE OR TYPE: live service game / indie title / mobile game / MMO / competitive multiplayer] with a community of [COMMUNITY SIZE: 10K / 50K / 100K / 500K / 1M+] active players across [CHANNELS: Reddit / Discord / Steam reviews / Twitter-X / official forums / in-game feedback / customer support / YouTube-Twitch comments / app store reviews]. The framework should serve [STAKEHOLDERS: game designers / product managers / community managers / executive leadership / QA team] and integrate into a [CADENCE: weekly / bi-weekly / monthly] reporting cycle.

## TASK: FEEDBACK ANALYSIS SYSTEM

### Multi-Channel Collection Infrastructure
Design the data collection architecture for each feedback channel:

**Community Platforms (Reddit, Discord, Forums):** Set up monitoring for [SUBREDDIT OR COMMUNITY: r/yourgame / official Discord server / Steam community hub]. Use [TOOLS: manual monitoring / automated scraping / community management platforms like Sprout Social, Hootsuite, or custom Discord bots] to capture posts, comments, and threads. Define collection rules: capture all posts with [THRESHOLD: 10+ upvotes / 5+ replies / moderator-flagged / developer-tagged]. For Discord, monitor [CHANNELS: feedback channel / bug-report channel / suggestions channel / general discussion] and flag messages with [TRIGGER: specific reaction emoji / keyword matches / sentiment spike detection]. Capture both the original post and the top [NUMBER: 5-10] responses to understand community consensus versus dissent.

**Review Platforms (Steam, App Store, Google Play):** Aggregate reviews from [PLATFORMS: Steam / App Store / Google Play / Metacritic / OpenCritic] on a [FREQUENCY: daily / weekly] basis. Track review score trends over time with special attention to score changes around [EVENTS: patches / content updates / pricing changes / competitor launches]. For Steam specifically, monitor Recent Reviews separately from All Reviews to detect sentiment shifts. Categorize reviews by [TAGS: gameplay / performance / content / monetization / community / bugs / positive-general / negative-general] using [METHOD: manual coding / NLP classification / AI-assisted tagging].

**In-Game Feedback Systems:** Design lightweight in-game feedback collection that does not disrupt gameplay. Implement [MECHANISMS: post-match rating (1-5 stars) / contextual micro-surveys (max 2 questions) / bug report tool with screenshot capture / "Was this fun?" pulse check after new content / NPS survey triggered at Day 7, Day 30, and Day 90 milestones]. Target a response rate of [RATE: 5-15%] by keeping surveys under [TIME: 15 seconds] and offering [INCENTIVE: small in-game currency reward / cosmetic item / badge].

**Customer Support Tickets:** Integrate [SUPPORT PLATFORM: Zendesk / Freshdesk / custom ticketing] data into the feedback pipeline. Categorize tickets by [TAXONOMY: bug report / account issue / payment problem / gameplay complaint / feature request / toxicity report / cheat report]. Track ticket volume trends and identify [SIGNAL: spikes in specific categories that correlate with game updates or events].

### Sentiment Analysis & Categorization
Build the analytical framework for processing raw feedback into structured insights:

**Taxonomy Development:** Create a hierarchical feedback taxonomy with [NUMBER: 8-12] top-level categories and [NUMBER: 3-8] subcategories each. Top-level categories: [CATEGORIES: Core Gameplay / Balance & Meta / Content & Features / Performance & Technical / Monetization & Economy / Social & Community / UI/UX & Quality of Life / Matchmaking & Competitive / Narrative & Lore / Accessibility / New Player Experience / Platform-Specific Issues]. Within each, define specific subcategories — for example, under Balance & Meta: [SUBCATEGORIES: character/hero balance / weapon balance / meta staleness / power creep / skill gap / ranked system fairness].

**Sentiment Scoring:** Apply a [SCALE: 5-point / 7-point / continuous] sentiment scale to each feedback item: strongly negative, negative, neutral, positive, strongly positive. Use [METHOD: manual analyst rating / NLP sentiment analysis using VADER or custom model / AI-assisted sentiment classification with human validation]. Track aggregate sentiment by category over time to identify trending issues before they become crises.

**Volume & Velocity Tracking:** For each feedback category, track absolute volume (number of mentions per week), relative volume (percentage of all feedback), and velocity (week-over-week change). Set automated alerts when any category exceeds [THRESHOLD: 2x its rolling 4-week average volume] or when a new topic not in the existing taxonomy suddenly appears in [THRESHOLD: 50+ / 100+ / 500+] feedback items within [WINDOW: 48 hours / 1 week].

**Signal vs. Noise Filtering:** Implement techniques to separate actionable signal from noise. Weight feedback by [FACTORS: author's play time / author's spend history / community endorsement (upvotes, agrees) / uniqueness of the point / specificity of the description / constructiveness of the suggestion]. Identify coordinated feedback campaigns (review bombing, Discord raids, influencer-directed campaigns) and flag them for separate analysis — these represent community organizing rather than independent sentiment.

### Prioritization Framework
Convert analyzed feedback into a prioritized action list:

**Impact-Effort Matrix:** Score each identified issue or feature request on two axes. Impact Score (1-10) based on [FACTORS: estimated number of affected players / severity of impact on experience / correlation with churn risk / revenue impact / brand reputation risk / strategic alignment]. Effort Score (1-10) based on [FACTORS: engineering complexity / design dependencies / art and content requirements / QA testing scope / risk of unintended side effects / cross-platform considerations]. Plot issues on a 2x2 matrix: Quick Wins (high impact, low effort — do immediately), Strategic Projects (high impact, high effort — plan for next season), Easy Fills (low impact, low effort — batch into QoL updates), and Deprioritize (low impact, high effort — revisit if circumstances change).

**Community Temperature Index:** Create a composite score representing overall community health, aggregating [COMPONENTS: average review score trend / social media sentiment index / support ticket volume per 1000 DAU / community moderator stress indicators / influencer sentiment summary / forum toxicity level]. Track this index weekly and set thresholds for escalation: green (healthy), yellow (emerging concerns — increase monitoring), orange (significant dissatisfaction — schedule response), red (crisis — activate communication plan immediately).

**Stakeholder Reporting:** Build report templates for each audience. For game designers: detailed breakdown of gameplay and balance feedback with specific player quotes and video clips illustrating the issue. For product managers: prioritized feature request backlog with impact scores and estimated effort. For executive leadership: one-page community health dashboard with traffic light indicators and a top-5 action items list. For community managers: prepared talking points addressing the top [NUMBER: 3-5] community concerns with approved messaging.

### Feedback Loop & Communication
Close the loop between player feedback and development response:

**Acknowledgment Protocol:** When a significant feedback trend is identified, publish a community acknowledgment within [TIMEFRAME: 48 hours / 1 week] confirming the team is aware. Use [FORMAT: developer blog post / Discord pinned message / social media post / in-game news]. Acknowledgment does not require a solution — simply confirming "we hear you and we're investigating" dramatically reduces community frustration.

**Resolution Tracking:** Maintain a public or semi-public tracking board showing [STATUS: acknowledged / investigating / in development / testing / shipped / won't fix with explanation] for the top community-requested changes. Update status [FREQUENCY: weekly / bi-weekly]. Celebrate shipped fixes by referencing the original community feedback in patch notes: "Based on your feedback, we've improved [FEATURE]."

**Post-Implementation Validation:** After shipping a change driven by feedback, measure whether the targeted sentiment category improves. Track the feedback volume and sentiment score for the specific issue for [WINDOW: 2-4 weeks] post-patch. If sentiment does not improve, initiate a follow-up investigation — the fix may not have fully addressed the root cause, or new concerns may have emerged.