Sitemap

Case Study: OceanGate-Titan Analysis

18 min readJun 23, 2025

--

Press enter or click to view image in full size
This represents a triad of forces that co-create and shape each other in the organizational decision-making process. The triquetral piscis central structure represents Kurt Lewin’s Life Space, a concept within his Field Theory.

OCEANGATE NETFLIX: Verbatim comments/narrative highlights

“I felt like OceanGate had a maniacal safety culture. They had this rule of three. If three tiny things were wrong, or out of place, or not optimal, they cancel the dive. They had literally the leading expert on Titanic diving, P-H [Paul-Henri] Nargeolet, probably the greatest expert alive. I asked him over and over, “Nothing about this worries you?” He said, “No, of course not.” That also gave me a lot of reassurance.”

Captain Neubauer: “P-H’s involvement is always going to be a mystery to us. He was told in no uncertain terms that he was lending his credentials to something that had a clear and obvious flaw to it. His response was always the same. “I’m an old man, I’ve had a fantastic career. If I can help add safety to their operation, then that’s a win.””

Captain Neubauer: “How on Earth did Stockton get as far as he did? I will never understand that. It just became such a tight group of people who had such strong belief in what they thought they were doing, that it became almost cult-like.”

“If you can’t convince the people who believe in your mission that your vessel is safe, then there’s something deeply wrong with your company. Why do you listen to those concerns? Do you take them on board, do you make them part of the process of making this the safest vehicle that they all wanted? Or do you call them into the conference room and say, You’re fired?”

“In the end, they discounted the one system that was gonna be vital to their operations. It is, in my mind, the smoking gun of what eventually caused this.”

“It appeared that OceanGate felt comfortable, after the vessel was able to get to depth, that they had a proven concept that could just keep operating.”

The Influencer: “Later on I remembered they had the crane holding up the dome after everyone had passed away, and just remembered that my feet were literally on that dome just a few days before. [Weeping] And I was thinking, like damn, you know, like, what if that was me? Stupid. Tough. You know, it’s not really about me. I, you know, just feel bad for everyone else, of course. But, it’s tough. There’s a lot of what-ifs, but — you can’t live like that. You know? [Wiping tears.]”

Stockton Rush: “This is the future of the company. This is the path I have determined to take. I have no desire to die. I got a nice granddaughter. I am going to be around.”

Team Member: “The real mistake isn’t in the idea that something wasn’t classed, that we didn’t follow a set of regulations. That’s not really the mistake.”

Team Member: “Stockton came to identify himself with OceanGate, and he’s the guy that does this. He’s the guy who breaks through barriers to unlock the oceans to humanity. If you criticize any aspect of the operation, you’re criticizing him personally. It’s culture that caused this to happen. It’s culture that killed the people, 100%.”

Captain Neubauer said that had Stockton Rush lived, he could have been charged with Seaman’s Manslaughter. The statute is a specific provision in U.S. federal law that allows for criminal liability when a death occurs due to misconduct, negligence, or inattention to duties by individuals responsible for the operation or oversight of a vessel.

PERSONAL INSIGHTS AND COMMENTS:

Legal Citation: 18 U.S. Code § 1115Misconduct or neglect of ship officers

Under this statute, a captain, engineer, pilot, or other person employed on a vessel can be criminally charged with manslaughter if a person dies as a result of:

  • Misconduct
  • Negligence
  • Inattention to duties

This also applies to corporate officers or agents whose failure to enforce safety protocols or supervision results in a fatality.

I followed each person’s thoughts using my Agentic Structuration lens. Each individual had their own perspective and made their own decisions on what to do or not do.

Had Rush died alone in the Titan implosion, he would have been called a stupid adventurer, and there wouldn’t have been a Netflix special.

However, as it turned out, five people sacrificed their lives. It didn’t turn out like it did for Richard Branson or William Shatner. They also undertook high-risk ventures into extreme environments (space, in their cases), but their journeys were successful. Their “adventurer” status is celebrated, and their risk-taking is framed as pioneering and triumphant. The outcome dictates the label: pioneer vs. fool, hero vs. tragic figure, or criminal.

Stockton Rush was in a classic duality. This is the fundamental duality that almost everyone in a leadership position embodies. Still, it becomes acutely strained when the “Legal Entity (LLC)” (representing its roles, responsibilities, and legal obligations) clashes with the “Culture” (values, ethics, beliefs) and the “Free Will” (individual orientation, disposition, intentionality) of the “human being.” Rush said he didn’t intend to die or cause anyone’s death. However, he ruthlessly pursued the company’s interests, seemingly psychopathically, which isn’t as rare or unique as we might hope.

https://www.forbes.com/sites/jackmccullough/2019/12/09/the-psychopathic-ceo/

Corporations have no morals. Humans do — when they’re not role-playing the corporate CEO. The last quote above pretty much nails it for me. “It’s culture that caused this to happen. It’s culture that killed the people, 100%.”

While I disagree with that, I acknowledge culture as a contributing factor. This was a system collapse. Stockton Rush was the driver. He knew how the system worked; he worked it like many CEOs do and could capitalize on his scheme. Without Rush, the Titan disaster wouldn’t have happened. However, the pattern will likely be repeated in other places, as it isn’t against the law to be a psychopathic CEO. Nor is it illegal to follow them into their dreams and schemes, but people do die or collapse into ruin doing it.

Press enter or click to view image in full size
Image: The opening Venn Map “Agentic Organizational Structuration” converted into a standard management-type 3x3 Matrix format.

Cross-cell synthesis (how the map reads)

  • Relational × Culture → Governance gap: A safety “brand” coexisted with punitive relations toward dissent, nullifying the stated “rule of three.”
  • Situational × Legal → Assurance gap: Once-at-depth successes were tacitly reclassified as validation, replacing third-party class/independent testing with internal belief and credentials.
  • Disposition × Free Will → Identity capture: Founder and key experts’ identities fused with mission; critique became personal attack → error-intolerant culture.
  • Field dynamic (Lewin): The force toward mission completion outweighed counterforces (concerns, anomalies), thereby shrinking the life space for abort decisions.

Immediate diagnostic for a board or inquiry team

  1. Stop-work authority: Who could halt a dive unilaterally, and who last exercised that right? Produce the written delegation and the last three instances of actual use.
  2. Anomaly management: Show the trend log of “tiny things wrong” and the rule-of-three cancellations. If none, the policy was decorative.
  3. Independent assurance: Identify each dive-cycle’s independent checks (party, method, acceptance criteria). If reliance was on internal expertise or passenger experts, state why that met the duty of care.
  4. Retaliation climate: Provide records of adverse actions following safety objections in the prior 24 months.
  5. Risk Communication: Compare pre-dive informed-consent content with best-practice marine casualty advisories and assess comprehension checks.
  6. Decision gate design: Recreate the go/no-go gate with explicit thresholds. Where were thresholds relaxed after “success at depth”?
  7. Board oversight: Minutes documenting challenges to the founder's decisions on safety matters; any instances where the board overruled operations.
  8. Role conflation: Separate who owned technical authority on hull integrity (or the “vital system”) from who owned schedule, media, and client relations.

Bottom line

  • Legal Entity aspects: OceanGate’s LLC structure, regulations, safety certifications, all centered in the LLC leader.
  • The culture exhibited classic high-risk drift, characterized by credential-anchoring, group cohesion, and retaliation against dissent, eroding genuine safety. The company’s risk-taking culture, “move fast and break things” mentality
  • Individual free-will choices (choices made by Rush and passengers, founders, experts, and passengers) were shaped by identity, legacy, and social proof — constricting abortion options at the point of execution.

Each cell lists a) evidenced patterns from the verbatims, b) risk/mechanism, and c) lines of inquiry.

Press enter or click to view image in full size

Diagnostic Insights

Relational layer:

  • Formal structure (LLC roles, rules) claimed safety policies, but relational practices (retaliation, cult cohesion, credential-borrowing) inverted their effect.
  • Takeaway: Written policies without protection for dissent = hollow governance.

Situational layer:

  • Contextual realities (classification gap, anomaly signals, media schedule) consistently overruled by mission drive.
  • Takeaway: “Success once” reclassified into “safe enough” → classic normalization of deviance.

Individual layer:

  • Identity fusion (Rush = OceanGate) collapsed critique into attack, while P-H and others rationalized risk through personal calculus.
  • Takeaway: Dispositions amplified systemic blind spots; individuals rationalized away hazard salience.
  • Below is the fully populated 3×3 case-study grid for OceanGate — each cell contains: (1) verbatim-derived evidence, (2) concrete case example, (3) tensions, (4) possible synergies (where remediation could have existed), (5) explicit contradictions / red flags, and (6) direct diagnostic probes/evidence to collect. No fluff. Use it as a teaching capsule or as an investigative checklist.

Legend

Columns = Domains: A) Legal Entity (LLC) | B) Culture | C) Free Will
Rows = Force types: 1) Relational Properties | 2) Situational Factors | 3) Individual Orientation / Disposition

Row 1 — RELATIONAL PROPERTIES (roles, accountabilities, interdependence)

A1 — Legal Entity (LLC)

Verbatim evidence: “They had this rule of three. If three tiny things were wrong… they cancel the dive.” / “If you can’t convince the people who believe in your mission that your vessel is safe… Or do you call them into the conference room and say, You’re fired?” / Captain Neubauer: Stockton could have been charged with Seaman’s Manslaughter.
Concrete example: Formal stop-work rule existed in rhetoric; operational authority and retaliation practices suggest it was not enforceable.
Tension: Written delegation of stop-work vs. centralized leadership override and punitive HR actions.
Synergy (remediation point): Contractual stop-work authority vested in named, independent role (e.g., Safety Officer) enforceable by corporate charter.
Contradiction / red flag: Policy presence while disciplinary culture punished dissent — policy was decorative.
Diagnostic probes / evidence to collect: written stop-work policies, org chart delegations, HR termination records following safety objections, emails documenting attempts to halt dives, board minutes about safety authority, legal counsel memos on seaworthiness.

B1 — Culture

Verbatim evidence: “It just became such a tight group of people … almost cult-like.” / “Stockton came to identify himself with OceanGate … If you criticize any aspect of the operation, you’re criticizing him personally.”
Concrete example: Informal loyalty networks concentrated deference to founder; safety concerns suppressed socially.
Tension: Safety-as-brand narrative vs. social penalties for dissent.
Synergy: Peer accountability could have enforced safety if culture rewarded whistleblowing.
Contradiction / red flag: “Maniacal safety culture” claim vs. “cult-like” conformity — stated value ≠ behavior.
Diagnostic probes / evidence to collect: interviews mapping influence ties, records of reprimands/firings for safety objections, meeting minutes showing presence/absence of dissent, rewards/recognition criteria.

C1 — Free Will

Verbatim evidence: P-H to interviewer: “Nothing about this worries you?” — P-H: “No, of course not.” / Influencer: “what if that was me?” (post-event).
Concrete example: Passengers and credentialed experts publicly expressed reassurance; that reassurance influenced relational trust despite latent hazards.
Tension: Individual deference to expertise vs. personal responsibility to challenge.
Synergy: Empowered passengers/crew could act as extra safety layer if briefings included explicit stop-work rights.
Contradiction / red flag: Expert reassurance used as social proof, potentially masking unresolved technical concerns.
Diagnostic probes / evidence to collect: pre-dive briefings, signed informed-consent language, recordings/transcripts of pre-dive safety conversations, P-H’s internal correspondence about vessel safety.

Row 2 — SITUATIONAL FACTORS (context, time pressure, operational constraints)

A2 — Legal Entity (LLC)

Verbatim evidence: “In the end, they discounted the one system that was gonna be vital to their operations. It is, in my mind, the smoking gun…” / “It appeared that OceanGate felt comfortable, after the vessel was able to get to depth, that they had a proven concept…”
Concrete example: Company bypassed third-party classification/verification; internal judgments substituted for external assurance.
Tension: Regulatory/classification absence vs. reliance on internal test history.
Synergy: Independent classification could provide objective go/no-go criteria for varied situational pressures.
Contradiction / red flag: “Proven concept” after limited successful runs was treated as full validation.
Diagnostic probes / evidence to collect: inspection/test reports, third-party classification status, acceptance criteria for “proven concept,” deviation logs from test runs, QA test plans for the “one system” discounted.

B2 — Culture

Verbatim evidence: “They had literally the leading expert … I asked him over and over, ‘Nothing about this worries you?’ … That also gave me a lot of reassurance.” / “When the vessel was able to get to depth, they had a proven concept that could just keep operating.”
Concrete example: Operational cadence and public pressures (media, influencers) created incentives to continue diving despite anomalies.
Tension: Schedule/PR/investor pressure vs. safety-first rhetoric.
Synergy: A culture that prioritized learning from anomalies would resist schedule pressures.
Contradiction / red flag: Narrative of success turned into permission structure for continued risky operations.
Diagnostic probes / evidence to collect: voyage scheduling emails, investor/media commitments, social media contracts with influencers, logs showing anomaly handling and whether schedules were adjusted.

C2 — Free Will

Verbatim evidence: Stockton Rush: “This is the future of the company. This is the path I have determined to take. I have no desire to die.” / Influencer: post-event “what if that was me?”
Concrete example: Founder’s mission commitment and personal optimism bias influenced go/no-go choices in situationally risky contexts.
Tension: Personal mission/ambition vs. objective hazard indicators.
Synergy: Transparent commitment declarations paired with external constraints (e.g., independent abort authority) could contain founder bias.
Contradiction / red flag: Personal reassurance about survival (“I have a nice granddaughter”) used to dismiss objective concerns.
Diagnostic probes / evidence to collect: founder statements to staff/press, last-minute operational decisions and rationale, logs showing founder overrides, psychological autopsy of decision cascade.

Row 3 — INDIVIDUAL ORIENTATION / DISPOSITION (identity, motives, personal ethics)

A3 — Legal Entity (LLC)

Verbatim evidence: “Stockton came to identify himself with OceanGate, and he’s the guy that does this … If you criticize any aspect of the operation, you’re criticizing him personally.” / Captain Neubauer: prosecution possibility (Seaman’s Manslaughter).
Concrete example: Founder’s identity fused with company governance; personal accountability lines blurred.
Tension: Founder-centric leadership vs. corporate fiduciary duties and legal accountability.
Synergy: Clear separation of technical authority and corporate leadership (chartered safety officer, independent board oversight) would mitigate identity capture.
Contradiction / red flag: Leader fusion reduces effective oversight and increases legal exposure.
Diagnostic probes / evidence to collect: corporate governance documents, role definitions, separation of powers, evidence of board challenges to operational decisions, insurance and liability communications.

B3 — Culture

Verbatim evidence: “It’s culture that caused this. It’s culture that killed the people, 100%.” / “maniacal safety culture” claim juxtaposed with punitive responses to critics.
Concrete example: A culture of heroism/innovation replaced procedural skepticism; safety became rhetorical rather than structural.
Tension: Pride-driven innovation culture vs. systemic safety practices that require dissent and skepticism.
Synergy: Cultural humility, rituals of dissent, and psychological safety would preserve creative drive while exposing hazards.
Contradiction / red flag: Cultural valorization of risk-making substituted for formal engineering rigor.
Diagnostic probes / evidence to collect: cultural artifacts (onboarding materials, slogans), promotion criteria, narratives rewarded publicly, whistleblower reports.

C3 — Free Will

Verbatim evidence: P-H: “I’m an old man, I’ve had a fantastic career. If I can help add safety to their operation, then that’s a win.” / Influencer’s weeping: post-event rationalization.
Concrete example: Individual motivations (legacy, access, status) shaped choices overriding prudential self-protection or robust challenge.
Tension: Personal legacy and access incentives vs. impartial safety judgment.
Synergy: Explicit personal-interest disclosure and refusal rights before dives could reduce conflicts of interest.
Contradiction / red flag: Experts’ willingness to lend credentials for legacy/assistance conflates endorsement with oversight.
Diagnostic probes / evidence to collect: conflict-of-interest disclosures, expert advisory agreements, records of what P-H was told re: vessel condition, testimonies about why experts did not insist on additional checks.

Cross-cell teaching points (short)

  • Policy without enforceability (A1, B1): Presence of a rule is meaningless if social reprisals render it unusable.
  • Validation bias (A2, B2): Repeated success in narrow conditions was misread as comprehensive safety.
  • Identity capture (A3, B3, C3): When leader identity fuses with the enterprise, governance and prudence collapse.
  • Expert endorsement vs. independent assurance (C1, C3, A2): Credentialing can be social proof, not technical verification.

Immediate evidence checklist (actionable)

  1. Stop-work & escalation artifacts: policies, last uses, deviations.
  2. Anomaly logs & rule-of-three records: list of incidents labeled “tiny” and actions taken.
  3. Independent verification: classification status, test protocols, lab reports for the “vital system.”
  4. Governance separation: board minutes, charters, role descriptions, decision overrides.
  5. Cultural evidence: HR records, reprimands, promotion criteria, marketing vs. operational practice contrasts.
  6. Informed consent & briefings: passenger materials and comprehension checks.
  7. Expert contracts & disclosures: what experts were told, compensated, or asked to sign.
  8. Schedule/PR pressure: contracts with influencers, investor deliverables, public statements.
  9. Communications trail: emails, Slack, SMS around last 48 hours pre-dive.

If you want, I will now convert each of the nine cells into a 3–5 question interview module (for board members, engineers, crew, or witnesses), or produce a one-page incident-review checklist that maps each diagnostic probe to likely documentary locations (email, minutes, personnel records, technical logs). Which of those next steps do you want — interview modules or the one-page checklist?

Teaching leverage

  • Each cell = a teachable paradox: “What was written vs. what was enacted vs. how people rationalized it.”
  • As a diagnostic tool: teams can fill each cell with their own tensions, synergies, contradictions to surface hidden organizational drift.

Teaching/Diagnostic Use

  • Tensions = friction points where two forces pull in opposite directions (e.g., written rules vs. enacted punishments).
  • Synergies = potential leverage points (e.g., shared values → collective vigilance).
  • Contradictions = red flags where the system says one thing and does another (e.g., “maniacal safety culture” alongside firing dissenters).

Example Diagnostic Prompts (OceanGate case, but generalizable):

  • Relational × Legal Entity: Did written accountabilities (e.g., stop-work authority) actually survive organizational retaliation?
  • Situational × Culture: How were early anomalies reframed? As weak signals to learn from, or as evidence of resilience?
  • Disposition × Free Will: Did personal identity investments (legacy, thrill-seeking, founder ego) reduce the cognitive space for abort decisions?

This grid works as:

  1. Case teaching tool (show how each domain-force produces different pathologies or opportunities).
  2. Diagnostic checklist (ask: where are our tensions, synergies, contradictions?).
  3. Comparative framework (apply across industries — aviation, energy, healthcare — for systemic accident analysis).

OceanGate-Titan: Trivalent Safety Domain Analysis

A) SOCIOLOGICAL SAFETY

Risks/violations: Structural relations, norms, legitimacy, belonging, collective meaning

Violations:

Structural Accountability Collapse

  • Evidence: Founder-CEO role fusion eliminated independent oversight; board failed to challenge operational decisions
  • Mechanism: When Rush’s personal identity merged with corporate governance (A3), it severed the relational separation required for fiduciary accountability
  • Result: No legitimate authority could halt operations without attacking Rush personally

Normalization of Deviance as Cultural Norm

  • Evidence: “After the vessel was able to get to depth, they had a proven concept that could just keep operating”
  • Mechanism: Group redefined success criteria collectively; each successful dive became social proof that risks were acceptable
  • Result: Institutional memory of anomalies was collectively suppressed

Retaliation Climate / Exclusion of Dissent

  • Evidence: “Do you take them on board… or do you call them into the conference room and say, You’re fired?”
  • Mechanism: Social punishment (termination, ostracism) for safety concerns; belonging required loyalty over prudence
  • Result: Sociological exclusion of those who threatened group cohesion

Credential Borrowing / False Legitimation

  • Evidence: P-H’s involvement “lending his credentials to something that had a clear and obvious flaw”
  • Mechanism: Expert status used for social legitimacy rather than technical verification; passengers relied on collective social proof (“he’s not worried, so I’m not worried”)
  • Result: Sociological authority substituted for technical assurance

Cult Dynamics / Identity Fusion

  • Evidence: “It just became such a tight group of people… almost cult-like”
  • Mechanism: Collective identity fused with mission; questioning operations = betraying the group
  • Result: Social coherence maintained through conformity, not through safety

Power Asymmetry / Hierarchical Silencing

  • Evidence: Captain Neubauer warned P-H “in no uncertain terms” but was overridden
  • Mechanism: Organizational hierarchy prevented horizontal safety dialogue; lower-status members couldn’t challenge elite decision-making
  • Result: Structural inequality prevented safety information from flowing upward

Sociological Safety Failure Summary:

The social structure eliminated the possibility of collective course-correction. Relations were organized around loyalty and identity rather than accountability and dissent. The group became a closed system that could not incorporate external feedback.

B) PHYSIOLOGICAL SAFETY

Risks/violations: Material hazards, bodily harm, environmental exposure, physical systems

Violations:

Material System Failure (Hull Integrity)

  • Evidence: “They discounted the one system that was gonna be vital to their operations… the smoking gun”
  • Mechanism: Carbon fiber hull subjected to cyclic pressure loading without adequate monitoring; material fatigue not tracked
  • Result: Catastrophic implosion at depth

Absence of Classification / Third-Party Verification

  • Evidence: Company bypassed external classification (Lloyd’s, DNV, ABS)
  • Mechanism: No independent material testing or structural validation by certified marine engineers
  • Result: Unverified design operated in extreme environment

Environmental Hazard Exposure (Depth Pressure)

  • Evidence: Operations at ~4,000m depth (400 bar / 5,800 psi external pressure)
  • Mechanism: Human bodies and vessel subjected to crushing force; any breach = instant death
  • Result: Extreme physical hazard with zero margin for error

Life Support System Dependency

  • Evidence: Closed environment; oxygen limited; no escape mechanism
  • Mechanism: Physiological survival entirely dependent on vessel integrity and life support
  • Result: Single point of failure = total loss

Ergonomic / Operational Hazards

  • Evidence: Bolted from outside; no internal release; single-viewport design
  • Mechanism: Physical design prevented emergency egress; occupants trapped if systems failed
  • Result: No physiological escape route

Medical Risk (No Emergency Response Capability)

  • Evidence: Operating in remote location; no rescue capability at depth
  • Mechanism: If medical emergency occurred (heart attack, injury), no physiological intervention possible
  • Result: Any health crisis = death

Physiological Safety Failure Summary:

The material system (hull) was inadequately tested and monitored. The physical environment (depth pressure) was unforgiving. The bodily safety of occupants depended entirely on unverified engineering in an extreme hazard zone with no rescue capability.

C) PSYCHOLOGICAL SAFETY

Risks/violations: Cognitive security, emotional stability, trust, voice, fear of sanction

Violations:

Absence of Voice / Fear of Retaliation

  • Evidence: Engineers and crew fired for raising concerns; “If you criticize any aspect of the operation, you’re criticizing him personally”
  • Mechanism: Psychological threat of job loss, exclusion, or personal attack prevented honest expression
  • Result: Individuals suppressed safety concerns to protect psychological security (employment, status)

Cognitive Dissonance / Rationalization

  • Evidence: P-H: “I’m an old man… If I can help add safety to their operation, that’s a win” (despite knowing the flaws)
  • Mechanism: Experts resolved mental conflict between technical concerns and personal commitments through rationalization
  • Result: Cognitive distortion allowed continued participation despite recognized hazards

Optimism Bias / Illusory Control

  • Evidence: Stockton Rush: “I have no desire to die. I got a nice granddaughter. I am going to be around.”
  • Mechanism: Founder’s psychological investment in success created belief he could control uncontrollable risks
  • Result: Mental model diverged from material reality

Groupthink / Conformity Pressure

  • Evidence: “Tight group… cult-like”; dissent seen as disloyalty
  • Mechanism: Psychological conformity to group consensus; individual doubt suppressed to maintain belonging
  • Result: Collective blind spots; no one willing to be the “weak link” who questions

Credential-Anchoring / Authority Bias

  • Evidence: Passengers reassured by P-H’s involvement: “That gave me a lot of reassurance”
  • Mechanism: Psychological reliance on expert authority as heuristic for safety; mental shortcut replaced independent evaluation
  • Result: Passengers’ risk perception shaped by social proof rather than technical analysis

Emotional Investment / Sunk Cost Fallacy

  • Evidence: Years of development, media attention, financial investment
  • Mechanism: Psychological commitment to mission made abandonment emotionally intolerable
  • Result: Escalation of commitment despite mounting evidence of risk

Post-Trauma Rationalization

  • Evidence: Influencer: “You can’t live like that” (dismissing “what-ifs”)
  • Mechanism: Survivors’ psychological need to reduce dissonance by minimizing the near-miss
  • Result: Cognitive closure prevented learning from close calls

Identity Threat (Rush)

  • Evidence: Criticism of operations = personal attack on Rush’s identity
  • Mechanism: Rush’s self-concept fused with OceanGate’s success; threats to the company = threats to self
  • Result: Psychological defensiveness prevented incorporation of feedback

Psychological Safety Failure Summary:

Individuals could not voice concerns without fear of retaliation. Cognitive biases (optimism, authority, sunk cost) distorted mental models of risk. Emotional investments and identity fusion created psychological barriers to abort decisions.

Cross-Domain Synthesis: How the Three Interact

Press enter or click to view image in full size
DomainPrimary Failure ModeHow It ropagated to Other DomainsSociologicalRetaliation climate; cult dynamics; credential borrowing→ Psychological: Suppressed voice, conformity pressure<br>→ Physiological: Prevented independent material verificationPsychologicalOptimism bias; identity fusion; cognitive dissonance→ Sociological: Reinforced group cohesion around flawed beliefs<br>→ Physiological: Rationalized away material warning signsPhysiologicalUnverified hull; extreme environment; no rescue→ Psychological: Created cognitive dissonance (experts knew risk but continued)<br>→ Sociological: Forced collective denial to maintain operations

Borromean Structure: The Collapse

The three domains were mutually sustaining:

  • Sociological safety (group cohesion) depended on psychological safety (no dissent) which required ignoring physiological hazards (material flaws)
  • When psychological safety collapsed for some (engineers who spoke up), they were sociologically excluded (fired), which prevented physiological safety improvements (no design changes)
  • Physiological success (early dives) created psychological confidence (optimism bias) which reinforced sociological norms (keep going)

When the hull failed (physiological collapse), all three domains collapsed simultaneously:

  • Physiological: Instant death
  • Psychological: Survivors’ trauma, public shock, cognitive reckoning
  • Sociological: OceanGate’s dissolution, regulatory scrutiny, cultural reckoning in industry

Summary Table: Violations by Domain

Press enter or click to view image in full size
Safety DomainKey ViolationsEvidence SignatureSociological• Retaliation climate<br>• Credential borrowing<br>• Cult dynamics<br>• Power asymmetry<br>• Normalization of deviance"Cult-like," firing dissenters, P-H's credentials used for legitimacy, "rule of three" not enforcedPhysiological• Unverified hull design<br>• No classification<br>• Extreme environment<br>• No escape/rescue<br>• Single point of failure"Discounted the one vital system," no third-party testing, 4000m depth, bolted from outsidePsychological• Fear of retaliation<br>• Optimism bias<br>• Groupthink<br>• Authority bias<br>• Identity fusion<br>• Sunk cost fallacy"Criticize = personal attack," "no desire to die," "cult-like," P-H reassurance, "maniacal safety culture" claim vs. behavioField Dynamic (Lewinian): How Violation Domains Interacted

The safety ecosystem collapsed because:

  1. Sociological violations (firing dissenters) eliminated psychological safety (voice)
  2. Psychological violations (optimism bias, identity fusion) prevented recognition of physiological violations (material flaws)
  3. Physiological violations (unverified design) were sociologically rationalized (“proven concept”) and psychologically minimized (expert reassurance)

Result: The force toward mission completion overwhelmed all three safety domains simultaneously, shrinking the life space for abort decisions to zero.

This trivalent analysis reveals what single-domain frameworks miss: OceanGate wasn’t just a technical failure, or just a cultural failure, or just a leadership failure — it was a system collapse across all three ontological domains of safety, with each domain’s violations reinforcing and enabling the others.

Press enter or click to view image in full size

--

--

Rob Jones
Rob Jones

Written by Rob Jones

A career spanning public, private, and nonprofit sectors. High-level management experience across a range of activities in F-500 companies and Consulting/Coach.