How do we distinguish quality assurance from quality control?

Process-versus-output checks

Use 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

  1. Identify how defects are prevented
  2. Identify how outputs are verified
  3. Assign owners for both activities
  4. Review gaps across the delivery lifecycle
Recommended action flow for process-versus-output checks: Identify how defects are prevented then Identify how outputs are verified then Assign owners for both activities then Review gaps across the delivery lifecycle. Escalate when one type of activity is being used to excuse the absence of the other.

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

Practice references