Cautionary Tales with Tim Harford
Cautionary Tales with Tim Harford

DOUBLE BILL: When a Plague Struck World of Warcraft/Blood on the Tracks

As a special New Year treat we're presenting two Cautionary Tales Shorts - which have previously only been available to paying Apple and Pushkin+ subscribers. When a Plague Struck World of Warcraft: The makers of WoW wanted to spice up the fantasy computer game by introducing a virtual disease

Featured Speakers

Tim Harford Guest

Topics Discussed

Episode Summary

Executive Summary: Tim Harford tells two cautionary tales: World of Warcraft's 2005 "Corrupted Blood" outbreak, a virtual pandemic spread by unintended code interactions and player behavior, and the 1915 Quintinshill rail disaster, where routine rule-bending, poor procedures, and human error caused a catastrophic troop-train collision. Both illustrate how systems fail when real behavior diverges from designed assumptions.

Main Topics: World of Warcraft's virtual pandemic (Priority: 5/5): A game mechanic meant to stay confined to one dungeon escaped into populated cities, creating an in-game epidemic that spread rapidly and unpredictably. Unexpected insights for epidemiology (Priority: 4/5): Researchers saw the virtual outbreak as a possible model for studying disease spread, altruism, misinformation, and compliance, though the data proved limited. Work as imagined vs. work as done (Priority: 5/5): The Quintinshill disaster shows how formal rules differed from real railway practice, including delayed shift changes and ignored safety procedures. Cascading human and system failures (Priority: 5/5): A series of small deviations—logbook manipulation, skipped checks, casual communication, and outdated rolling stock—combined into a mass-casualty disaster. Accountability and blame (Priority: 4/5): The court blamed the signalmen, but the episode argues that management rules and organizational culture also contributed to the failure. Why cautionary tales matter (Priority: 3/5): Harford frames both stories as instructive examples of how hidden assumptions, complexity, and routine shortcuts can produce catastrophic outcomes.

Key Arguments: Complex systems can fail when designers assume behavior that users or workers do not actually follow. In World of Warcraft, a bug intended for a confined boss fight escaped through pets and teleportation, turning a local hazard into a server-wide pandemic. The virtual outbreak showed behaviors relevant to real epidemics: flight, altruism, misinformation, and reckless spreaders. However, the game was not a perfect epidemiological model because it differed from real disease dynamics and Blizzard did not share enough data. At Quintinshill, the disaster arose from a gap between formal rules and actual railway practice, especially informal shift changes and skipped safety rituals. Safety systems depend on honest reporting and adaptable rules; when workers must hide normal practice, latent danger grows. Blaming front-line workers alone misses the role of unrealistic procedures and poor organizational design. Small, mundane errors can combine into catastrophic failure when safeguards are weak and communication is imperfect.

Data Points: Year of WoW outbreak: 2005 - Corrupted Blood spread after the Zulgurub update Spread rate: doubled every 9 minutes - Rate at which infected World of Warcraft characters multiplied Early COVID doubling time: every 2 or 3 days - Harford compares in-game spread to real pandemic growth Warcraft server structure: a few thousand players per server - Outbreaks happened on parallel game servers Quintinshill troop train passengers: 500 men - 1st Battalion of the 7th Royal Scots traveling to Gallipoli Troop train casualties: 214 soldiers - Royal Scots lost in the Quintinshill crash Bodies identified: 83 - Only this many troop-train bodies could ever be identified Railway staff deaths: 3 - Rail staff who died at Quintinshill Other train passenger deaths: 9 - Passengers from the local train and express Sentence for signalmen: 1 year in prison - George Meekin and James Tinsley were convicted of culpable homicide Time of shift handover: 6:00 a.m. vs about 6:30 a.m. - Rule required six o'clock; practice was often later Date of Quintinshill disaster: May 22, 1915 - The troop train collision occurred near Kirkpatrick Date of World of Warcraft outbreak: September 13, 2005 - The Corrupted Blood incident began

Pivotal Quotes: "The nightmare of Hakar the Soul Flayer was not going to be confined to Zul Ghurub." — Tim Harford: Introduces the in-game outbreak and its unintended spread "The number of characters infected with corrupted blood doubled every nine minutes." — Tim Harford: Highlights the explosive pace of the virtual pandemic "It’s always easy to find fault with workers done. But workers imagined had played its part too." — Tim Harford: Summarizes the lesson from Quintinshill about system design and blame

Implications: Both stories warn that hidden assumptions, weak safeguards, and normalized rule-bending can turn minor flaws into disasters. For health, tech, and transport industries, the lesson is to study real behavior, not just written procedures.

🔓 Sign Up for Unlimited Episode Search

About Cautionary Tales with Tim Harford

View all episodes from Cautionary Tales with Tim Harford