Cassandra Syndrome
Accurate warnings dismissed until catastrophe proves them — too late to act cheaply
Unwelcome evidence at honest tier must reach a commitment boundary before consequences compound — not after disaster validates the bearer.
Cassandra was cursed to speak true prophecies no one would believe. Organisations reproduce the myth without the supernatural: an engineer, analyst, or front-line operator states an accurate warning — safety margin gone, fraud pattern visible, architecture will not scale — and the room discounts it until the failure arrives. Afterward the same content is treated as obvious. The truth did not change. Believability changed — usually when the cost of denial exceeded the cost of admission.
Cassandra syndrome is a failure of reception, not of prediction. The warning often lacked polish, came from the wrong status band, or threatened a narrative the leadership had already committed to. Homophily and heterophobia explain why the bearer was the wrong kind of person to listen to; epistemic tier collapse explains why the content was read as opinion rather than supported claim.
In software systems
Alerts fire repeatedly below threshold until an outage forces a Sev-1. Security findings from internal red-team “troublemakers” sit in backlog while vendor scan scores drive budget. The on-call who has seen this failure mode before is overridden by the architect who has not — homophilous trust in title over track record. Logs contained the warning; no commitment event recorded that anyone acted on it at honest tier.
In human organisations
Risk functions are consulted after the decision. Internal audit reports circulate without escalation path. The person who “cries wolf” — because wolves keep arriving — is categorised as negative rather than calibrated. Post-mortems quote their Slack messages with forensic admiration. Authority weight followed presentation and affiliation, not accuracy history.
In socio-technical systems
Model drift warnings, clinician overrides, and regulator letters can all play Cassandra — accurate signals embedded in systems that route attention homophilously (only surfaced if the right role affirms them). Without tier and lineage on warnings, dashboards show green until red is undeniable.
Structural causes
Homophilic closure
When organisations only grant uptake to warnings from familiar roles, Cassandras are structurally produced. Fix: named escalation paths, immutable warning records at stated tier, and commitment events when warnings are accepted or explicitly overridden with authority — not silent dismissal.
Homophily / heterophobia
Reception bias against unlike bearers turns accurate tier-2+ claims into background noise until disaster upgrades them to “obvious.” Judgment infrastructure must separate messenger from message — record tier on the claim, track who dismissed it and on what basis.