My designer buddy, Kevin Nunn, is exploring the different ways we game designers utilize play tester feedback. That series of articles has sparked an interesting discussion in the comments and is worth reading.
“Give me problems, not solutions.”
So said our mutual friend. He’s interested in a play tester’s gut response to his game, to help pinpoint elements of the design that aren’t working as intended or which cause un-fun moments in play. His job as a designer, as he sees it, is to analyze those faults and propose solutions to them to achieve the play experience he’s looking for.
Kevin has a somewhat different philosophy of utilizing play tester feedback. He sees the designer’s role in play testing as a winnower. Kevin listens to everything his play testers have to say and sifts through the inevitable chaff to glean the fat kernels of insight that will inform his future design choices.
Our mutual friend’s mantra struck me as something of a revelation: I’d never imagined so direct an approach to play tester feedback. “Give me problems, not solutions.”
Considering the argument from a data analysis perspective, if a dozen play testers offer a dozen solutions to a single problem, the useful data is the problem, not the solutions.
Food for thought.