Different ways to play
Each tested approach has clear action choices and scoring aims. Opponents use different preferences and levels of planning where the question calls for them.
METHOD
How we test.
A reliable rules model, purposeful comparisons, and findings you can use in development.
Begin with the rules.
We organize the rulebook, components, official clarifications, and version notes. The agreed rules are implemented as an executable model. Legal actions, resource changes, scoring, special situations, and game endings are checked before large-scale testing.
Compare the conditions that matter.
Players, seats & deals
Change player counts, rotate seats, and use another batch of starting conditions. Check where a finding holds and where it changes.
Original & revised versions
Compare the same starting conditions with the same seats and approaches. This makes the effect of a rule change easier to separate from ordinary variation.
Results & examples
Review scoring, trajectories, and exceptional outcomes. Use comparison tables and examples to explain differences and their causes.
Six aspects of mechanism quality.
GQS is our Game Mechanism Quality Score. It organizes the assessment into six equally weighted aspects, each scored out of 10. Findings and recommendations explain the scores.
Rules reliability
Can actions, scoring, and game endings be carried out consistently?
Fairness & balance
Do seats, starting conditions, roles, or individual cards create uneven advantages?
Meaningful decisions
Do choices change the result, and does the best choice depend on the situation?
Strategy diversity
Are several approaches competitive, each with useful conditions?
Strategic depth
Does planning help, and can players respond to strong opposing strategies?
Game progression
Does the game keep moving, with useful actions and a clear ending?
Each aspect uses the same six score levels: 0, 2, 4, 6, 8, and 10. The total is the average when all six can be assessed. A focused project can answer a question without requiring a complete score.
What the report explains.
The result
Show which approaches worked, how large the differences were, and the conditions behind them.
The cause
Connect an observed problem to card choices, scoring rules, resource competition, or the progression of play.
The next action
Recommend a specific change or a reason to retain the current design. Where a proposal needs another comparison, state that next test.
Alongside player playtests.
Automated testing examines rules, balance, strategies, and progression. Player sessions explore enjoyment, learning, social interaction, and the physical game. We identify concrete questions you can bring to those sessions.
WORK WITH ZONE IN
Tell us what you want to test.
Your game’s stage, player count, and main question are enough to start a conversation.