Skip to main content
Loading video...

Why Listening to Every Playtester Will Ruin Your Game | Design Pillars

Transcript 13:50

You wrap up your game at a local play testing group and invite the players to give you some feedback. One player tells you the game was too long. Another says it ended too quickly. One player tells you the game was too complex. Another says the game was super easy to learn. One player loved all the dice rolling. Another says to cut out all the randomness. One wanted more player interaction. Another wanted less. You dutifully note down all the testers observations and thank them for their help. But you have absolutely no idea what to do next. Does this sound familiar? Players are full of suggestions, but they rarely agree. So, who should you listen to? And who should you ignore?

I'm Adam Porter. I've been creating games my whole life and over the last decade I've seen multiple of my designs distributed all over the world. I've faced the scenario that I just described countless times and I want to provide you with a tool to help you to negotiate those contradictory messages, to find your own way through the confusing fog of play tester feedback. New designers often try to design by committee. If two testers suggest adding trading, then trading gets added. If three testers suggest removing combat, then combat gets removed. All good ideas, but the game is being pulled in too many different directions at once. The truth is, this isn't a problem with your testers. The real issue is that you haven't decided what game you're actually trying to make. Design pillars exist so you can reject good ideas.

Design pillars are the foundation of your design. The non-negotiable features which direct your process. If you find your design wandering off course, you can return to these pillars to see if you can bring the game back onto the right track. I see huge value in defining design pillars early in the game design process. They should follow a period of sustained reflection. Who am I designing this game for? How best can I serve them? Once you've determined that you have a strong concept with a viable audience, and importantly, a concept that you will enjoy developing, it's time to nail down the basics, to set them in stone. I would suggest writing three to five statements which describe the absolute fundamentals of your game, the non-negotiable aspects which make the concept special.

So, a design pillar might refer to component type, duration, age range, a key mechanism, an environment, character, or story element, retail cost, or many other elements. Your design pillars are there to serve your intended audience, to ensure that the game is relevant to them, your desired publisher, to make it fit their catalog, and you, to keep you motivated. They act as a filter. So, without pillars, every piece of feedback can feel equally important, and that can be counterproductive and overwhelming. So, here's an example from my game Complot, released as Ballot Battle in the US, and co-designed by Rob Fisher. We knew early in the process that we wanted to create a card game for two players only. So, that's two pillars, one relating to player count, and one relating to components. It's interesting looking back on those pillars now. I do recall several times during the process of making this game that we were pushed towards expanding the player count by playtesters and some potential publishers, but we resisted. The two-player duel aspect was core to the experience that we wanted to create. The final two pillars for Complot were more mechanical. So, our basic concept was to create a lane battler in the vein of Schotten Totten or Lost Cities, but with a Blackjack mechanism at its core. If any of those pillars had been altered during development, we would have been

creating a fundamentally different game. So, let's take a look at a more recent release, Flip Pic Towers, again co-designed by myself and Rob Fisher. We set out to create a flip-and-write game. So, that's a mechanism-based pillar. We would not have been content to switch to dice, for example. The use of cards as a randomizer was central to our concept. And we also wanted the game to become more beautiful as you played it. Rather than simply filling in the score sheet, players would gradually create an illustration. So, that became another pillar. And finally, this was very much a COVID-era design, and we wanted it to work over Zoom and Teams. And that meant supporting any number of players. No upper limit on player count became another pillar.

During playtesting, several people suggested increasing player interaction. Under different circumstances, that might have been a great idea, but greater interaction would have made the game harder to play remotely, and harder to scale to large groups. So, we resisted. Flip-and-write, player as illustrator, unlimited players. Those were the pillars. And whenever feedback threatened any one of them, we knew it was time to stand firm. Note that a pillar is quite different to a hook. A hook is a short statement about your game that highlights its standout features, the elements that make publishers, retailers, customers, and players stop and pay attention. The hook is the single most important factor in attracting a publisher, and it also strongly influences whether retailers choose to stock a game, and whether customers choose to buy it. But your hook is not the same thing as your design pillars, even though the two may overlap. Design pillars are not intended to attract attention. They're the structural foundations that hold a project together. The hook, by contrast, is not concerned with the invisible systems and processes supporting your game. It's all about audience perception. Unlike your design pillars, your hook might change several times during the playtesting process. You can refine it as you learn what players enjoy most about your game. There's just one rule here, though. If you do change your hook, it must always be to make the game stronger, to make the hook more appealing in the eyes of publishers and

players. With pillars in place and a potential hook in mind, you've built a really solid foundation to do some intensive playtesting, and you should be much more resilient to contradictory suggestions from testers. I wrote an entire book about this part of the process. Adam in Wales Playtesting is available on Amazon worldwide, but I've developed a new tool, which I want to discuss here. During the early stages of playtesting, you're looking for opportunities. You cannot implement every suggestion presented to you by testers, or you'll soon find yourself lost in the process, jumping from one idea to another. The HUM model will help you to identify which opportunities to pursue and which to ignore.

And it works like this. So, when presented with a new opportunity for your game, score it 0 to 3 in each of the following three categories, resulting in a total HUM score between 0 and 9. So, H is for hook. Ask yourself, will this opportunity that's being presented to me by my testers bring me closer to the hook of the game? A 0 means no, absolutely not. A 3 means yes, definitely. U is for user experience. Is the opportunity likely to improve the player experience? Again, give the suggestion a score between 0 and 3. 3 means yes, this will make the player experience better. And E is is for effort. Is the opportunity easy to implement?

Zero is no, three is yes. It's very easy. So, imagine a tester suggests adding player elimination.

Does it strengthen your hook? Does it improve the user experience? And is it easy to implement? When using HUE, rather than accepting or rejecting ideas on instinct, you're evaluating them against the goals of the project. So, I would encourage you to record every suggestion made by your playtesters, maybe in a little notebook. Score them then using the HUE model. Opportunities which have a high HUE score are worth pursuing, and those with a low HUE score worth noting down, but they're unlikely to be beneficial for this particular project. Note that you should very rarely implement a playtester's suggestion if it means changing one of your game design pillars. To do so would essentially mean morphing your project into an entirely different game.

Later in the playtesting process, you're going to start to look at your game from a different angle. Instead of looking for opportunities, you might consider problems, which you might look to address in your design. A problem might become apparent because of verbal feedback given by a player, because of behaviors that you witnessed at the table, or through your own analysis of player scores and strategies. Now, just as you did when considering opportunities to pursue, you can also use the HUE model to determine which potential problems are worth fixing. And this time, the questions are just very slightly modified. H for hook becomes is this problem detrimental to the hook of my game? U for user experience becomes is the problem likely to negatively impact on the player's experience? And E for effort becomes is the problem easy to fix? Score each of those categories from zero to three and then use the total to help you to determine whether it's worth investing time in searching for a solution. Problems with a high HUE score are worth prioritizing, but those with a low HUE score, they're still worth fixing, but this is not always possible.

Sometimes we have to make compromises with our designs to accept weaker elements if removing them would be detrimental to the experience as a whole. So, let's take a hypothetical example. Imagine you're creating an abstract strategy game. The challenge you've set yourself is to create a game which doesn't require a board. You've particularly enjoyed playing Hive and Okay Play, and you want to create your own game within this subgenre of abstract games. A player suggests that it would be easier to strategize if the game was played on a fixed grid. This would warrant a board. You score the suggestion using H. Does it bring you closer to your hook? Well, no. Your selling point is no board, so the suggestion scores zero.

Would it improve user experience? Well, it might, but you only have one playtester's opinion on that. Others have been quite happy with the game the way it is. So, you score it a two for user experience. E is for effort. How easy would it be to prototype and experiment with using a fixed grid? Well, pretty simple, really. It's a single component and it requires minimal artistic skill to put it together. So, you score it a three for effort. The overall score is five out of nine, middle of the road. It might be worth experimenting with the suggestion, and ultimately you don't have to adopt it if you don't enjoy it. But for me, the deciding factor would be whether your no board stance is a pillar. If it's just a nice feature, but you're not committed to it, then you can discard it so long as you can find another suitable selling point. If it's a pillar, I would stand firm. You set out to create a game with no board, so adding one would make it a different game.

Playtesters have two important roles: identifying the most enjoyable aspects of your game, and identifying problems. They're often very keen to offer solutions as well, but really that sits outside of their role, and you're under no obligation to implement those suggestions. Five different players might tell you that your game feels too slow. Now, that's a pretty strong indication that you've got a bit of a pacing issue. Those same five players, though, might offer five completely different solutions. One wants fewer turns, another wants simultaneous play, a third wants fewer decisions, a fourth wants more powerful actions, a fifth wants the game shortened by 20 minutes. But, they can't all be right. So, this is where you need to return to your hook and your design pillars. The playtesters have helped you to identify the problem, and your job as a designer is to determine the solution. Only you have the full context needed to decide what changes strengthen your game and which transform it into a different game.

So, here's my closing piece of advice. Next time you run a playtest, don't leave with a page full of random notes. Leave with two lists: opportunities and problems. And then, score them using HUE. Not every suggestion deserves your attention, and not every problem deserves a solution. Before you implement anything, ask: Does this align with my design pillars? Does it strengthen my hook? And is it genuinely improving the experience, or am I simply reacting to the last person I spoke to? You've got one job: build the best version of the game that you set out to make. So, if you enjoy this kind of product-focused approach to game design, you'll probably also enjoy my books. The Adam Wells board game design series is available all over the world on Amazon, and it covers topics ranging from play testing and pitching to product design and personal development as a designer. I'll put some links in the description to the video below.

I look forward to bringing you more game design content in future videos, and until then, all the best.

Progress saved