So, we’re sending out “Austen Translation” for initial play testing. This is a time of both delight and horror. It’s delightful in that people are actually *playing* our game, which is great! And they’re sending back suggestions and commenting and giving us fresh insight into gameplay, pacing, and tone, and that’s all amazing! But it’s also a little horrifying because we *know* there are things that aren’t working and we know that there are big fixes still to be made, but you can’t wait till you think it’s perfect before you send a game out for play testing. It would never leave the nest. So it’s time to push our squawking, squealing little fledgeling out of the nest. Yes, right now.
We like to embrace a hands-off approach to play testing. New players are generally given only a short soundbite about the goals of the game and set free to muddle their way through a round. There is no tutorial. It can be very informative to watch a fresh player figure out how your game works through trial and error. When they grok things right off, you know you’re in the ballpark. When multiple players make the same mistakes or experience the same frustrations, it can be a sign that what you thought was intuitive or obvious really isn’t. After play, there’s generally an informal discussion to capture impressions and suggestions.
In addition to our usual cadre of industry folks and insiders — who are great for technical and higher-level commentary and understand the process well — we invited a few more “civilians” into the play testing mix this round. We were particularly interested in getting the game into the hands of female players, players slightly older than the predictable demographic, and folks with a literary background. The game was also made available at the recent Playcrafting Spring Play Game Expo event here in Boston, which brought a wide range of players and sparked a lot of lively discussion. We want to thank the Playcrafting folks for the opportunity to get “Austen” out in front of their audience.
One of the hardest parts of play testing effectively is interpreting the feedback you receive. Often feedback is couched in terms of specific recommendation (“A should be B”) which you may or may not agree with at this very moment. It can be helpful to avoid a binary “we’re going to accept or deny this recommendation” and look beyond the suggestion to the issue which sparked the suggestion in the first place. Specific play tester requests can be symptoms of deeper issues which could be better addressed by fixing the underlying problem instead.
There’s also a constant natural tension between wanting to hear and respond to your testers, and the necessity of maintaining the integrity of your original vision for the game. Group processes tend to be biased toward knocking the quirky sharp edges off products, but sometimes — just sometimes — those edges are precisely what make a game experience unique and memorable.