What are the qualities of a successful beta testing session from the player's perspective?

Question

I'm a board game designer with the luxury of a large public playing area filled with board game enthusiasts. I would like to beta test a new board game and was wondering what YOU, as the player, would consider a successful session.

I've already seen the posts on how to run a session from a technical, or designer's perspective (I have an idea for a card game. How can I best start testing it?). I would like to focus on what makes for a fun session for the player. For example, are you looking for polished, illustrated gaming pieces? Pizza and soda? Do you prefer the game guru (me) answer questions as you go or sit back and let you figure them out on your own? How long should a typical session last? What would you want in return?

When you answer, please mention if you've done beta playtesting before and what your experience has been. I would also love to know if you have experience running these kinds of sessions. Thank you!

Answer 1

Designer and sometimes attendee at design group BOGA DAP here. I'll share my personal experiences and preferences.

As a tester, to feel good about the event:

• In general, I prefer the game to be taught as if you were teaching an already-published game. If you are getting a blind playtest, or testing the ability of players to learn from a rulebook, then I expect the game to be 99% done and the instructions to be as clear as you can make them.
• If you have specific questions about the game you want answered, in terms of balance or how a mechanism works or how it feels or whatever, let me know. In a playtest game, I am not averse to you changing the rules mid-game if you want to try something out or the rules aren't working.
• I have no expectations at all in terms of graphic polish or illustration. An unpolished prototype is a sign that you are not emotionally invested in the game as it is and are open to feedback and changes. Even going so far as a deliberately sketched-in look-and-feel can be helpful.
• I expect you to respect my time. I play games for fun all the time, so if the game is fun or at least interesting, I don't need a food bribe. I do want you to be willing to playtest my games as well, and I want you to make appropriate changes or pull the plug if it ends up not working or not being fun.
• 1-2 hours, with time on the end to ask for feedback, makes a good playtesting session for most games. An early playtest (where we expect to pull the plug quickly and go back and make changes) might end up being shorter, or a test for a very short game. I don't expect to play a medium-or-longer game more than once in a sitting. Unless the game was a smash hit, I expect you to take it back for at least a few changes before we play again.

As a designer, to get the most out of a playtest:

• Try to observe the game, rather than playing it yourself, unless you are needed to fill up the player count. This lets you pay more attention to both the game and the players and how they're acting and feeling.
• Tell the players what you changed since the last iteration of the prototype. If it's not obvious whether it worked or not, ask the players.
• After the game, ask each player what they liked and didn't like. This is tricky. On one hand, never defend your game. If a player gives a criticism that you feel is invalid, ask yourself what you might be able to change to mitigate the perception of the problem - whether in the rules or the explanation. On the other hand, you will need to pass by many suggestions, since they will not lead your game in the direction you want it to go in. Not every game is meant for every player. Criticism might just be telling you who the best audience for your game is.

Answer 2

I've playtested games for a couple of friends (one at various early iterations, one in a near-finished state). What I'm looking for:

• Complete rules (even if they may go through more iterations). It's frustrating to have a rules question that is not answered by the booklet because it is intentionally incomplete. On the other hand, unintentional oversights are fine (that's why we play test!).
• Detail and finish on the play elements are unnecessary; I've used Lego blocks and random coins as tokens during play tests.
• No hovering by the designer. As sitnaltax mentioned, it's probably best if the designer doesn't play. The designer should be available for questions, and observing is fine, but looking over players' shoulders at their cards, etc, is to be avoided.
• For long games (e.g. targeting 90-120 or 150+ plays), a single playthrough is likely best. I'm happy to spend a few afternoons on various iterations, but playing for 4 hours in one sitting can be rough. You might even consider pulling out specific subgames if you're looking to balance rules so that you can have multiple playthroughs of the endgame, for example.
• Compensation: Pizza and soda, snacks, etc are probably fine. Playtesters should probably get a mention in the final rulebook (there's often an acknowledgements section); it's best if it can be by name but it could be something like "and the Boston gamer's group who helped test early versions of this game."

Answer 3

I agree mostly with sitnaltax and ruds, and would like to add some more points:

The game must be playable and fun to play.

I like it when I can provide some useful feedback. I don't want to play a half done game, but I am happy to help polishing details.

Answer 4

I agree to what was said before. When I designed my board game, I tested it with many "non-gamers" (because I lacked the luxury you were writing about) - but that resulted in some extra insights about what is important:

• Make it clear to yourself and to the group at what stage the game is and what the purpose of todays test is. What kind of suggestions do you need, what do you want to test in this round, what questions to ask -> If I test a game, I want to know what I am doing. Many people are also excited to be part of the whole process, so they enjoy stories about "behind the scenes details" and regular updates.

• The biggest barrier for playtesting I encountered was that players were afraid it would take much longer than a "normal" game, especially when they had to learn the rules themselves (in retrospective, I should have stopped more games halfway or changes rules in the middle) -> Make realistic accouncements about the time you will need before the game starts.

• The most uncomfortable part was when I asked people who played before to explain the rules to new players (I wanted to see what they forget/explain wrong). While it worked perfectly on a "methodological" level, they seemed to feel pressued -> Players might want to avoid judgement by the author/feel observed.

• Almost every single player appreciated and used the opportunity of asking the author sitting next to them when they were not sure about rules (instead of debating or looking them up)