How can I separate a confusing rule from a confusing prototype component?
Quick answer
Record where players hesitate, what they say or do, and what information they were using. Then check one possible cause at a time: paraphrase the rule without changing the component, show the same information with a clearer temporary component, or ask the player to describe the choice and its consequences. Treat these checks as clues, not proof; more than one cause can contribute to the same pause.
The question, the details, the next step.
A practical checklist
Record the pause, the player’s words or actions, and what was visible before intervening.
Separate uncertainty about permitted actions, component meaning, and choosing among understood options.
Ask neutral questions about the player’s interpretation and expected consequences.
Test one suspected cause at a time with a temporary aid.
Keep observation and interpretation in separate fields; treat a single test as a clue, not proof.
A few more useful answers
What if the player says the rule is clear but still makes the wrong move?
Ask them to explain what they thought the rule allowed and what they expected the move to do. Their explanation may reveal a component misread, a different interpretation, or a choice they understood but found difficult.
Should I correct the player during the playtest?
If you want to observe unaided understanding, first note the pause and ask what they think is happening. Then clarify if needed so the session can continue, and record exactly what you explained.
How many times must a confusion happen before I revise something?
There is no universal count. Repeated similar observations can strengthen a suspicion, but a single pause may still expose an important ambiguity; use judgment and test a focused revision.
