Frame the problem as a task
Begin with a defined task, such as understanding an instruction or completing an interaction. Specify the game version, participant criteria and observation scope. A reader should understand what the player was trying to do; otherwise, pauses from unrelated tasks can be grouped into a misleading problem.
Describe the sequence before diagnosing it
Repeated actions may indicate difficulty, but they may also be deliberate exploration. A pause may have causes outside the task. Describe the step, preceding and subsequent actions, and available screen evidence before proposing explanations that need checking. The record and the interpretation should remain distinguishable.
Prioritize with evidence and impact
Separate issues that prevent progress from those that add effort or concern a preference. Document the relevant usable observations, conditions and gaps. One experience does not represent every player. A prioritized issue list is a basis for decisions, not proof that resolving it will improve retention.
Check a change through another study
Choose a specific, interpretable issue, propose a change and examine it under suitable conditions. UXPlus is currently a game user experience research pilot. Confirm the version, tasks, participants and deliverables before starting. Its findings can inform improvements without guaranteeing that a particular change will increase retention or revenue.
Explore the related service · Research methods and scope · Discuss a study