Process

Solutions vs. problems

Players suggest fixes, but your job is finding the problem behind them.

Also called the problem behind the request.

In plain words

Testers rarely describe problems. They describe solutions: “It needs a jetpack.” “Add a skip button.” Their solution is often wrong, but the problem underneath it is almost always real. Your job is to dig it out.

See it

“It needs a jetpack” really means “I was stuck at the bottom of that cliff and wanted to get up.” The fix might be a ladder, a different path, or a clearer hint, not a jetpack. A sports player asking for new boots may really be slipping on the turn, and need footwork practice.

Why designers care

Players aren’t designers and shouldn’t have to be. Treat every request as a clue. Ask what wall they hit that made them wish for it. Often several different requests point to the same single problem, and fixing that one problem answers all of them.

Common mix-up

Ignoring requests isn’t the point. Taking them seriously is: seriously enough to find what caused them.