How can I test whether one strategy is overshadowing the others?
Quick answer
During playtests, record the strategy each player chooses, the game conditions around that choice, which alternatives were realistically available, and what happened afterward. Compare choices across different starting positions and situations rather than treating frequent use alone as proof of imbalance. Ask players why they chose their approach, then check whether another strategy has a clear situation where its trade-offs make it attractive.
The question, the details, the next step.
I’m testing a game with several possible strategies. How do I tell whether one is actually overshadowing the others, rather than just being popular with the people at my table?
Look for a pattern across choices and circumstances, not just a high count. A strategy may be popular because it is easy to understand, suits a player’s style, or fits the particular game state. It is more concerning if players repeatedly choose it when other approaches are viable, it works well across varied situations, and the alternatives have no clear reason to be chosen.
For each decision, note what the player was trying to achieve, what conditions mattered, and which alternatives they considered. After the game, ask a neutral question such as, “What made that approach seem like the best option here?” Avoid leading with “Was that strategy too strong?” because that can steer the answer. Treat the log as evidence for a design question, not a verdict from one session.
What exactly should I record while people are playing? I don’t want a log so complicated that I stop watching the game.
Keep each entry short and tied to a decision point. Record the player using a simple placeholder, the round or situation, the approach chosen, and any visible alternatives that seemed feasible. Add a brief note about the relevant conditions: for example, available resources, position, opponent behavior, or the objective in play. Then record the immediate result and, if possible, the player’s reason afterward.
A compact entry could look like this:
Round 3 | Player B | Chose: gather resources | Situation: low supplies, nearby objective | Considered: direct contest | Result: gained supplies, objective lost | Reason: wanted options next round
That is a hypothetical example, not a finding about your game. The “considered” field matters: an option that was unavailable or obviously unsuitable does not tell you much about whether players had a meaningful choice. If you can’t observe a detail without interrupting play, leave it blank and ask afterward.
How do I make the comparison fair when starting positions or game situations differ? And what if a strategy wins more often in my small test?
Compare like with like where you can. Run sessions with different starting positions, player orders, or objectives, and note those conditions in the log. Look at whether a strategy is chosen and performs well in more than one kind of situation, and whether alternatives have situations where players deliberately prefer them. Don’t combine unlike situations into a single simple total and assume the number explains why.
A few wins in a small or uneven set of games are a reason to investigate, not proof that a strategy is too strong. Record the number and type of opportunities, not only final wins. Also note whether a player had more experience or whether a key event shaped the outcome. Those details help you decide what to test next without claiming they establish a cause.
Once I have the notes, how do I decide whether to change the game? Can you give me a reusable log and a sensible next step?
First summarize the pattern in plain language: which approach was chosen, under what conditions, what alternatives were available, and what reasons players gave. Then identify one specific design question to test, such as whether an alternative has a compelling use when a particular objective is active. Change one relevant element at a time if practical, and use another playtest to see whether choices and explanations shift. Keep the old version’s notes so you can compare; don’t treat a single changed result as conclusive.
Copy and adapt this entry template:
Session / rules version: [ ]
Round or decision point: [ ]
Player placeholder: [ ]
Situation and constraints: [ ]
Chosen strategy: [ ]
Feasible alternatives noticed: [ ]
Immediate result: [ ]
Player’s reason, asked afterward: [ ]
Follow-up question to test: [ ]
Keep observations separate from interpretations. “Three players chose approach A when the supply was low” is an observation; “A is always best” is an interpretation to test. If the evidence stays mixed, collect more targeted observations rather than forcing a yes-or-no conclusion.
A practical checklist
Log the game situation and relevant constraints at each strategy decision.
Record feasible alternatives, not just the approach selected.
Ask players neutrally why they chose that approach.
Compare choices across different starting positions, objectives, or conditions.
Separate observed patterns from explanations and test one design question at a time.
A few more useful answers
Should I count how often each strategy is chosen?
Yes, but interpret the count alongside the situations and alternatives available. A raw popularity total cannot show whether players had comparable opportunities or why they made their choices.
What if players choose one strategy but say they enjoy another more?
Record both the choice and the stated preference. Ask what made the preferred approach hard to choose in that situation; the difference can point to a design question, but it does not by itself prove a balance problem.
How many playtests are enough to decide?
There is no universal threshold in this log. Look for repeated patterns across relevant conditions, and use uncertain or contradictory results to plan a more focused test.