Wei didn’t have an answer, or at least not one that didn’t involve a deep, systemic failure of imagination. He sat there, his thumb tracing the edge of his phone, which he had just polished to a mirror shine for the fourth time that hour. The screen was so clean it felt like an invitation to a void, a stark contrast to the clutter of the IT ecosystem he was currently trying to resuscitate.

The problem wasn’t that the system had crashed. The problem was that the system had forgotten how to be paid for.

01

The Automation Paradox

Automation is the primary metric by which we judge the health of a modern corporation. But automation is often just a polite word for the systematic removal of human oversight-a process that works perfectly until the moment the human who wasn’t supposed to be there is finally gone-and yet we continue to treat every automated ‘success’ as a permanent victory.

The failed payment notice had been circling for days. It was an elegant little ghost, a digital wraith sent from a billing server in Northern Virginia to an inbox that no longer existed. Sarah, the former Director of Operations, had been the one to set up the subscription for the team’s primary project management suite back in 2021.

She used her corporate card, as one does, and she entered her email as the primary contact, as one does. When she left, her email was deactivated, her card was canceled, and the “set it and forget it” machinery of the SaaS world began its slow, inevitable march toward a cliff.

I spent years as a corporate trainer telling people that the “subscription economy” was the ultimate hedge against obsolescence. I would stand in front of rooms of tired middle managers and explain that by paying monthly, they were forcing the vendor to earn their business every single day.

I was wrong. I was profoundly, embarrassingly wrong. I ignored the fact that the vendor’s desire for fresh revenue creates a dependency that is inherently more fragile than the “obsolete” software of the past. I mistook a recurring bill for a recurring commitment to quality, when often it’s just a recurring point of failure.

Wei found the trail eventually. He had to dig through the logs of a dead SMTP server to see where the warnings were being sent. He saw the escalating tone of the automated emails: from “Action Required” to “Urgent: Payment Failed” to the final, cold “Service Suspended.” Each one was a flare fired into a dark, empty room.

The irony, of course, is that we do this to ourselves in the name of “agility.” We want to be able to scale up or down at a moment’s notice. We want to avoid the “heavy lift” of capital expenditure. But the cost of that agility is a hidden tax on our attention.

02

Digital Smudges and Perpetual Anchors

I think about my phone screen. I clean it because the smudges bother me; they distort the clarity of the information. They are small, physical reminders that the interface between me and the world requires effort to maintain. Corporate infrastructure is the same, but the smudges are digital. They are the names of people who don’t work there anymore. They are the expired cards.

This is particularly evident in the world of server management and remote access. You have a team of 42 people who need to get into the Windows Server environment to do their jobs. You set up the Remote Desktop Services, and then you face a choice. You can go down the path of recurring licenses that require constant “handshaking” with a billing server, or you can opt for the older, more stable path of perpetual licensing.

There is no credit card to expire. There is no automated email sent to a dead inbox. There is only the software, doing exactly what it was told to do, without asking for permission to continue existing every thirty days. There is a certain dignity in the perpetual. It acknowledges that the work we do today should not be contingent on our ability to navigate a billing portal tomorrow.

Wei eventually got the service back up. It took four hours of frantic phone calls, a temporary charge to his own personal card (which he’ll have to fight to get reimbursed), and a very awkward conversation with the CFO about why a dead woman’s credit card was still the linchpin of their operations.

The “convenience” of the subscription had cost them roughly $9,400 in lost productivity and about three years‘ worth of Wei’s sanity. We are living in an era of “phantom dependencies.” We rely on systems that rely on people who are no longer there.

We build workflows on top of “seamless” integrations that are actually held together by the digital equivalent of duct tape and prayers. The more we automate the mundane, the more we lose the muscle memory required to fix things when the mundane becomes catastrophic.

The lesson I try to impart now, when I’m not obsessively cleaning my screen or staring at failed payment logs, is that redundancy is about recognizing that the “invisibility” of a service is a warning sign, not a feature. If you don’t see it, you aren’t maintaining it. And if you aren’t maintaining it, it is already decaying.

The lemon drizzle cake has long since been digested, but the ghost of the woman who ate it still holds the keys to the server room.

We talk about “digital transformation” as if it’s a destination, a place where everything is smooth and automated. But the real transformation is the realization that the more complex our tools become, the more we need to anchor them in things that are simple, permanent, and physical.

Whether it’s a backup drive, a printed manual, or a perpetual license key, we need anchors. Without them, we are just drifting in a sea of subscriptions, waiting for the next card to expire, the next employee to leave, and the next invisible foundation to crumble.

Wei put his phone down. It was spotless. He looked at the server rack across the room, the little green lights blinking with a steady, rhythmic indifference. They didn’t care about Sarah. They didn’t care about the billing cycle. They just needed a reason to keep running.

And for today, at least, he had given them one. But he knew, as he reached for the microfiber cloth again, that the smudges always come back.