The short answer
You cannot judge whether your own game is understandable. Watching five people play for two minutes each, without saying anything, finds more than any amount of internal review.
The first thirty seconds is where most players are lost.
Run it properly
- Give them the link and say nothing else.
- Do not explain, however uncomfortable it becomes.
- Note every hesitation and every wrong assumption.
- Note when they stop, and ask why afterwards.
- Fix the most common problem before testing again.
Point two is the hard part and the entire value. The moment you explain, you have removed the thing you were trying to measure.
What to look for
| Observation | Means |
|---|---|
| Hesitating at the start | The objective is unclear |
| Trying the wrong control | The interaction is not obvious |
| Not noticing feedback | Signals are too subtle |
| Stopping mid-session | Boredom or frustration, ask which |
| Finishing without replaying | No reason to continue |
The distinction in the fourth row matters. Frustration is a design fault; boredom means the mechanic is not carrying the length.
Test on their devices
- Their own phone, not a test device
- On mobile data, not office broadband
- In whatever browser they normally use
- Without any special setup
- In a normal environment, sound off
Testing on a prepared device in ideal conditions misses most of what real players encounter in the first ten seconds.
Fix the opening first
Improvements to later content reach fewer people than improvements to the opening, because most players never get there.
Make the objective obvious within seconds, make the first interaction unmistakable, and give immediate feedback for it.