On February 24, 1966, Ghana's first president Kwame Nkrumah was on a plane to Vietnam when military officers staged a coup back home. By the time he landed, he'd lost his country. The founding father of Ghanaian independence—the man who'd led the nation from British colonialism to sovereignty—discovered he'd been removed from power while literally in the air, unreachable and unable to respond.
It's a stark reminder that being indispensable makes you a single point of failure. Nkrumah had centralized so much authority that the entire system became brittle. Sound familiar? We see this pattern constantly in tech: the brilliant founder who won't delegate, the "10x engineer" whose code only they understand, the CEO who insists on approving every decision. When that person is unavailable—whether they're on a plane to Hanoi or just burned out—the whole organization freezes or fractures.
The best systems are resilient because they're designed to function without any single person. That means documentation that actually gets maintained. Knowledge-sharing that's baked into your culture, not bolted on during someone's last week. Leadership pipelines that develop people before you desperately need them. Nkrumah's mistake wasn't taking that trip to Vietnam—it was building a government that couldn't function without him for a single day. Whether you're running a nation or shipping code, ask yourself: if you were unreachable tomorrow, would your system survive? If the answer is no, you're not building something sustainable—you're building a house of cards.