Today, I plan on doing something a little different. I talk a lot about making games. I talk a lot about games to look at to get ideas about making games. I talk about games that are not even video games to get ideas about making games. But, when you get enough of that project you are working on done to show off a demo, there is going to be that next step.
That step where you have to put yourself out there. Every person who creates puts themselves out there. That thing you made, is a piece of you. So you take that piece of you, you package it up with a nice topic on our forums, or maybe one of the many other excellent fan sites, or maybe you just send it to a friend. And you tie it off with a bow. And you just know that people are going to love it. Because you love it. How can it be bad?
And then the shoe drops. Someone has come up to you, and told you what you made is awful. Or maybe they just criticized a couple of details. But all the same, its a crash. We get it. It isn’t fun. No one likes hearing someone say something they made is flawed.
But what you do next is important.
Never, ever respond to criticism right after you read it. You could be a bit emotional at the time. Its understandable. Someone is criticizing your baby. And I’m sure you don’t need me to explain why responding emotionally is a bad idea.
But let’s say you aren’t. Let’s say that you actually are perfectly calm. Still don’t respond yet.
If you respond right after reading, 99 times out of 100, you haven’t actually thought about what the person told you.
Okay. You’ve taken a break. Had a Snicker’s (you’re not yourself when you’re hungry). And you’re back at the keyboard. Now, read what they wrote again. Try to identify what they saw as problem spots.
In well written criticism, it shouldn’t be too hard to find. They will tell you directly. Sometimes though, its not as obvious. Maybe they are really vague, or maybe they just are explaining themselves badly.
Either way, think about what in your game could make them come to the conclusions they did.
Ask them questions to get a better idea of the problem they had. Always lead off by thanking them for taking the time to check out your game. Even if they really were behaving badly, showing that you are mature in your response will help you get more detailed answers, as people will really want to help you out. Detailed answers about why people had problems with your game is crucial to perfecting your project.
Now that you have that detailed description of their issue, look at it in the context of your game. Try not to think of your game as your game, think of it as someone just coming in. Does what they are saying make sense?
If it does, you have some work to do. If it doesn’t, why doesn’t it make sense?
Did they misunderstand something? Then maybe you need to work on having your game communicate that better.
Are they not part of the target audience? What attracted them to your game in the first place, and could your target audience be adjusted to include people with his tastes, too?
Now is when you can take the time to respond. Once again, start by thanking them for their time. You put that demo out to get feedback, and they came to help you out. More than likely, they really wanted to help. Or maybe they just are a jerk who likes to get people down, but I like to assume the best until they prove they are worse, and it never hurts to show you aren’t going to sling mud.
After that, it depends on what you think you should do with their advice. If you think they have a point, tell them so. You can tell them how you hadn’t thought of that, and man, its a good thing they came along to help you out. Tell them some plans you have for fixing it, see if they have any suggestions.
If you think that their criticism isn’t applicable, you can tell them so. You can even point out the reasons you feel that it isn’t relevant. But don’t try to make it a rebuttal. You don’t have to justify your decisions. You can explain that you appreciate their advice, but you feel your original design for that portion of your game best serves your intended purpose.
You aren’t bound to follow every bit of criticism you get, and no one reasonable is going to judge you for politely saying you feel confident in your current design. (Though if you find a large majority giving you the same criticism, you should probably take heed).
Of course, there is always the criticism you can feel safe ignoring. If it is laced with so many profanities it could OD a sailor, and says nothing meaningful and personally insults your mother, your third cousin, and your childhood dog, just roll your eyes and move on, don’t even bother responding (and hit the report button if its on our forums!(extra points if you include the eye rolling emoticon on the report)).
So, do you have any advice on taking criticism? Any fun stories of criticism that really helped you? Or maybe an embarrassing story about you having a bad reaction to criticism. Make sure to join us in the comments section below!