How do I give players feedback that helps them choose their next move?
Quick answer
For each important action, record what the player did, what they can observe, what it might mean, what remains unknown, and what they can choose next. Keep observations separate from uncertain interpretations so feedback informs a decision without giving away its answer. Then ask players what changed, what they are unsure about, and which moves they might consider. Revise the row if the result is hard to notice or the intended uncertainty disappears.
The question, the details, the next step.
How can I tell whether feedback helps players choose a next move rather than just describing what happened?
Start with the decision a player faces after receiving the feedback. If it does not help them notice a relevant difference between possible moves, it may be a recap rather than decision support.
For each important action, note four things: the action, the observable result, what that result might suggest, and a choice the player can consider. For example, after gathering supplies, the player sees they gained two and that a nearby route still looks risky. They might gather more, take the route, or seek another path. The feedback shows what changed without declaring which move is best.
Ask: “Could a player name two plausible next moves and say what information supports each?” If not, clarify the relevant result or signal rather than deciding for them.
What should go in the planning grid? I want to separate useful clues from details that give too much away.
Use one row for each action or decision point where feedback matters. Include columns for player action, observable result, possible meaning, what remains unknown, and next decision. Add a final column for what information helps compare the options.
| Action | Observable result | Possible meaning | Still unknown | Next choices |
|---|---|---|---|---|
| Inspect muddy footprints | They stop beside the locked garden gate | Someone may have left the path there | Who made them, and whether they opened the gate | Search nearby, question a character, or check another route |
This is a hypothetical mystery-game example. The interpretation is a possibility, not a confirmed fact. If players are meant to work out what happened, keep that uncertainty visible rather than presenting an inference as certain.
How do I check the grid with players without just asking whether they like the feedback?
Ask them to use the information. After a play moment, ask: “What changed?”, “What are you still unsure about?”, and “What could you do next?” Then ask which details led them to those answers.
Notice whether they can point to a result, distinguish a clue from a certainty, and describe more than one reasonable move when the game intends a choice. If they miss a result, make it easier to notice. If they treat a tentative clue as definite, adjust its wording or presentation. If they can list options but cannot compare them, consider clarifying the relevant costs, risks, or benefits.
These answers show how that group interpreted that moment; they do not establish how every player will read it. Use confusion to identify a row to review, rather than immediately explaining the intended answer.
Can you give me a reusable template, including how to revise a row that is too vague or too revealing?
Copy this template for each important action:
- Action: What the player did
- Visible result: What they can directly observe
- Possible meaning: What the result may suggest
- Still unknown: What the game has not established
- Next choices: Two or more plausible options, if intended
- Decision support: What helps compare those options
- Playtest question: What you will ask the player to explain
For a worked revision, “The forest is dangerous” is vague because it gives no particular observation. You might instead show, “A broken branch lies across the narrow trail.” Players could investigate or choose another route; the cause of the break remains unknown. Adapt the details to your game’s rules and story.
If a row gives away too much, keep the observable result but remove or qualify the conclusion. If it gives too little, make the result more specific or show what changed. Then check that the intended decision still belongs to the player.
A practical checklist
Name the decision that follows each feedback moment.
Separate observable results from possible interpretations.
Record what remains uncertain.
List intended next choices and what helps compare them.
Ask players what changed, what remains unknown, and what they might do.
Revise unclear or over-revealing feedback and review the decision again.
A few more useful answers
Should feedback always offer more than one next move?
Only when the game intends to leave a choice. If an action is required, feedback can clarify what happened without pretending there are alternatives.
What if players keep choosing the same move?
Check whether other options are visible and comparable, and whether the situation gives players a reason to consider them. Repeated choices alone do not show what needs revision.
How can I keep a clue from sounding like a definite answer?
State the observable detail first, label an uncertain interpretation as a possibility, and note what remains unknown. Check whether players understand the distinction.