Player Feedback, Creative Vision, and Knowing What to Change
retained text
Being player-centric doesn't mean designing by committee I've been thinking quite a bit lately about the relationship between a developer's creative vision and the experience players actually have. I believe we have a responsibility to respect our players, but I don't believe that means giving them everything they ask for. Sometimes those two things can even be at odds. My latest experience with this has come from founding playtesting for an RPG I'm developing. Different testers have had noticeably different experiences with difficulty, progression, and how they engage with the world. It's tempting to look at those differences and immediately start changing things. But I think that can be a mistake. If a player struggles with a mechanic, is the mechanic poorly designed? Is the challenge intentional? Or have I failed to communicate something the player needs to understand? Those are three very different problems, and they don't necessarily have the same solution. I think part of our responsibility as developers is to understand the distinction before making changes. Otherwise, we risk removing meaningful challenges when we should be improving communication, or defending poor design simply because it matches our original intentions. There's also something to be said for trusting players. They don't necessarily need every decision explained or every obstacle softened. Sometimes discovering how to overcome a challenge is precisely what makes the experience rewarding. For me, player-centric development isn't about putting the developer or the player entirely in charge. It's about respecting both the creative vision and the person experiencing it. And I think knowing when to preserve something is just as important as knowing when to change it.
document fetched 2026-11-15 00:24 · canonical https://reddit.com/r/gamedev/comments/1xvpvp9/player_feedback_creative_vision_and_knowing_what