Focus on What Best Supports Improvement
On this page
Receiving feedback is a crucial part of the development process, and it is essential to be prepared to accept criticism with a constructive mindset. Remain positive when hearing critique from your playtesters. Always keep in mind that criticism is a tool for improvement, and it should not be taken literally or personally. Sometimes, playtesters will raise valid points, but other times their perspectives may not align with your design intentions.
Understanding Intentional Design Decisions
Example:
Consider a boss that appears for the first time in the game. During this initial encounter, players are unable to defeat the boss and must evade its attacks until the only exit door opens, allowing them to escape. Later in the game, players gather specific components to craft a unique weapon that can defeat this boss. Some players may express frustration at feeling powerless during the first encounter and might complain. However, it is important to recognize whether this design is intentionally meant to build tension and anticipation. Does this scenario contribute to the excitement of your game? Is it part of the experience you intended to deliver?
The Designer’s Role in Navigating Feedback
When evaluating feedback from playtesters, allow their input to help you identify problems, but do not let it dictate your design direction. The purpose of playtesting is to understand what elements players enjoy and what they do not. While you may feel inclined to fulfill every request or suggestion, remember that you, as the designer, are ultimately responsible for shaping the game. You possess a comprehensive understanding of how each feature interacts with others, and how changing one component may negatively impact another. Therefore, it is your responsibility to decide which aspects should be adjusted and which should remain unchanged.
Identifying Valuable Feedback
Truly constructive feedback often comes from playtesters who are capable of articulating specific issues and even suggesting potential solutions. Others may offer less helpful commentary by voicing general dissatisfaction with features that may, in fact, serve your design goals—as illustrated in the earlier example. However, if multiple playtesters raise the same concern, it may warrant closer examination.
When playtesters propose solutions, avoid giving immediate evaluations of their ideas. Instead, take careful notes for later consideration. It is vital not to rush into implementing their suggestions without thorough analysis. All data and comments gathered during playtesting sessions serve as raw information that requires proper evaluation. Consider who is offering the feedback and how many individuals express the same concern. Refrain from making changes until you are confident that a revision will improve the player experience. Your objective is to identify the true source of design problems, using player feedback as a guide—not a directive.
Turning Bugs into Features
During development, it is possible that one or more playtesters may encounter a glitch or bug that unexpectedly contributes to a more engaging and emotionally resonant gameplay experience. In such cases, do not immediately categorize the issue as something to be fixed. Instead, analyze whether the bug can be transformed into a deliberate and beneficial feature within the game.