Description
Many players play a build at the same time and then answer a structured questionnaire, so the team gets quantified attitudes about whether the designed experience is enjoyed.
A large-scale playtest answers the question 'are players enjoying the experience we designed?' rather than 'can they use it?'. Groups of target players play a near-complete build in a room with several seats, then complete a carefully designed questionnaire about appeal, enjoyment, difficulty, art style, features and core mechanics; a few may join a short group interview. Player Research describe a minimum of 36 players run as three groups of 12 in one day, with about an hour of play and 25 minutes of questions, followed by several days of analysis. Medlock's overview names variants by scope: the initial experience playtest covers roughly the first two hours of play, the extended playtest runs over days (for example two days and 16 hours) to show how ratings change across levels, and the benchmark playtest uses a standardised questionnaire and larger sample so that results can be compared with other titles tested in exactly the same way. Because attitudes only mean something against a reference, the method depends on consistent questions and enough participants for statistical comparison. It complements small-sample usability playtests, which find problems but cannot quantify liking. For UX teams outside games, the same pattern suits any experiential product where enjoyment, not task success, is the main outcome.
Attributes
- Discipline
- Usability & Evaluation
- Loss type
- Siloed
- Stage
- Design, Evaluation
- Data
- Quantitative
- Effort
- Days
Steps
- Agree the questions the team needs answered and which of them must be quantified.
- Write or reuse a standardised questionnaire with rating items per game area plus a small number of open questions.
- Recruit a target-audience sample large enough for comparison (the book suggests at least 25 to 36 players).
- Run groups of players simultaneously on the same build, with a fixed play period and minimal moderator intervention.
- Administer the questionnaire straight after play and, optionally, hold a short group interview.
- Analyse ratings by game area and segment, code open responses, and compare against earlier builds or benchmark titles.
- Report results structured by the team's questions and track them across builds.
Sources
- Drachen, A., Mirza-Babaei, P. & Nacke, L. (eds), Games User Research (2018)
Also known as
- Benchmark playtest
- Initial experience playtest
- Extended playtest
- UX playtest
- Group questionnaire playtest
Categories
- User Research
- Usability & Evaluation