Speaker to deliver two food safety talks at Oslo Aquatiq Forum in September 2026

The speaker’s upcoming talks signal a renewed emphasis on proactive hazard detection in food supply chains, moving beyond reactive litigation. The first talk frames poisoning customers as a business risk rooted in undetected supplier gaps and delayed responses. It cites real cases where costly settlements followed failures to act on positive tests. The underlying message is that preventing harm requires continuous monitoring akin to observability in software systems.

Historical examples from Norway illustrate how initial warnings can misdirect efforts if investigators do not pursue alternative sources after an alert. The 2006 morrpølse outbreak required thousands of samples before the true source was identified, showing the cost of incomplete traceability. Engineers see a parallel in systems where early alerts are ignored or misattributed, allowing faults to propagate. The lesson is that observability must include validation and cross-checking of signals.

The second talk shifts focus from financial penalties to criminal liability, raising the personal stakes for decision-makers. When insurance no longer covers prison sentences, organizations face stronger incentives to embed rigorous checks and documentation. Adopting such rigor entails investing in audit trails, real-time testing, and clear escalation paths, costs that appear in budgets as overhead but reduce uninsurable losses. The change stops working when firms treat these controls as checkboxes rather than integral processes.

Ultimately, the talks argue that the price of neglecting detection far exceeds the price of prevention, a principle that translates to any engineered service. Observability practices that capture anomalies, trigger timely investigations, and enforce accountability can avert catastrophic outcomes. Where monitoring lapses or where responsibility is diffused, the protective benefit erodes, mirroring the food-industry scenarios described. Engineers should therefore view the talks as a case study in why robust observability is not optional but a core safety requirement.