BC-0258 · TROUBLESHOOTING
Editorial review 2026-09-27
Players Leave Immediately in Playtest
An early test exit is an observation, not a confirmed reason for leaving. Locate the last stage reached—entry, orientation, action or first outcome—and distinguish a technical interruption from a voluntary exit or unknown cause. Do not turn a small informal session into a retention statistic.
Symptom
A participant leaves or becomes unavailable early in an informal test session.
Immediate action
Record the last known stage and distinguish observed exit, technical interruption and missing information.
Diagnostic branches
- The game was never entered.
- Use access or launch diagnosis and do not infer a gameplay judgment.
- A reproducible obstacle precedes the exit.
- Investigate that obstacle without claiming it explains every participant's departure.
- The reason is unknown or personal.
- Retain that limitation and avoid speculative content changes or intrusive questioning.
Least-destructive change
Preserve the session evidence rather than redesigning the opening around an invented motive.
Retest
- No informal count is presented as an analytics retention metric.
- The player had an actual opportunity to reach the task being evaluated.
- Later comparisons preserve version and familiarity context.
Escalation
Use a focused future observation when appropriate. Without usable evidence, the conclusion remains unresolved rather than a claim that a specific feature drives drop-off.
Working notes
Start with the observation's completeness. Did the person say they stopped, did the application close, or did communication simply end? Missing follow-up is not proof of dissatisfaction. Record the last visible action and any explanation the participant voluntarily provides without claiming to know their motivation.
Map the exit to the opportunity actually offered. Someone who never reaches a playable screen did not evaluate the game's opening loop. Someone who sees the goal but cannot use a control faced an interaction obstacle. Someone who completes the first task and chooses to stop may have reached a satisfactory endpoint rather than failed onboarding.
If a safe follow-up is possible, ask what they were trying to do and what happened just before stopping. Avoid questions that supply a preferred explanation such as 'Was the tutorial too long?' Keep personal interruptions separate from game observations and do not pressure participants to justify leaving.
Choose a revision only when evidence identifies a game boundary. A broken control can be repaired; an unknown exit remains unknown. When comparing later sessions, retain version, familiarity and observation limits so different conditions are not presented as a measured improvement.
Examples
- Unknown exit: the participant stops responding before describing a game frame. Mark the reason unknown rather than counting it as boredom.
- Completed opening: the participant delivers the parcel and leaves after the result panel. Investigate whether the game communicates a worthwhile next task only if continued play is part of the intended design.