VOL. VIII · CH. 8.7 · PROJECT MANAGEMENT

Quality Assurance Processes

Quality as an organizational process, not just the automated tests covered in Part VII.

DivisionQA / Project Management

DifficultyIntermediate

Prerequisites7.4

Related8.6

2 min read · 351 words

8.7.1Definition

Quality assurance (QA) as an organizational process is the set of practices — manual testing, launch checklists, sign-off gates — that verify a product meets its requirements before release, complementing rather than replacing automated testing (7.4). Where Chapter 7.4 covers automated verification of code behavior, this chapter covers the broader process ensuring the right things get checked before anything ships.

8.7.2Why It Exists

Automated tests verify what they were written to verify — they cannot catch a requirement that was misunderstood at a level tests were never designed to check, or a launch-blocking issue outside code correctness entirely (missing legal copy, unverified content, an unresolved dependency). QA process exists to catch this broader category of issue through structured human review, not just automated verification.

8.7.3Core QA Practices

Test plans — a structured document of what will be manually verified before release, covering flows automated tests may not.
Launch checklists — a standard, reusable list of items to confirm before any release (legal content, real vs. placeholder data, monitoring in place).
Sign-off gates — an explicit approval step before release, ensuring accountability for the decision to ship.

8.7.4Common Mistakes

Treating a passing automated test suite as sufficient QA, missing issues automated tests were never designed to catch — fabricated content, missing disclosures, unreviewed legal copy.
No standard launch checklist, relying on memory to catch the same recurring category of pre-launch issue every time.
No clear sign-off owner, leaving ambiguity about who actually decided a release was ready.

8.7.5Best Practices

Maintain a standing, reusable launch checklist that captures recurring pre-launch risks specific to the product category.
Require an explicit sign-off step before any release, with a clearly identified owner of that decision.
Treat automated tests (7.4) and manual QA process as complementary, not substitutes for each other.

Real-World ExampleThe Iron Ridge Combat Club evaluation — which identified fabricated competition results, recycled stock footage, and a missing waiver checkbox as launch-blocking issues — is a direct example of manual QA process catching exactly the category of problem automated testing was never designed to detect.

← Back to Part VIII — Project Management