Tester "opinions" are a waste of time. If they seem aligned in direction, you can do something about what the testers are noticing. Or if you have on-staff QA who can tell you which issues are critical and which are not. Pivoting at the sound of tester opinions is a surefire way to fragment your design.

To decide which bugs to fix first amid conflicting tester opinions, I would have prioritized issues that align most closely with the game’s core experience, focusing on bugs that hinder key mechanics or narrative flow. By examining the context of each bug, I would have assessed if it disrupts immersion or causes frustration, prioritizing those that impact player engagement. I would also have consulted with the design and tech leads to gauge which bugs might cascade into larger issues if left unresolved. This approach would allow us to address critical blockers, ensuring a cohesive and enjoyable player experience.

You get your product manager to decide! Putting that aside, various options: - Widen the testing pool to identify which prevails - Assess ease vs impact for the various bugs, use a Kaizen PICK chart to support - A/B test

Dealing with conflicting tester opinions can be challenging, but prioritizing bug fixes requires focus on three key factors: 1) Assess impact—fix issues that break gameplay or cause crashes first; 2) Check frequency—prioritize bugs reported by multiple testers; and 3) Weigh complexity—quick fixes that enhance user experience can be highly rewarding. Balancing these factors helps streamline the process and ensures the most critical issues are resolved efficiently. How do you approach prioritizing bug fixes?

Para decidir qué errores corregir primero cuando hay opiniones contradictorias de los testers, priorizo en función del impacto y la frecuencia del problema. Primero, atiendo los errores críticos que afectan la jugabilidad básica o rompen la experiencia del juego, ya que pueden desmotivar a los jugadores rápidamente. Luego, considero la frecuencia con la que se reportan ciertos problemas; si muchos testers mencionan un mismo error, es señal de que debe abordarse pronto. Finalmente, evalúo qué correcciones aportan más valor al equilibrio y disfrute del juego, siempre manteniendo en mente la visión general del diseño.