In designing games, as in writing, a valuable step to the process is to gather feedback from someone outside of your own head. During our science-based video game design unit, we play-test each other’s games, and work on giving feedback to what is noticed. While this happens quite a bit informally (“Hey, anyone want to try my game?” – a pretty common refrain in my classroom these days), I do try to formalize it a bit. The form we use comes from a new book on systems thinking, but I also had a similar form that I had made on my own.
I like how this new form incorporates the warm/cool feedback concept, and allows for reaction notes from the game designer. Obviously, this activity began with a mini-lesson on giving constructive feedback to other game designers, and how to use warm/cool feedback on someone else’s work.
It’s still interesting how some students read and accept the feedback, and ask for clarification from the play-testers, making adjustments to their projects, while others just shrug and go on as if the process never happened. They can’t get out of their own heads, and see the game objectively (“Well, I BEAT that level. You should, too. It’s easy.” — a student said this to me the other day. Me: “Well, you BUILT that level, so you know it inside and out. It’s not easy at all if you don’t know it.”). This is part of the learning process.
Peace (in the game),