Industry and Organizational Context

This case examines a regulated manufacturing organization producing products subject to formal quality standards. Quality deviations are recorded when product, process, or documentation does not conform to approved specifications, and each deviation requires a formal disposition decision.

• Deviations originate from inspection, production, testing, suppliers, or audits.

• Disposition decisions determine whether material is accepted, reworked, repaired, scrapped, or escalated.

• Poor disposition discipline increases compliance risk, cost, and customer exposure.

Leadership initially viewed deviations as a volume problem, but operational instability came from inconsistent treatment of individual deviations.

How the Work Was Intended to Function 

On paper, quality deviation disposition was intended to operate as follows:

• A deviation is documented with objective evidence.

• Engineering and quality assess impact and root cause.

• A disposition is approved according to quality policy.

• The decision is executed and recorded for traceability.

Leadership believed this standardized workflow could handle all deviations consistently.

What Was Actually Happening

In practice, deviations behaved very differently:

• Low-risk deviations waited in queues designed for high-risk cases.

• High-impact deviations were sometimes rushed under schedule pressure.

• Teams disagreed on what constituted an acceptable risk.

• Disposition meetings became debates rather than decisions.

The failure mode was not missing procedure. The failure mode was misclassification of deviations.

How FLOW Was Introduced

Leadership was not seeking to weaken quality controls. They were seeking consistency and defensibility. Specifically, they wanted:

• A shared language to distinguish minor deviations from consequential ones.

• A way to avoid over-review of low-risk issues.

• A basis for escalation grounded in impact, not opinion.

FLOW was introduced as a classification lens to evaluate each deviation before disposition routing.

Identifying the Unit of Effort

Rather than focusing on defect rates or backlog counts, the organization anchored on a single unit:

• Unit of Effort: one documented quality deviation requiring a formal disposition decision.

• Each deviation is evaluated independently.

• Aggregate metrics are tracked separately and are not used to classify the unit.

How Complexity Was Determined

Complexity was defined as the amount of technical and regulatory judgment required to determine acceptability.

• Low complexity deviations have clear specifications and objective accept/reject criteria.

• Higher complexity deviations involve ambiguous requirements or conditional acceptability.

• Higher complexity deviations require engineering judgment or regulatory interpretation.

• Higher complexity deviations increase the risk of unintended downstream effects.

This definition of complexity was applied consistently across all deviations in this case.

How Scale Was Determined

Scale was defined as the breadth of impact created if the deviation is accepted, reworked, or released.

• Number of units, lots, or batches affected.

• Number of customers or downstream processes exposed.

• Degree of regulatory or audit visibility created by the decision.

Cost and scrap value were tracked, but they were not used as the primary definition of scale.

Other Measures of Scale Considered

Several commonly used indicators were considered but not used for classification:

• Dollar value of affected material.

• Time pressure from production schedules.

• Customer delivery urgency.

These indicators influenced planning, but they did not reliably reflect impact breadth or compliance risk.

Applying FLOW to Real Quality Deviations

With complexity and scale definitions fixed, each deviation was classified before disposition approval:

• Determine complexity first (judgment required).

• Determine scale second (impact breadth).

• Assign a single FLOW classification to the deviation.

FLOW A — Local, Contained Deviations

Example: a cosmetic surface blemish within documented acceptance criteria.

• Complexity: low.

• Scale: low.

• Handling implication: rapid disposition using standard acceptance rules.

FLOW B — Broader Impact Deviations

Example: a dimensional deviation affecting multiple units in the same lot.

• Complexity: low (well-understood requirement).

• Scale: moderate (multiple units and processes affected).

• Handling implication: coordinated review to manage exposure, even though the deviation is clear.

FLOW C — Complex, Judgment-Driven Deviations 

Example: a deviation requiring functional analysis to determine fitness for use.

• Complexity: high (engineering judgment and tradeoffs required).

• Scale: low-to-moderate.

• Handling implication: deliberate analysis and documentation before disposition.

FLOW D — System-Level Deviations

Example: deviations affecting a released specification used across multiple products.

• Complexity: variable.

• Scale: high (cross-product and regulatory impact).

• Handling implication: formal governance and cross-functional alignment.

FLOW S — Exceptional Deviations

Example: deviations with immediate safety or compliance implications.

• Normal disposition timelines are inappropriate.

• Explicit exception handling is required.

• Regulatory notification may be necessary.

What Changed After FLOW Classification

Once deviations were classified consistently, disposition outcomes stabilized:

• Routine deviations were resolved faster without unnecessary escalation.

• Higher-impact deviations received visibility early enough to manage risk.

• Disposition rationale became consistent and auditable.

Organizational Implications 

FLOW classification reshaped how quality decisions were made:

• Escalation was tied to impact breadth rather than fear of audit.

• Review effort matched the nature of the deviation.

• Quality decisions became explainable, consistent, and defensible.