Playtesting: Self-Imposed Objectivity

I recently took some time to blind playtest the games of other designers and wanted to share my experiences. The short version is that I’m fantastically glad I did. I think everyone interested in gaming should do some playtesting (if for no reason other than an intellectual exploration and appreciation of the design process).

The slightly longer answer is that I think there’s a lot to be learned from stepping outside your own creative process to really evaluate the work of others. You get to objectively see what works, what doesn’t, what’s polished, and what’s confusing – all without the fog of design to obscure things. Here are some of my takeaways:

How I Anticipate my Playtests Will Impact my Game Development:
  • Spend ample time on the rulebooks, focusing on overview and simplicity
    • Start with an overly-verbose, excessively long, and tediously-thorough rulebook with plenty of explainer graphics, reminders, and overviews
    • Spend multiple edits paring down the text; increasing clarity and reducing walls of text
  • Play through the game alone several times with an emphasis on questioning everything
    • It’s impossible to be truly objective, but reading the rulebook verbatim and not skipping steps should help reduce some of the blind-playtest confusion
  • Really focus on the balance between ‘easy-to-learn’ and depth of replay
    • Easy-to-learn games are fantastic for adoption, but often fizzle out quickly
    • I want to try and inject complexity into my games through content and varying strategies rather than an increased number of mechanics and/or required steps. Tension via options per decision + concise # decisions >> # Options via multiple decisions and rules
How I Plan to Utilize Playtesters for My Future Games:
  • Make it clear
    • If it’s lengthy, or requires many components be supplied, make sure the playtesters know up front
    • Provide discrete questions to guide their review. “Did you like the game? What would you change?” is difficult to answer well.
  • Make it easy
    • PDF PNP files that don’t need explanation on printing, cutting, or assembly
  • Make it consistent
    • Web forms aren’t sexy, but they should be great for getting and tracking consistent data points
    • One person citing a problem isn’t as powerful as ten people citing the same problem
  • Provide an incentive
    • It doesn’t have to be grandiose – a simple mention as a playtester on the website or rulebook to give credit is far more than nothing
    • Can be substantial if it makes sense (e.g. lengthy game)
My Thoughts for Those Who Wish to Playtest:
  • Really consider why you want to playtest and what value you can provide to the designer
    • Even if you’re not a designer – think about how they might utilize your feedback
    • Being nice isn’t helpful if the game is garbage, but neither is slamming their game without explanation
    • Your observations are likely close to priceless, and your proposed solutions are likely close to worthless
    • Don’t worry about trying to solve their problems (that’s their job), but being thorough and precise is crucial; you try to imagine coming up with a solution for “the setup didn’t make sense”.
  • Get basic information about the game ahead of time
    • Things like number of players, expected time of play, required components, etc.
    • The goal is to ensure that you have an understanding of what you’re taking on so you can follow through
    • At least one of the games I playtested ended up requiring WAY more time than I expected, which resulted in some longer, more frustrating nights on my end (as I wanted to keep my word to the designer)
  • DON’T, however, be tempted to get too much information about the game if you’re blind playtesting
    • Every piece of gameplay information you have undermines your ability to objectively stumble through the rules
    • No playthrough videos, no overview of the setup…nothing
  • If you’re getting stuck, either because the rules or rulebook are broken or unclear, come up with something plausible and keep moving
    • Something might clarify itself later in the game
    • Even if the game is broken, you can still provide insight into the rest of the game (and problems), by moving past the sticking point
Happy playtesting!
Advertisements

Author: Adam Levitus

I'm the mastermind and wizard (Order of Merlin, First Class) behind A Bit of Levity. Apart from travelling down the road of board game design, I have also created a greeting card design company (Pithy Diction) and co-founded/exited another greeting card subscription company (Greetfully). I'm from Chicago but now live in California (if that matters) - NorCal specifically (which apparently matters a lot).

One thought on “Playtesting: Self-Imposed Objectivity”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s