QA isn't about finding bugs for the sake of reporting them.

It's about checking whether the player's actual experience aligns with the project's intent.

In the early stages, teams often consider QA the final stage.

In practice, the absence of QA before release leads to:

- design errors disguised as "features"

- inconveniences attributed to "hardcore" gameplay

- pacing issues noticed too late

A developer should always know how their game should be played.

A player shouldn't.

QA is needed not because the team lacks competence,

but because any project inevitably becomes distorted from within.

In QA, a publisher doesn't look at the number of bugs, but at:

- clarity of mechanics without explanation

- readability of the interface

- stability of pacing

- moments of frustration that the developer has stopped noticing

It's important to understand:

QA is not criticism or control. It's a way to restore objectivity to the project. The earlier QA is involved in the process, the fewer painful decisions have to be made before release.