Test the question, not the polish
An early build does not need to prove the whole game. It needs to answer one useful question. Is the central action understandable? Does the character invite curiosity? Do players want to try again when a plan fails?
A focused question makes rough work easier to share and feedback easier to interpret.
Separate confusion from preference
Not every reaction points to the same kind of problem. Confusion usually asks for clearer communication. Preference may simply show that the game has a point of view. We pay close attention to what players do, then use what they say to understand why.
Repeated hesitation matters more than a single suggested solution. Our job is to find the cause, not copy the prescription.
Protect the part with energy
Early tests are most valuable when they reveal the moment people lean forward. That moment may be smaller than the feature we expected them to notice, but it often contains the real promise of the project.
We leave each session with fewer assumptions, a sharper question, and a better idea of what deserves another round.