Break the Cycle of Recurring Problems: Stop Playing “Whack‑a‑Mole” with Repeat Incidents

The Event Whack‑a‑Mole Theorem—coined by BlueDragon founder Rob De La Espriella—captures a hard truth of high‑risk operations: if you only swat at symptoms, similar incidents will keep popping up because a finite set of deeper, systemic causes remains untouched. The theorem explains why organizations feel busy yet fall behind—expending energy on visible events while latent organizational, programmatic, and cultural factors continue to align and re‑create repeat failures.

Rob’s work—built on 30+ years of root cause analysis across regulated sectors—formalized a lean, evidence‑driven way to end recurrence by integrating critical thinking, systems thinking, and human performance into one practical framework.

 

Why Recurring Problems Keep Coming Back

Surface fixes feel fast—but they’re shallow. Under pressure to restore operations, teams often patch symptoms (a procedure tweak here, a retraining there) without testing whether those actions address the deepest systemic causes. This reactive pattern moves work back online quickly while leaving latent weaknesses untouched—an outcome many regulators warn against when emphasizing graded causal evaluations and effectiveness reviews that prevent recurrence.

Complex systems demand holistic analysis. High‑risk operations are shaped by interlocking technical, organizational, and human factors. Models like James Reason’s “Swiss Cheese” show how accidents emerge when multiple barriers fail and latent conditions align—not because of one “bad actor” or isolated error.

Human performance is the infinite variable. DOE’s Human Performance Improvement (HPI) guidance highlights how latent organizational weaknesses (work environment, workload, procedures, culture) create error‑likely situations. If we don’t hunt and mitigate these latent factors, the same classes of incidents will recur—no matter how many symptoms we fix.

 

The “Whack‑a‑Mole” Trap (and Its Cost)

BlueDragon’s theorem describes a common failure pattern: organizations keep knocking down individual incidents while a finite set of deeper causes (programmatic, organizational, cultural) remains undiscovered and unaddressed. The result is a false sense of control and a growing corrective‑action backlog.

Financially, recurrence is a silent drain. Quality literature consistently shows the Cost of Poor Quality (CoPQ)—rework, downtime, warranty, compliance penalties—can reach double‑digit percentages of revenue, creating a powerful case for prevention over repeated containment.

 

Why Traditional Root Cause Analysis Falls Short

Many legacy RCA programs fragment analysis across tools (5‑Whys, fishbone, etc.), silo human factors, and take months to finish—delaying learning and inviting “fix‑it‑fast” patches. Current industry guidance urges graded, evidence‑based causal evaluations that integrate human, technical, and organizational contributors with speed and rigor.

The nuclear and government sectors have long codified good practice—IAEA manuals and DOE standards emphasize comprehensive data collection, barrier analysis, change analysis, and management oversight—yet even well‑documented RCAs can underperform if they stop at the event level instead of pursuing deepest‑seated causes and verifying effectiveness.

 

Breaking the Cycle with BlueDragon: Lean, Evidence‑Driven, Holistic

BlueDragon’s framework was built to solve modern, human‑centric problems in complex socio‑technical environments—fast. It integrates critical thinking, systems thinking, and human performance with a disciplined three‑phase flow: Phase 1 gathers and analyzes evidence; Phase 2 drives cause‑and‑effect analysis to the deepest causes; Phase 3 designs corrective actions that prevent recurrence.

  • Speed without sacrificing accuracy: Lean investigations complete in days or weeks—not months, minimizing downtime while maintaining rigor.
  • Holistic depth: Human, cultural, and systemic factors are integrated—so fixes target latent organizational weaknesses, not just immediate triggers.
  • Evidence‑driven transparency: The methodology relies on verifiable facts and structured logic, making findings and Lines of Inquiry (LOIs) clear to stakeholders and regulators.

BlueDragon’s Event Whack‑a‑Mole Theorem is supported by systems theory and systems thinking. The BlueDragon framework breaks the cycle of solving individual problems by codifying how to inventory and analyze a holistic set of defenses (“administrative requirements, physical barriers, cyber controls”)—preventing systemic issues from recurring, not just one event.

 

What “Breaking the Cycle” Looks Like in Practice (Blueprint)

To move from firefighting to permanent solutions, leaders can adopt the following blueprint—each step grounded in proven guidance:

  1. Make investigations lean and evidence‑driven.
    Use AI-enhanced data analysis, systems thinking and critical‑thinking practices during BlueDragon Phase 1 to avoid bias and generate focused lines of inquiry, because asking the right questions is how you solve problems (ask Einstein). During Phase 2, causal analysis, conduct focus groups in lieu of individual interviews, so that you can use the expertise of hundreds of SMEs in a short amount of time.
  2. Go deeper than event root causes—hunt latent organizational, programmatic and cultural weaknesses.
    Think like a Doctor: identify and investigate surface level symptoms (the initial non-compliance or deviations) and behavioral factors (at-risk behaviors and error-likely situations), and environment factors, and the defenses that were in place for each infraction. Continue the causal analysis past the event root causes, to the deepest-seated causes that explain not only the one event, but many other issues. Because root causes are the common cause of many cause and effect sequences.
  3. Proactively strengthen defenses.
    Improving on James Reason’s barrier perspective, BlueDragon’s “Analysis of Defenses” ca be used proactively to examine how existing defenses are allowing repeat problems or events, so that those latent weaknesses can be eliminated, strengthening those defenses before more serious events take place.
  4. Instrument the process with analytics and analyze with Artificial Intelligence.
    Quantify CoPQ on an annual basis to identify the true cost of recurrence. Document and apply cause codes for every level of events, and use AI to trend and analyze the data to identify negative trends that can be acted on. Standardized cause codes improves learning and prevention.
  5. Adopt High Reliability Organization (HRO) habits.
    Build a mindfulness infrastructure—preoccupation with failure, reluctance to simplify, sensitivity to operations, commitment to resilience, deference to expertise—to keep weak signals from becoming crises. This requires a strong causal analysis and corrective action program that documents every class of incident that threatens operations, applies cause codes, trends and analyzes the data, and proactively investigates negative trends to strengthen defenses before the latent weaknesses allow a serious incident to take place.

Conclusion: Solve It Right the First Time

Playing “whack‑a‑mole” with symptoms will always feel busy—but it will never be enough. Ending recurrence requires a disciplined, evidence‑driven, human‑aware investigation process that hunts the deepest causes across systems and culture. That’s the standard BlueDragon was built to meet—find root causes in days (not months), fix what others miss, and prevent entire classes of incidents from returning.

 


Learn More & Take Action

About BlueDragon

BlueDragon was developed out of necessity in 2015 by Rob De La Espriella, a Root Cause Analysis Subject Matter Expert from the commercial nuclear power industry and the US Nuclear Regulatory Commission.

Share This Post:

Related Posts: