Quality Assurance Process

How do you prevent defects before inspection finds them too late?

Problem: End-of-line inspection finds defects only after time, downstream work, and confidence have already been spent.

Question: Which defects can be prevented, which invariants can be automated, and where must human judgment retain stop authority?

Decision: Move controls to the earliest useful point, then verify the output and correct its earliest durable owner.

Quality assurance designs confidence into the process. Quality control inspects or tests the resulting output. The distinction matters: prevention and verification work together, but inspection alone cannot improve the process that produces defects.

Inputs

• A validated process and intended outcome.
• Quality requirements, unacceptable failures, and evidence boundaries.
• The approved governing standard or explicitly proposed setpoint, with its revision authority.
• Baseline defect, rework, delay, and outcome evidence.
• Named Pattern, Process, and Platform owners plus release and stop authority.

Assure Quality

1. Declare the contract. Name the beneficiary, output, quality setpoint, requirements, evidence source, process owner, release owner, and unacceptable failure. Output: a reviewable quality contract.
2. Prevent predictable defects. Improve inputs, templates, sequencing, training, interfaces, or environment before adding inspection. Place a checklist only where a critical omission still needs a pause-point control. Output: preventive controls at the producing source.
3. Automate invariants. Use schemas, types, tests, policy checks, or physical interlocks for deterministic facts a machine can compare reliably. Make failure block continuation when release would be unsafe or invalid. Output: fast, repeatable gates.
4. Preserve human judgment. Assign experts to assess ambiguity, context, values, usability, and exceptions that deterministic checks cannot settle. Name the evidence they inspect and who may stop or override, with rationale. Output: accountable judgment rather than automated theatre.
5. Verify controls and output. Confirm that required process controls ran with valid evidence, then inspect or test the completed output against the declared standard. Record failed, skipped, overridden, conditional, and untested states; none can silently become a pass. Output: separate process-control and output-compliance readings plus a release verdict.
6. Correct the earliest owner. Trace variance to the first durable cause: Pattern for framing or judgment, Process for sequence, handoff, or authority, Platform for repeated deterministic enforcement, and Standard only when accepted evidence shows the contract itself is miscalibrated or obsolete. A single failed run does not authorize a standard change. Output: a correction owner and next-run assertion.
7. Measure the next cycle. Compare prevention, gate performance, defects, rework, delay, and outcome measures with baseline. Retire controls that add no protective value and raise the standard only when later evidence supports it. Output: a measured baseline change.

Place Controls

Need	Best control	Human edge
A deterministic requirement must always hold	Automated invariant that blocks invalid continuation	Approve the requirement and handle legitimate exceptions
A critical action is easy to omit at a known pause point	Short GATE or PROMPT checklist item	Coordinate the team, assess prompts, and exercise stop authority
Meaning, ethics, fitness, or local context must be judged	Expert review with named criteria and evidence	Make and explain the consequential judgment
The output must conform before release	Quality-control inspection or test	Own the verdict and unresolved risk
The same defect returns	Change the earliest Pattern, Process, or Platform owner	Decide the durable correction and review its consequence

Generator Example

A generator should pass the same applicable gates as manually created output.

Before generation, read the authoritative registry, schema, or taxonomy; classify the intended artifact; and fail fast if the name, route, or purpose conflicts. During generation, constrain deterministic structure through templates and typed data. After generation, run the same formatting, type, link, test, and publication checks expected of human work. Keep human review for meaning, usefulness, risk, and exceptions.

If failures repeat, fix the earliest owner. A naming failure may belong to the Pattern or contract; a wrong sequence to the Process; a deterministic rule repeatedly interpreted by hand to the Platform. Adding reminder prose after every failure is not assurance.

Deming's Implications

The Deming Institute's Fourteen Points emphasize constancy of purpose, building quality into the system instead of depending on inspection, continual process improvement, training, leadership, cooperation across boundaries, and participation in transformation. Applied here, they imply three practical rules:

• Treat defects as information about the system, not merely operator failure.
• Improve the producing process and capability instead of relying on final inspection.
• Give people the training, authority, and cross-team conditions needed to protect quality.

These are concise implications, not a replacement for the source or a claim that one checklist implements Deming's management system.

Checks

• Prevention occurs before the expensive or irreversible point.
• Automated gates enforce only deterministic requirements they can observe reliably.
• Human reviewers have criteria, evidence, and explicit stop or override authority.
• Output verification uses the declared contract and exposes every non-pass state.
• Process-control compliance and output compliance are both verified and remain separate readings.
• Recurring defects change the earliest durable owner rather than adding downstream inspection.
• Process measures and outcome measures are compared with baseline on a later run.

Failure Modes

• Inspection dependence: defects are found repeatedly but the producing system stays unchanged.
• Automation overreach: a machine check pretends to settle meaning, values, or context.
• Advisory gate: a failed critical invariant does not block continuation.
• Silent override: a person bypasses a control without evidence, authority, or rationale.
• False pass: skipped, conditional, failed, or untested checks disappear from the verdict.
• Downstream correction: the release checklist grows while the earliest cause remains intact.
• Gauge failure: the measuring instrument is not itself tested or calibrated.

Proof Of Done

The process rejects a deliberately invalid input or output at the earliest designed control, allows a valid case to proceed, preserves expert judgment for an ambiguous case, and records stop or override evidence. A later run shows whether the correction reduced defects or rework without degrading the intended outcome.

Changes my mind: repeated evidence shows that a control adds more delay or risk than it prevents, cannot observe its claimed requirement, or catches a defect more effectively at another point.

Source Trail

• ASQ: Quality Assurance vs. Quality Control — source for the prevention-oriented QA and product-oriented QC distinction.
• The Deming Institute: Fourteen Points — source for the management-system implications summarized above.
• ISO 9001 process approach — primary guidance for inputs, outputs, ownership, risks, controls, evaluation, and improvement.

Context

• depends-on Process Modelling — define intended ownership, interfaces, risks, and measures before installing assurance.
• depends-on Standards — supply the governing setpoint, evidence contract, and authority for any revision.
• pairs-with Checklists — coordinate critical human controls at exact pause points.
• proved-by Performance Reality — test whether prevention and correction improved the next cycle.
• applies-to Standard Templates — build repeatable quality into the producing instrument.
• pairs-with Control System — connect setpoint, gauge, authority, and correction.

Questions

Next question: Which recurring defect can move from downstream inspection to an earlier Pattern, Process, or Platform control?

• Which judgment must remain human even if every deterministic invariant is automated?