--- key: lesson/running-a-playtest type: lesson id: running-a-playtest lang: en title: Running a playtest with a concrete question summary: >- Prepare a short play session, separate observations from interpretations and choose the next change. updatedAt: '2026-10-20' status: active url: 'https://gamemechanics.pro/en/lessons/running-a-playtest/' jsonUrl: 'https://gamemechanics.pro/api/v1/knowledge/en/lesson/running-a-playtest.json' markdownUrl: 'https://gamemechanics.pro/content/knowledge/en/lesson/running-a-playtest.md' aliases: [] tags: - playtesting - observation - iteration sourceIds: - source-9c87522b3f95004d sources: - id: source-9c87522b3f95004d title: 'The Level Design Book: Playtesting' url: 'https://book.leveldesignbook.com/process/blockout/playtesting' verifiedAt: null relations: - type: requires direction: outgoing label: Before you start key: lesson/scope-and-prototype title: Scope and a testable prototype url: 'https://gamemechanics.pro/en/lessons/scope-and-prototype/' jsonUrl: >- https://gamemechanics.pro/api/v1/knowledge/en/lesson/scope-and-prototype.json markdownUrl: >- https://gamemechanics.pro/content/knowledge/en/lesson/scope-and-prototype.md - type: reviews direction: outgoing label: Review through a lens key: lens/schell-103 title: Playtesting url: 'https://gamemechanics.pro/en/knowledge/lens/schell-103/' jsonUrl: 'https://gamemechanics.pro/api/v1/knowledge/en/lens/schell-103.json' markdownUrl: 'https://gamemechanics.pro/content/knowledge/en/lens/schell-103.md' - type: practices direction: outgoing label: Put it into practice key: practice/three-minute-museum title: Three minutes at the museum url: 'https://gamemechanics.pro/en/knowledge/practice/three-minute-museum/' jsonUrl: >- https://gamemechanics.pro/api/v1/knowledge/en/practice/three-minute-museum.json markdownUrl: >- https://gamemechanics.pro/content/knowledge/en/practice/three-minute-museum.md - type: contains direction: incoming label: Learning paths key: path/game-verification title: Game verification url: 'https://gamemechanics.pro/en/learn/game-verification/' jsonUrl: 'https://gamemechanics.pro/api/v1/knowledge/en/path/game-verification.json' markdownUrl: 'https://gamemechanics.pro/content/knowledge/en/path/game-verification.md' placements: [] supersededBy: [] attributes: category: workflow level: beginner minutes: 5 endsAt: null provenance: >- Original gamemechanics.pro material. Check illustrative examples in your own project. license: CC-BY-4.0 codeLicense: MIT attribution: gamemechanics.pro contributors --- # Running a playtest with a concrete question id: running-a-playtest type: lesson key: lesson/running-a-playtest lang: en status: active url: https://gamemechanics.pro/en/lessons/running-a-playtest/ Prepare a short play session, separate observations from interpretations and choose the next change. ## Prerequisites “How did you like the game?” often produces a polite answer that is hard to act on. It is more useful to choose an uncertainty beforehand and observe what someone does in a specific play situation. ## The principle Form a question, prepare a suitable game segment and observe. [The Level Design Book](https://book.leveldesignbook.com/process/blockout/playtesting) distinguishes self-playtests, critique with a colleague and observing an outside player. They serve different purposes. Testing a first encounter requires someone who does not already know the solution. The same person's repeat attempt can check usability, but no longer reproduces first discovery. A few observations can reveal problems; they do not establish the preferences of an entire audience. ## Practical example ### A station delivery The teaching question is: “Can a new player deliver a battery to the antenna without spoken explanation?” Prepare one level version, the same starting state and a consistent objective. Invite the person to play and explain that the game is being tested, not their abilities. Obtain consent before recording screen or voice. During play, separate your notes: | Observation | Possible explanation | Next check | | ---------------------------------------- | --------------------------------- | --------------------------------- | | Approached a locked hatch three times | Hatch suggests an available route | Change its signage | | Returned to the start after climbing | Lost direction toward the goal | Check antenna visibility upstairs | | Asked whether the battery can be dropped | Allowed actions are unclear | Check the carrying hint | These are example notes, not completed research. Do not supply the solution merely to get a successful run sooner. If a blocking bug requires intervention, record when and how you helped. Afterward, ask which goal the player pursued at an ambiguous moment. Their answer helps refine an interpretation without erasing the observation. Choose one change connected to the question and test again. ## Common mistakes - Changing the build midway through a series and treating conditions as equivalent. - Recording “confused” without location, action or context. - Changing camera, route and controls simultaneously and losing the cause of an effect. ## Verify it - The report includes a question, build version, starting conditions and the participant's prior familiarity. - Facts are separate from assumptions and author decisions. - Assistance and blocking bugs are recorded separately. - The next change connects to at least one observation. ## Prompt for an AI agent > Prepare a five-minute station playtest: one question, a neutral task, an observation table and follow-up questions. Do not invent participants or results. After receiving real notes, propose one next experiment. Use the [Playtesting lens](/en/lenses/#schell-103) and [Three-Minute Museum](/en/practice/#three-minute-museum). ## Connected materials - Before you start: [Scope and a testable prototype](https://gamemechanics.pro/en/lessons/scope-and-prototype/) (key: lesson/scope-and-prototype) - Review through a lens: [Playtesting](https://gamemechanics.pro/en/knowledge/lens/schell-103/) (key: lens/schell-103) - Put it into practice: [Three minutes at the museum](https://gamemechanics.pro/en/knowledge/practice/three-minute-museum/) (key: practice/three-minute-museum) - Learning paths: [Game verification](https://gamemechanics.pro/en/learn/game-verification/) (key: path/game-verification) ## Sources and provenance Original gamemechanics.pro material. Check illustrative examples in your own project. - [The Level Design Book: Playtesting](https://book.leveldesignbook.com/process/blockout/playtesting) (id: source-9c87522b3f95004d) CC-BY-4.0 · gamemechanics.pro contributors