Dragon Age boss warns devs about player feedback “They’re not developers”

Game development is often framed as an exercise in listening—to the community, to players, and to feedback. But what happens when that advice hits a wall? Former Dragon Age producer Mark Darrah suggests that while developers should absolutely pay attention to their player base, they must temper that instinct with a crucial reality: listening is not the same as finding solutions.

In a recent discussion about game design, Darrah argues that players are incredibly valuable resources. They are phenomenal at identifying pain points—telling developers exactly where things feel unbalanced, frustrating, or confusing. They can signal where they get lost and what they genuinely dislike. Ignoring this immediate, raw feedback is a mistake; it means building a game in a vacuum.

However, the challenge lies in the second half of the equation: identifying solutions. Darrah points out that players are experts at spotting problems, but they are not developers. The proposed fixes they generate often miss the mark because they don’t possess the necessary systemic understanding to fix the root cause.

For example, a player might complain that enemy AI needs to be smarter. While this feedback is valuable, the actual problem might not be the AI itself, but an underlying issue with pathfinding or enemy survival rates. Developers need the insight to pick apart the stated complaint and understand the systemic problem underneath it.

Furthermore, Darrah cautions that the player community is not a single monolith. A group of players will range from casual story-focused enthusiasts to hardcore math nerds who demand complex systems and realism. If a studio focuses only on the loudest voices—often the most engaged segment—they risk creating systems that are enjoyable for one group but unconsumable by another.

Maintaining this balance is critical, especially for long-established studios dealing with diverse player bases. Focusing too heavily on satisfying the most vocal segment can lead to a narrow vision, potentially alienating those players who value complexity and realism over immediate gratification. It requires stepping back and asking: are we listening to the whole community, or just a select few?

Ultimately, true insight comes from blending qualitative feedback with quantitative data. Darrah advises developers to seek out diverse data sources—not just community chatter—by employing robust playtesting, telemetry analysis, and examining external market realities, such as sales trends for other titles. This multifaceted approach provides the crucial balance between player experience and creative vision.

As a final piece of advice, Darrah reminds us to always remember the original artistic vision. Feedback should inform development, but it must never override the core identity of the game. If a suggestion comes from the community but fundamentally violates what the developer intends the game to be, it may not be the best path forward.