New episode! Should Game Designers Listen to Negative Player Feedback?
Added 2020-05-07 18:47:05 +0000 UTCPlayers certainly aren't shy about sharing their thoughts on video games. So what should developers do when players tell them they hate a certain game mechanic, character, or level? This video will explore some tips for responding to feedback and criticism.
Hope you like it!
Mark
Comments
I just came across a very early example of this from Compute!'s October 1983 issue, in an article talking about the rise of online gaming... Have a look at p. 36, left hand column of https://archive.org/details/1983-10-compute-magazine/page/n37/mode/2up The salient bit discusses a game called DECWARS, and says "After a long development -- marked by enthusiastic suggestions from nearly everyone -- the game went on-line. Immediately, CompuServe was flooded with suggestions for improvement. People would sign on the DECWARS SIG and fill the screen with criticisms. It became a significant problem. After that experience, [programmer Russ] Ranshaw says they all realized that while suggestions are great, there comes a time when the programmer simply must do what seems best, letting others decide whether the game's fun to play."
Richard
2020-07-20 18:50:54 +0000 UTCFeedback is always useful in developing any project, as long as it becomes constructive. Great video.
NXT STUDIOS
2020-05-22 11:51:12 +0000 UTCI came across this quote from Shigeru Miyamoto talking about making the first Zelda game in his 2007 GDC Keynote that is very relevant to this video: ...and a lot of people said, “Look, why don’t you just make one way through the dungeon? No multiple paths.” But of course I ignored them all. Rather than making it easier for players to understand, I decided to take their sword away from the very beginning. You do that, then you know what you have to do. See, I did this because I wanted to challenge them to find that sword, because I knew that they would think about these problems. They would think before they go to sleep, “How am I gonna do this?,” or maybe as they’re riding to work in the morning. And at the same time, I wanted them to talk with other Zelda players and exchange information: ask each other questions, find out where to go next, exchange information. And that’s what happened. Source: 7:30 - 8:30 in this clip: https://youtu.be/jqBee2YlDPg
Sabrina Bea
2020-05-12 12:44:49 +0000 UTCMark, I cannot stress how important and necessary this video is on today's obsessive hypercynical culture of either contempt or, arguably worse, hypercriticism without a single consideration as to WHY something would be added to a game. Analytical discourse and feedback discourse benefits greatly from this greatly written, easy-to-follow video, JAM PACKED with a lot more of depth than I usually see in your videos (Which, bear in mind, is not a bad thing - Your channel is by far one of the most importants for aspiring and up-and-coming game designers) and amazing, diverse and extremely relevant examples - to the point I could easily talk about several others that you haven't cited, but easily gave room for. I know it feels like I'm just sucking up to you or just exxagerating, and maybe it really is just the thrill of finally seeing someone speak up in a well-directed and well-writen way what I've been having trouble telling everyone around me for the past 5 years as a game designer, but I just wanted to say... Thank you. As a long-time fan and patreon supporter, thank you very very much. You continue to prove yourself as one of my favourite YouTubers and a great educational resource for Game Design.
Cyber Twilight
2020-05-09 02:49:33 +0000 UTCI was just rolling around in bed trying to think about how to solve some recently player feedback, got up, grabbed the laptop, and saw this video was available. Perfect timing. In my full time job as a user experience designer, I often tell my clients that the core of my job is to be a problem solver. So I say focus on explaining the problems and I'll come up with the solution. This not only turns the situation around where a client constantly tells you the solutions to implement, but also takes the pressure off on them to try and fix everything. We're much better at critiquing than we are solving.
Boz
2020-05-08 15:52:09 +0000 UTCVery nice and interesting topic :)
Andreas Sjølund Pedersen
2020-05-08 06:18:11 +0000 UTCI found this video very vindicating, as these points are almost verbatim what I've been teaching my students for so many years haha!
Gunnar Clovis
2020-05-07 22:33:18 +0000 UTCSolid video! This does a great job of explaining the subtleties of feedback --- something I'm trying to get better at responding to (correctly) with my game prototyping endeavors.
Logan Moore
2020-05-07 21:29:35 +0000 UTCThanks for the video, Mark. Feels timely--I've picked up Valorant recently, even though I'm not much of a competitive shooter guy. Even though it's in beta, it's wonderfully polished and full of crunchy mechanics that make a player interested in game design happy. But I've also been lurking quite a bit on the subreddit, which is already curdling into a toxic mess. A lot of that centers around feedback unrelated to game design (some feel the anti-cheat package is invasive), but that atmosphere comes to invade everything about the relationship between the development team and its community. I still have hope, but it seems like an unwinnable challenge. Anyways, I appreciate the thoughtful video and hope that you're able to influence the mindset of some entitled players who aren't thinking about the development teams on the other side. Cheers!
Daniel Zaleznik
2020-05-07 19:08:21 +0000 UTC
