Juniper Contamination / Five Whys Analysis

Root Cause

The immediate cause was a contaminated juniper lot, PDI-JNP-220620, received from a Vietnam-based supplier on 20 June 2022. The more important failure was structural: there was no intake control capable of detecting it before it entered production.

The exact cause of the contamination was never confirmed. Sensory evidence pointed to either microbial activity or oxidative degradation during storage or transit, but no lab analysis was performed. The investigation confirmed the failure was upstream. The juniper arrived compromised. No error was identified in distillery handling, production, or quality control execution.

Lot PDI-JNP-220620 moved through intake, production, and four consecutive QC assessments before the deviation was caught. Detection depended on chance, not design.

Five Whys

The Five Whys below trace how that detection failure was built into the process.

WHY 1
Why did contaminated juniper pass quality control across four consecutive batches?
The contamination was subtle. Each batch was assessed against a reference bottle selected at the time from available finished goods, rather than against a fixed baseline. Because the reference batch changed from one assessment to the next, small shifts across consecutive batches were harder to detect.
WHY 2
Why was each batch assessed against a changing reference batch rather than a fixed baseline?
The quality control process did not require a fixed reference bottle, so the assessor could choose any reference bottle from finished goods at the time of assessment.
WHY 3
Why did the quality control process not require a fixed reference bottle?
The process was built to judge whether a batch was acceptable, not to detect slow drift across batches caused by lot-to-lot ingredient variation. That risk was not part of the control design.
WHY 4
Why was ingredient variation not recognised as a risk?
Supplier consistency was assumed rather than verified. Because the supplier had not caused a quality issue before, lot-to-lot variation was not treated as a failure mode. As a result, there was no intake check to test that assumption.
WHY 5
Why was there no intake check to test that assumption?
Supplier selection was based on price and availability, not on demonstrated consistency. Because consistency was assumed rather than tested, no intake verification step was ever built into the process.

Structural Root Cause

Finding
Supplier quality and consistency were not treated as reliability requirements. The system relied on an assumption of consistency that was never tested, so no detection step was built into intake. Final QC became the only downstream point where problems could be found, and it was not designed to catch this type of failure.