Gamasutra: The Art & Business of Making Gamesspacer
View All     RSS
October 30, 2014
arrowPress Releases
October 30, 2014
PR Newswire
View All
View All     Submit Event

If you enjoy reading this site, you might also want to check out these UBM Tech sites:

The Quest for Honest Feedback
by Ryan Creighton on 11/04/13 10:54:00 am   Expert Blogs   Featured Blogs

The following blog post, unless otherwise noted, was written by a member of Gamasutra’s community.
The thoughts and opinions expressed are those of the writer and not Gamasutra or its parent company.


[This article by Ryan Henson Creighton is re-posted from the Untold Entertainment blog, which is awesome.]

Over the past few days, i've had a few colleagues run me through quick play-throughs of their mobile games. Maybe you've been there? A fresh-faced developer looks at you with his big doe-eyes, inclines his head, and asks plaintively "can i show you my game?"

Oh ... crap.

Your butt muscles clench. What can you say? "No?" It's not usually practical to make an excuse and bolt for the door. Face it: you're going to have to play his game. And you hope to God it's good.

It's Not Good

When the game isn't good, you say it's good anyway. Why? Because you just can't possible look into those dewy Disney bunny eyes and crush this poor developer's dream. He's worked hard on this game, you can tell. Probably spent a lot of time - and perhaps a lot of money - on it. And anyway, games are so subjective, right? Someone's bound to like it. So you look at him and say, somewhat non-committally, "yeah. Yeah. It's ... it's good." And perhaps, while in the depths of your treachery, you may even add "i like it." You think you are doing this because you are a good person, and because the developers' feelings matter more than honest feedback. In reality, you are doing this because you are a dirtbag.

Truth Is Love

There is nothing more poisonous to a developer than falsely positive feedback. If you're developing a terrible (or lacklustre, or uninteresting) game, but your passion has blinded you to its shortcomings, the encouragement you field from players and colleagues will only hurt your cause. It's like asking people "hey! What do you think of my shark-feeding skills?" and the people all say "yeah. Yeah. It's ... it's good. i think you should stick your arm even further into that shark's mouth. You're not quite there yet. Keep going."

We're gonna need a bigger game.

The result is that the developer keeps feeding the dangerous shark until he gets his arm bitten off at the shoulder, he wanders away from the shark in disinterest, or he grows old with the shark and eventually dies, never having ventured to feed another, perhaps nicer animal. (And at this, my metaphor crumbles spectacularly.)

The Snowflake Factor

When a game has obvious flaws, why are we so reticent to give constructive criticism? It's because we're all rare and precious individualist snowflakes, and the emotional pain of failure (and the ego-bruising that it entails) is the worst affront we can possibly suffer. We would never want to inflict that pain on other people - the stinging truth that our creation is mediocre and uninteresting, or just not very special.


Because we're all so thin-skinned ... because spirited debate is now viewed as distasteful, and criticism is now chalked up to "one's own opinion" and easily disregarded ... we need to get craftier about the way we solicit feedback from people. Here's what i've recently suggested to the colleagues who asked me to play their games (i haven't tested this myself, but i'm very interested to know if it works):

Do not present the game as your game. Present it as your friend's game. Say "my buddy's making this game, and he asked me what i thought of it. i know him too well to give him good, impersonal feedback. Could you take a look?"

The potential problem is that for some people, the Snowflake Factor may even extend to arm's length. You may not get honest feedback on your game, because the player doesn't want to hurt your imaginary developer friend's feelings. FFS. That's okay: i got this.

Present your game like this: "Hey. My friend is making this game, and he wants me to invest in it. He says i'll get a cut of the game's profits when it's released if i give him some money to finish it. Can you play the game and tell me what you think?"

You'll never change into a real developer at this rate.

The Snowflake Factor is now working in your favour. The player's need to protect your feelings, since you're standing right in front of him, now overrides his need to protect your imaginary arm's-length friend's feelings. With this tall tale in place, you will likely get the constructive feedback you need. And if the player asks if he, too, can invest in the game, you'll know you've got something good on your hands.

In this age of developer delicacy and easily-bruised fruit, tactics like these are crucial to soliciting honest opinions from people who should know better.

Related Jobs

DeNA Studios Canada
DeNA Studios Canada — Vancouver, British Columbia, Canada

Analytical Game Designer
Blizzard Entertainment
Blizzard Entertainment — Irvine, California, United States

Senior User Experience Designer, Irvine
Blizzard Entertainment
Blizzard Entertainment — Irvine, California, United States

Senior User Experience Designer, San Francisco
Avalanche Studios
Avalanche Studios — New York, New York, United States

UI Artist/Designer


James Morgan
profile image
Your advice about, "My friend is making this game, and he wants me to invest in it," is fantastic. I have never been able to get really honest opinions from anyone close to me, but flipping it around to where honest feedback will be protecting me instead of hurting my feelings is something that never occurred to me. Thank you.

E McNeill
profile image
In the end, the only way to get honesty... was to lie to people.

Ryan Creighton
profile image
Fight fire with fire.

Sam Whillance
profile image
I always ask people what they don't like about my games. I'm not interested in fake reviews, or empty 5-star ratings. If someone hates my game, telling me why is worth more than 100 5 star ratings.

James Yee
profile image
I see this all the time with artists and writers I know. "Is my stuff good? Can you read my blog? What do you think of this image?"

You know what I do?

I tell them the bloody truth and screw their "feelings."

But I'm a dick like that. :)

Scott Simpson
profile image
I actually find that my developer friends are familiar with this problem and are pretty good about giving constructive feedback.
If I do ask a non-developer to look at something, I try to be in the room with them and watch their face as well as how they interact with my game. That way, what they actually say doesn't really matter as much as what I observe.

Damir Slogar
profile image
First you need to make sure they really want to hear an honest feedback. When your wife/girlfriend ask you "Do I look fat in this?", does she ask for honest feedback ?

Eric Finlay
profile image
Start-ups have the same problem, and I think I'm going to have to steal your line. It's a good line.

I've been guilty quite of few times of "Yeah...that's a neat idea. How 'bout that local sports team?"

Curtiss Murphy
profile image
Try the 5-1 rule, which means 5 positives for every criticism. Or, easier to swallow is the "Yes ... And" rule, which goes ...

Yes I like the way this works, and I like the idea behind the game - it has kinda a modern retro, spongebob meets politician thing going for it. AND I think it might be even better if the tutorial were cut from 10 minutes to 30 seconds, and if the interface was easier to follow, and maybe use snippets of dialog in place of 50 word stories.

There is much science to this approach. Another approach is the old: Name 2 things you didn't like and 2 things you did. This creates an expectation of flaws, which releases the tension.

TC Weidner
profile image
Exactly Curtiss. The problem lies in the fact that people dont know how to properly GIVE criticism. As you suggest, the correct way to do it, is to start with the things you liked, then you simply add and phrase the things you didnt like at the end. Using phrases such as " what Im not sure I get is... Or perhaps you may want to relook at... etc etc.

Its all about how you give criticism. Most people are very receptive and welcoming of criticism if its phrased correctly and done in the right way.

Mihai Cozma
profile image
My developer friends always give me the right, critical feedback I expect. The other are more retained and I have to educate them in "give me your worst, i can take it" :). When I have to give feedback to someone, I always give my best critical feedback but I take care in what words I use so the game's developer doesn't feel bad about it.