How to give feedback that helps

THE FEEDBACK LOOP THAT RUNS THE COMMUNITY

The point is to help the person who made the game. A useful review gives them evidence they can act on, not a score for the reviewer.

What makes feedback useful?

Start with the moment you experienced, then say what you expected and what happened instead. A builder can test a concrete observation; they cannot test “it felt off.”

A few rules keep the system honest:

• Play the build when you can, rather than judging from a screenshot alone.
• Say what happened to you before prescribing a fix.
• Avoid drive-by comments such as “looks cool” when you can name a specific moment that changed your reading of the game.

Feedback is not publicly ranked or published as a personal score. The point is to improve the build, not to create a public status competition.

What makes a review comment actually helpful?

Play the game before you write anything. A comment based on a trailer or a screenshot reads differently from one written by someone who hit the actual wall, and owners notice the difference immediately.

Describe what happened to you, not what the developer should do about it. “I stopped paying attention around the third room because nothing new had shown up yet” tells the owner something true about their game. “You should add more enemy variety” tells them your opinion, and it’s easy to set aside an opinion that arrived without evidence behind it.

Name the exact moment. “The pacing feels off” forces the owner to guess where. “The pacing feels off, specifically the stretch between the second checkpoint and the boss door” is something they can act on that afternoon.

Separate taste from friction. Disliking the pixel art style is taste. Not being able to tell your health bar from your ammo counter at a glance is friction. Both are worth saying, but say which one you’re giving, because an owner who mistakes a taste comment for a bug report chases the wrong fix.

One thing to keep and one thing to fix beats ten scattered notes. A wall of text makes the owner triage your comment before they can use it. Find the strongest observation in each direction and stop.

What should you do as a thread owner?

Ask a specific question in your post. “What do you think?” produces vague answers. “Does the double jump feel too floaty in the second area?” produces comments you can actually score against.

Value comments that changed your build, not the ones that were nicest to read. A reviewer who told you something true and uncomfortable is more useful than one who only offered flattering encouragement.

Respond to your reviewers, even briefly. Telling someone what you changed because of their note, or why you didn’t, closes the loop, and it’s the reason a good reviewer comes back to your thread instead of someone else’s.

Why review other people’s games at all?

Reviewing sharpens your own design eye faster than working on your own project does, because you’re not attached to the decisions. Spotting a confusing menu is much easier when you didn’t build the menu yourself. Do enough of it and you start catching the same problems in your own game before anyone has to point them out.

Looking carefully at other people’s work improves your own eye for confusing moments. That habit transfers straight back to your own game without needing a public score attached to it.

Going deeper

Structured playtest notes beat a running commentary. Instead of typing reactions as they occur to you, split each note into what happened, when it happened, and which of three buckets it belongs to: feel, content, or clarity. Feel is how an action responds under your hands. Content is what’s actually in the level or the dialogue. Clarity is whether the game told you what to do. Owners fix these in different places, so folding them into one note like “this level feels bad” sends them looking in the wrong file.

Recording your session, or at least noting the timestamp where something broke, removes the biggest source of lost information in text feedback: you describing a moment from memory a few minutes later, after hindsight has already smoothed it over. A raw clip catches the confusion before you’ve explained it away to yourself.

None of this replaces actually playing. A structured template filled in from watching someone else’s stream is worse than three honest sentences from your own playthrough.

This whole loop runs inside the AI Game Dev Org Discord’s feedback forum — the fastest way to get good at giving feedback is to leave a few comments today.