In the echo of the atom bomb, emerged a slow drip drip drip.
The terror of the bomb inspired many fears. One tiny concern at the time was the worry of data loss. Early networks had a singular priority. They had to survive a nuclear assault. Engineers built a literal bomb-proof system to protect data at all costs.
In an environment focused entirely on survival, no one considered removal.
As new digital tools arrived, access expanded and data creation exploded. Systems multiplied. The businesses behind them grew rapidly. Customer numbers surged. Governments adopted the applications. Soon, almost everyone was using, attached to, or identified by a data system.
The drip became a torrent. The problem of removal remained ignored. This permanent accumulation continues today. It weakens our systems across four core areas.
1. The User: Psychological Exhaustion
Over decades, individuals signed up to these new digital systems. We opened email accounts and speculative crypto wallets with excitement. Then we slowly abandoned them.
Alongside this mechanical residue of usernames and passwords sits our emotive litter. We leave behind snap reactions, discarded points of view, and regretful comments. These freeze our past personalities in time. Under risk of extraction and extortion.
Human relationships need endings to establish healthy boundaries. Digital systems stripped those boundaries away. Apps keep minds locked in unresolved loops, driving adolescent anxiety without a closing bell. The invisible machinery of ad tech worsens the damage. You close a browser tab, but your identity lives on in real-time auctions beyond your control. Joining takes one click. Leaving requires navigating dark patterns and retention traps. Consumers drag an invisible, permanent trail behind them.
2. The Product: Cluttered Features and Dead Hardware
Established software companies find it hard to kill old features. Mature products carry layers of half-abandoned tools. The industry has an extraordinary ability to start new things, but zero vocabulary to end them. Products become bloated and brittle because nobody has the mandate to decommission obsolete code. Meanwhile, connected hardware sits pristine on your shelf. Then a company remotely cuts off an API. A functional device turns into an expensive, unfixable doorstop overnight.
3. The Business: Lost Vocabulary and Servers in Purgatory
Within tech companies, the absence of endings is an operational disaster. Corporate language focuses entirely on onboarding, acquisition, and retention. Teams have dozens of terms for bringing customers in. They have almost no professional words to close a relationship or let customers go with dignity.
Without an ending vocabulary, forgotten cloud storage and unindexed data lakes sit in purgatory. Businesses burn millions babysitting old data just to avoid compliance fines. Companies also find themselves trapped in long-term enterprise contracts, paying ongoing fees for software nobody uses because exiting is too complex.
AI will only accelerate this mess. It will add another dense layer to tangled in-house data, creating systems that linger indefinitely and resist any attempt to sunset them.
4. The State: The Loss of Digital Sovereignty
Historically, nations asserted authority through physical borders. Today, three foreign hyperscalers dominate the digital infrastructure of entire continents. Private satellite constellations beam data from the sky, bypassing national borders altogether.
In the rush to digitise, countries handed over access to their citizens for free. Passports worked well at physical checkpoints. For online access, governments allowed international tech giants to become the de facto identity brokers. This created a permanent privacy liability for citizens.
Public sectors even pay these platforms through public procurement, funding tools that harm the mental health of their own populations. When nations try to set boundaries, foreign tech lobbies and trade threats quickly bully them into silence.
Designing the Exit
We built a digital civilisation that is skilled at saying hello, but incapable of saying goodbye.
An ending is a required stage of system design. We have enough frictionless signups and endless feeds. We need to recover the lost discipline of Endineering and learn how to design the end.
