Don't Stop, Girlypop!

Role and responsibilities

Gameplay QA / UX Playtesting Support

• Performed structured PC playtesting with primary focus on controller-based gameplay.
• Evaluated onboarding, controls, menus, weapons, abilities, prompts, and core-loop readability.
• Identified and documented usability concerns with clear context, player impact, and reproduction notes where applicable.
• Compared controller and keyboard input flows to identify accessibility, mapping, and progression risks.
• Translated player-facing friction into concise, actionable QA feedback supported by GUESS-18 evaluation data.

Testing activities

• Structured exploratory playtesting
• First-time user experience and onboarding evaluation
• Controller support and input-flow validation
• Keyboard and controller comparison checks
• Menu, prompt, keybinding, and pause-behavior usability review
• Core-loop, weapon, ability, and progression-readability analysis
• Audiovisual clarity and player-experience assessment
• GUESS-18 based feedback consolidation

Coverage areas

• First-time user experience and progression clarity
• Controller mapping and keyboard input comparison
• Core loop, weapons, abilities, and combat readability
• Menus, prompts, keybindings, and pause behavior
• Difficulty perception, pacing, and gameplay readability
• Visual identity, atmosphere, music, and sound design
• Player comprehension, usability, and overall experience flow

Representative QA findings

• Identified and documented onboarding clarity risks affecting first-time player comprehension and early progression.
• Reported controller mapping gaps where required actions were not consistently accessible through gamepad input.
• Flagged prompt and input-flow inconsistencies that could make progression less clear during early play.
• Documented keybinding persistence concerns and their impact on player confidence across sessions.
• Reported pause-state and menu-behavior issues affecting player control during active gameplay sequences.
• Highlighted positive core-loop engagement once movement, combat rhythm, and mechanics became clear.
• Noted strong audiovisual identity and pacing alignment, while also flagging potential repetition risks for review.
• Consolidated usability, clarity, and player-experience findings into structured feedback for development follow-up.

Challenges

• Evaluating intended player flow while controller support and input coverage were still being refined.
• Separating subjective preference from reproducible usability, clarity, and accessibility concerns.
• Turning broad playtest observations into concise, actionable QA feedback.
• Balancing qualitative player-experience feedback with structured GUESS-18 evaluation data.

Lessons learned

• Controller support should be validated across the full player journey, not only during isolated input checks.
• Onboarding quality directly affects how quickly players understand the core loop, mechanics, and progression goals.
• Effective playtest feedback should connect each issue to context, player impact, and expected experience.
• Structured frameworks such as GUESS-18 help support qualitative feedback with more consistent evaluation criteria.

Methods and tools

• PC playtesting
• Controller and keyboard input comparison
• GUESS-18 evaluation framework
• Structured QA documentation
• Usability and player-experience analysis
• Issue reporting and feedback consolidation