Radical Banality: The Missing Antidote to Modern Disinformation

If you watched Lost during its original run, you probably remember the online message boards dissecting every stray hieroglyph, background cable, and polar bear. Audiences assumed the showrunners had a pristine master plan locked inside an airtight vault. The reality was messy. The writers were improvising week to week, scrambling to deliver scripts before the production crew ran out of daylight in Oahu. Viewers took that creative panic and retrofitted it into intricate mythology, convinced that every production accident was secret genius.

On television, filling in narrative blanks is harmless leisure. In public life, that exact cognitive reflex turns dangerous.

Psychologists call the instinct to spot patterns in random noise apophenia. Combine that with intentionality bias our deep-seated refusal to accept that massive events happen by accident and you have the engine driving modern disinformation. Human brains despise an informational vacuum. When an organisation leaves a gap in a story, our minds treat the silence as an active threat and rush to finish the script.

I watched this play out during the worldwide CrowdStrike outage. A faulty configuration update crashed millions of Windows machines simultaneously, grounding flights and knocking banking terminals offline. The root cause was an ordinary software bug: a logic error in a routine sensor file. Yet in the hours before engineers could explain the mechanics of the crash, the silence became fertile ground for madness. Within sixty minutes, online platforms filled with theories of state-sponsored cyberwarfare, financial collapse drills, and engineered sabotage. People simply could not accept that global commerce could be halted by a stray piece of unvalidated code.

Today, generative AI supercharges this vulnerability. Large language models are, by definition, algorithmic apophenia engines. When you give an AI system an incomplete sequence, it cannot tolerate the empty space; its mathematical architecture forces it to predict the next plausible token. When anxious people paste fragmented news reports into chat interfaces and ask what is "really" happening, the software hallucinates connective tissue. It weaves random fragments into smooth, authoritative fiction, which then gets screenshotted and shared as proof.

Most organisations fight this with dry press releases and post-incident fact-checks. That approach fails because fact-checking only tells people what did not happen, leaving the underlying psychological plot hole untouched.

If you want to stop speculative narratives from taking root, you have to treat institutional communication as narrative architecture. That requires two practices almost nobody in corporate communications or incident management has deployed: Synthetic Narrative Stress-Testing and a Banality Protocol.

Right now, crisis communications teams rely on legal advisers and corporate spokespeople. Their reflex is always defensive brevity, issuing polished statements that reveal as little as possible. That corporate gloss makes the organisation look entirely in control, which paradoxically feeds public suspicion. When a seemingly omnipotent organisation suddenly claims an incident log is missing or a backup failed, nobody believes it was a mistake. It looks like an orchestrated cover-up.

To break that cycle, teams should use autonomous AI agents to stress-test their draft releases before public distribution. You prompt an adversarial agent to adopt the mindset of an online conspiracy theorist, instructing it to hunt down every unexplained gap in your timeline. Within seconds, the system flags the narrative vulnerabilities: "You omitted the thirty-minute window between the automated alert and the system restart. Speculative readers will infer that an unauthorised third party had hands on the console."

Once those vacuums are mapped, you activate the Banality Protocol. Instead of hiding the operational mess, you publish the unglamorous friction that actually caused the problem.

Conspiracies flourish when the public imagines an invisible mastermind directing events behind the scenes. Nothing kills that illusion faster than the tedious reality of administrative failure. If an automated backup failed during an incident, do not issue a stiff statement stating that telemetry was unavailable. Tell the public that an engineer accidentally let a digital certificate expire, or that a scheduled cron job stalled on an outdated operating system patch.

You destroy the mystique that feeds apophenia by replacing the missing plot point with boring, granular truth. People can project grand conspiracies onto silence, but nobody can build an ideology around an unread support ticket.