How do we distinguish quality assurance from quality control?
Process-versus-output checksUse process-focused prevention and output-focused verification together. The practical question is whether your approach both reduces the creation of defects and detects unacceptable results before use.
What to do now
- Identify how defects are prevented
- Identify how outputs are verified
- Assign owners for both activities
- Review gaps across the delivery lifecycle
When to escalate
Escalate when
One type of activity is being used to excuse the absence of the other.
Who decides
The acceptance authority and relevant quality owner
Example
A reviewed development method supports assurance, while transaction tests verify the delivered result.
Mistake to avoid
Assuming a documented process proves every deliverable is correct.
Prevent a repeat
Check that closure evidence proves the agreed outcome instead of relying only on a completion percentage.
Suggested ApprovedFlow setup
- Tasks
- Documents
- Approvals
Attach acceptance criteria and test evidence to the deliverable or task, then record the authorized review decision. See the platform
Related cases
- Can we launch with known defects?Uncontrolled residual quality exposure
- How do we keep quality evidence usable after handover?Unusable evidence archive
- A scheduled backup is running, but nobody checks failures. Is that a control?Unowned operational assurance
- How do we distinguish an output, an outcome, and a benefit?Value-chain confusion