When two ideas compete, “I like this one” is a starting point rather than a complete evaluation. A useful comparison puts both ideas against the same player task.
Agree on the task
Choose something concrete, such as finding a game mode, reading a rule or submitting a support request. Give each design the same information. If one has clearer wording and the other has better artwork, separate those differences instead of crediting everything to the layout.
Observe a few meaningful outcomes
Can a player identify the next action? Do the labels make sense without explanation? Can the task be completed on a phone? Ask where the person hesitated and what they expected to happen. Do not present a small informal comparison as a representative survey of all players.
Record disagreement usefully
One option might be faster for frequent users while another is clearer for newcomers. That is a design trade-off, not proof that one group is wrong. Note the audience and device for each observation.
End with a small recommendation
Propose the next change and explain which observation supports it. A revised label or reordered step may solve the problem without a full redesign. If you publish results, describe how the comparison was run and avoid invented scores or participant counts.
Related reading
Write a suggestion that a team can evaluate
https://panel.zeismoplay.com/community/topic/22
Build for keyboard, controller and touch players
https://panel.zeismoplay.com/community/topic/28
0 thanks
