Unlock Better Game UX: A Lazy‑Person’s Guide to QA, Personas, and Benchmarking

1. Requirement Analysis – 5 Why Method

Collect raw requirements (player feedback, design briefs, market data) and decompose them with the 5 Why technique to reach root causes and concrete keywords. Example:

Why 1: Why can’t players hit the target?
- 1.1 Aim difficulty (manual aiming)
- 1.2 Target selection (wrong target)
- 1.3 Vision obstruction (camera)
Keywords: operation precision, target selection, camera control

Why 2 (branch 1): Why is manual aiming hard?
- 1.1.1 High aiming difficulty
- 1.1.2 Non‑directional skill
Keywords: manual difficulty

Why 2 (branch 2): Why does auto‑lock target the wrong enemy?
- 2.1 Lock‑priority based on distance only
- 2.2 No threat‑value weighting
Keywords: lock priority, target weight

Why 3: Why does the camera lose the target?
- 3.1 Camera lag on fast movement
- 3.2 Camera blocked by environment
- 3.3 Camera spin too fast (dizziness)
Keywords: camera tracking, collision, comfort

The final keyword set drives the rest of the workflow.

2. User Persona Construction (9 Dimensions)

Basic attributes : age, gender, region, language, occupation, device type.

Physical & cognitive traits : vision/hearing ability, dominant hand, memory style, learning preference.

Behavioral traits : interaction patterns, operation complexity (single‑tap, multi‑tap, hot‑keys), rhythm, social role.

Scenario traits : typical play time (morning/evening), environment (commute, home, office), social context (alone, with friends).

Community role : leader, contributor, casual participant.

Motivations : achievement, competition, social belonging, curiosity.

Cultural & aesthetic preferences : art style, UI language, value orientation.

Economic factors : disposable income, willingness to pay, price sensitivity.

Hardware & software context : platform (iOS/Android/PC), OS version, network quality, app familiarity.

Example: a 25‑35 year‑old mobile gamer who plays nightly on a high‑end phone, values precise lock‑on and smooth camera.

3. Role Mapping (Stakeholder Motivation Map)

Role name (official title)

Nickname (informal name for quick reference)

Importance (high / medium / low)

Core motivations : power, money, reputation, social contribution.

Acceptance criteria : must‑have, should‑have, nice‑to‑have features.

Separate internal teams (development, QA, product, ops) from external parties (players, partners, regulators) and fill the matrix for each role.

4. Benchmark Analysis – Interface Traversal

Identify three benchmark types: direct (same genre, same user), indirect (different genre but similar function), fundamental (same underlying need).

Traverse each competitor’s UI: menu navigation → feature flow → special interactions (long‑press, swipe) → documentation.

Record observed features in a structured table (feature, location, advantage, limitation).

Compare against the keyword set to spot gaps and inspiration.

5. Scenario Validation

Build concrete use‑cases using the template:

Persona: [core persona]
Time: [e.g., night commute]
Location: [e.g., subway carriage]
Trigger: [push notification, BOSS appears]
Actions: [manual camera pan, auto‑lock toggle]
Props (optional): [headphones, limited bandwidth]

Execute the scenario, note pain points, positive moments, and map them to the previously extracted keywords.

6. Synthesis & Design Inspiration

Cross‑reference persona pain points, role motivations, benchmark strengths, and scenario findings.

Prioritise design ideas that address high‑importance keywords (e.g., improve lock‑priority algorithm, add camera damping).

Produce a concise, actionable list of design recommendations with clear acceptance criteria.

This systematic workflow turns vague player complaints into a validated, stakeholder‑aligned design direction without heavy documentation overhead.