Overview
Balance testing fails when it's informal. The designer plays the game for 20 minutes, decides a weapon "feels too strong," and nerfs it. Another designer plays the same game, decides the weapon "feels fine," and doesn't change it. The outcome depends on who played, not on the weapon's actual balance state. Informal testing produces inconsistent results because it is subject to the tester's skill, playstyle, and subjective judgment.
The Balance Testing Methodology prompt builds structured test frameworks with three properties: (1) hypothesis-driven testing — each test has a specific hypothesis (e.g., "Weapon A's DPS is >10% above the target range"), a measurable outcome (DPS measured against standard enemy), and a pass/fail criterion (if DPS >110% of target, the hypothesis is confirmed and the weapon needs adjustment), (2) statistical significance — the test plan specifies the sample size needed to distinguish a real balance issue from random variance, preventing both false positives (nerfing something that is actually fine) and false negatives (missing something that is actually broken), and (3) tester bias mitigation — the test plan controls for tester skill, playstyle, and familiarity through standardized test protocols, diverse tester pools, and blind testing where the tester doesn't know what balance state they're testing.
What you get: - Hypothesis-driven test plan template - Sample size calculator with statistical significance requirements - Tester bias mitigation protocol - Automated balance test specification - Balance regression test suite - Balance testing calendar with phase gates
Built for: QA teams, balance designers, and playtest coordinators who need balance decisions backed by data — not by whoever played the game last.