Give every tester the same task
Ask someone to complete one level, reach a target score, or try one named mechanic without coaching. Record where they pause, what they click, and which instruction they read twice. Avoid telling them how to play during the first attempt; explanation can hide the exact cue that needs improvement.
Use a short feedback script
After the attempt, ask: “What did you expect when you pressed that?” “Which rule was unclear?” and “What would you try next?” Keep suggestions separate from observations. Several people asking for more levels does not tell you whether the current first level communicates its goal.
Turn feedback into a small revision
Group notes by a specific moment, such as missed input, an unnoticed goal, or a confusing restart. Choose the most repeated friction point, revise one instruction or cue, then ask a new tester to repeat the same task. Do not tune only for the most vocal participant; compare individual observations with the intended audience and design goal.
Because the shared version is public, invite people to use the public link and leave only feedback they are comfortable sharing. Avoid putting private playtest notes or personal participant information into the game prompt. Keep the revision log focused on the game behavior, not on labeling the people who tested it.
Questions about playtesting a game with your audience
Should I ask testers what features they want?
You can collect ideas later, but first ask what they expected and what happened. Behavior and confusion reveal whether the current loop works before a wishlist expands scope.
How many people should I test with?
Start with a few separate sessions to identify obvious confusion, then test again after a focused revision. Treat findings as signals to investigate, not as a universal result from a large audience.