The Ancient Ritual That Makes Your Backup Plan Look Primitive
Ancient Assyrian kings used a substitute to absorb crisis damage; modern leaders should pre-designate sacrificial assets to survive existential threats.
This article examines the ancient Assyrian *šar pūhi* ritual, where a substitute king was crowned to absorb lethal omens, then executed to protect the real monarch. The author argues this represents sophisticated crisis engineering, not superstition, and applies the lesson to modern business: organizations should pre-authorize a non-essential asset to fail first, creating a controlled sacrificial layer that absorbs regulatory fines, reputational damage, or financial shocks while the core operation survives. The key insight is that plans attempting to preserve everything cannot make the hard tradeoffs real crises demand.
The Assyrians didn't have two kings; they had one king and one human lightning rod. That distinction is the entire difference between superstition and engineering. In 672 BCE, Esarhaddon of Assyria faced a string of unfavorable omens. His court enacted the šar pūhi — the substitute king ritual. A commoner was crowned, placed in the royal bed, and when the omens turned lethal, that man was put to death. The real king emerged from hiding, his reign untouched. This was not primitive superstition. It was a deliberate sacrificial layer: a pre-built component designed to absorb the first and worst hit of a crisis. The real king was not hiding. He was betting a controlled loss against total ruin. Modern crisis playbooks aim to preserve everything. Insurance, remote work, redundant systems — all assume we can keep the whole intact. But when the threat is existential — a catastrophic financial event, a regulatory hammer, a reputational implosion — that assumption becomes the vulnerability. A plan that tries to save every asset cannot make the hard tradeoffs that real crises demand. The substitute king principle recommends the opposite: identify one non-essential asset — a satellite office, a marginal product line, a secondary process — and pre-authorize it to fail first. That sacrificial layer becomes your bullet-catcher. It absorbs the regulatory fine, the class-action blow, the reputational fire. Meanwhile, your core operation buys time to stabilize or adapt. The hard part is choosing. Most risk officers resist the idea of designating something to lose. But the ritual shows that the alternative is worse: random failure on the part of the system most critical to recovery. A sacrificial layer is a decoy you control — and that control is precisely what makes it valuable. Design your fallback plan around one controlled surrender. Everything else follows.