If you are having trouble deciding on what actions to take based on player feedback, it’s a sign that your goals/pillars lack clarity. Go work on that instead.

When deciding which player feedback to act on, I follow these key steps: 1. Align with Game Vision: If the feedback supports the core goals and design philosophy of the game. If it fits with the overall direction, it’s worth considering. 2. Evaluate Gameplay Impact: Does it improve balance, engagement, or the player experience? 3. Look for Trends: I pay attention to recurring feedback. If multiple players are pointing out the same issue, that's problematic. 4. Consider Feasibility: I evaluate the time, cost, and resources required to implement the feedback. High-impact suggestions that are feasible get prioritized. 5. Test and Validate: Before making any final decision, ensure the suggestion will have a positive impact on the game.

Ich füge erstmal alle Kritik als Tasks in Jira ein. Dann bewerte ich, zusammen mit den Gamedesignern, sie mit Complexity, Impact, Priorität und Risiko. Dadurch kann man sehr gut erkennen, welche Ideen einfach und schnell umsetzbar und gleichzeitig den größen Impact aufs Spiel haben. Bisher konnte jede Meinungsverschiedenheit mit Zahlen und Fakten aus dem Weg geräumt werden.

I think it's worth noting that players often are blind to what they actually want, even the most literate amongst them, it's critical to work to find the root cause of common complaints, as they often share one. That said sometimes it's OK to act on none; players can frequently expect a game to conform to their expectations that they brought in, rather than living in the given experience. This is true across all software design and requires meeting people partway.

When debating player feedback with your team, as I consider these strategies to decide which suggestions to act on: Evaluating Player Feedback: 1. Impact: Assess gameplay and user experience. 2. Feasibility: Consider resources and technical limits. 3. Frequency: Identify recurring themes. 4. Alignment: Check game vision and goals. Additional Strategies: 1. Categorize feedback. 2. Prioritize using MoSCoW. 3. Analyze metrics. 4. Community engagement. Conflict Resolution: 1. Open discussion. 2. Consensus. 3. Assign decision-maker. Tools: 1. Feedback tracking. 2. Community forums. 3. Analytics. 4. Player surveys. By following these steps, you'll effectively evaluate player feedback and improve your game.

When deciding which player feedback to act on, focus on suggestions that align with the game's overall vision and goals. Prioritize feedback that's mentioned frequently or addresses major gameplay issues affecting player experience. It's also important to consider the feasibility of implementing changes within your team's resources and timelines. Balancing immediate fixes with long-term improvements can help you make the most impactful decisions while keeping the player community engaged.

Categorize feedback: Bugs, gameplay, new features, UI improvements. Assess impact: Player experience, retention, engagement, revenue. Frequency: Prioritize common requests. Feasibility: Consider development complexity, resources, and timelines. Align with game vision: Ensure suggestions fit the game’s long-term goals. Competitive analysis: Look at industry trends. Data-driven validation: Use analytics and A/B testing. Community engagement: Keep players informed.

You shouldn't make decisions based solely on player feedback. Decisions should be based on multiple sources of input, with player feedback either adding weight to previously considered topics or serving as a starting point for further investigation.

We make an overview of what was good enough and what wasn't. We use this scale: - feedback on things that could be gamebreaking, - feedback on things that impact immersiveness, - feedback on accessibility, - enhancements of the game - personal opinions First get the obvious things in these categories, Everything in enhancements and "unknown" we put next to our gamedesign document to see if they align with our set goals for the game. Finally teammembers can vouch for their favourite enhancements to put our soul in the game. Of course all tests start with a plan on what we look for and we have a document that sets the goals for the game or development cycle.

This is why writing and evaluating a Game Design Document for your game prior to starting development is so important. The core loops, values, and beats of your game should be so well defined before hand that they provide a guide in every decision you have to make. In addition to that, there should be a designated Product Person or Game Designer who has ownership and authority to make decisions to ensure a game follows and adheres to a central vision.