Learn from a playtest

Turn player behavior into a useful next experiment.

On this page

Use this when: You have something playable and a question about how people experience it.

You will leave with: Observations separated from interpretations, with a focused change to investigate.

Keep in mind: Observation shows what happened, but not always why. Ask about motivations and feelings as well. A small or friendly sample is useful, but does not establish how all players will respond.

Step 1

Choose people who fit the question

Describe the intended audience and what your sample misses. Informal tests can expose obvious problems; calibrate your conclusions to the evidence.

Read the full principle and its exceptions: Mind your sample and your biases →

Step 2

Let the game do the explaining

For an onboarding or clarity test, avoid coaching through the part you are observing. If progress requires help, record the intervention and distinguish it from unassisted success.

Read the full principle and its exceptions: Don't help, don't explain →

Step 3

Record behavior before your verdict

Note hesitation, attempts, confusion, and moments of understanding. Ask follow-up questions, then compare what was said with what you observed.

Read the full principle and its exceptions: Watch what players do, not just what they say →

An example

A player says the objective was clear, but spends the first minute trying unrelated doors. Record both facts. Ask what they thought they were trying to do; investigate the discrepancy before deciding that the answer is a bigger objective marker.

Illustrative scenario, not a report of a tested project.

Try this next

Choose one repeated or high-impact problem. Write a possible explanation and one change that could test it. Observe again before generalizing.

Explore the wider handbook →

This guide is an editorial companion to the linked principles. Their full conditions, disagreements, and source trails remain authoritative.