1. Focus Criticism on Changes, not Developers

This is the most important tip on this list. Use statements that focus solely on the changes. Using inflammatory language against developers will almost guarantee that your feedback is not as valuable as somebody who may have had similar feedback, but without the personal attacks. If you must ask whether a post is a personal attack, you should not be posting it.

2. Recognize Value of Data vs. Personal Experience

There are times where hard mathematical data will be the sole way to communicate that a change may not have achieved the intended result, or that it is causing other issues. It is also important to realize that changes can simply not “feel” right. Made up examples of each circumstance is below.


“According to the calculations here, the changes to Lava Whip did not actually buff the damage dealt as it was implied to by the developer note.”


“The new Rapid Strikes feels like the strikes are not quick enough.”

3. Avoid Generalization

The irony is that this is tip is a generalization, but it is nevertheless valuable to avoid generalizing feedback. When giving feedback, statements that attempt to speak for “the entire community” or “everyone” often do not truly reflect the thoughts of those it tries to. Additionally, feedback such as “this dungeon sucks, it’s too hard/easy” contributes nothing of value and is thus likely going to be disregarded by somebody reading it. Break down why it is too hard/easy using Tip #2 to build a piece of constructive feedback.

4. Feedback Channels

It is important to utilize the proper feedback channels when giving feedback so that it is delivered to the intended teams and receives the proper attention. Bugs and issues are best reported through in-game means via tickets and bug reports. Other feedback such as that which relates to content and combat is best delivered through the forums and official ESO social channels.

5. Feedback Implementation (or Lack Thereof)

Just because your feedback was not implemented immediately after you delivered it does not mean that it was not read and valued. Sometimes, a piece of feedback can be an inspiration for another change that happened, or maybe it was considered, but not implemented for any number of reasons.

6. Grammar and Readability

This is the least important tip, but make no mistake: feedback written with poor grammar can be interpreted as lacking thoughtfulness and effort. It is best to frame feedback in a way that is easy to read, and the point cannot be misinterpreted. Take the time to proofread and verify that the feedback is written effectively. If grammar is a struggle, consider using an online tool or asking a peer to review.


While it cannot be guaranteed that following these tips will make your feedback heard, it will prevent it from being immediately discarded. This is repeated for emphasis: do not attack or harass developers for implementing changes you disagree with or do not find value in. Doing so not only demonstrates that you are incapable of delivering feedback in a sophisticated manner, but it also can discourage developers from communicating further about changes in the future, which in turn affects the entire playerbase. Hiding behind the curtain of “being passionate” is not a valid defense for this behavior.