Nudging the cursor toward the 16th ‘Confirm’ button of the morning, I feel a strange, hollow twitch in my wrist-the physical manifestation of a digital soul-rot. I am currently trying to approve a $56 expense report for a lunch that happened 26 days ago. The software I am using cost this firm roughly $2,000,006 to implement, including the 66 months of ‘onboarding’ that seemed to mostly involve consultants in expensive vests explaining why our existing workflow was ‘legacy.’ My pulse is currently sitting at 96 beats per minute because I just hung up on my boss accidentally. It wasn’t an act of rebellion. It was the new unified communications suite. The ‘End Call’ button moved 26 pixels to the left during a background update that I didn’t authorize. Now, I am sitting in the silence of my home office, staring at a progress bar that has been stuck at 46 percent for the last 6 minutes, wondering how we convinced ourselves that this was progress.

Trading Simplicity for Labyrinths

There is a specific kind of nostalgia that hits you when you realize you are working for the machine rather than the machine working for you. I remember, with a longing that feels almost physical, the old paper forms we used to use. You could sign them in 6 seconds. You could drop them in a physical tray. There was a tactile satisfaction in the completion of the task. Now, completion is a nebulous concept defined by whether or not the API successfully handshakes with the cloud-based accounting module. We have traded the simplicity of a signature for a labyrinth of permissions, roles, and ‘automated’ workflows that require more manual oversight than a Victorian textile mill. We are living in an era where we have successfully automated the old stupidity, making it move at the speed of light without ever questioning why we were doing it in the first place.

“

The greatest trick the tech industry ever pulled was convincing us that friction and complexity were the same thing as sophistication.

Ruby spends her days helping people untangle their lives from the mess of ‘fintech’ solutions that promise to save them money while charging $26 a month in hidden subscription fees. She recently worked with a client who had purchased $86,000 worth of enterprise resource planning software to manage a team of 46 people. The client was convinced that the software would solve their ‘communication issues.’ It didn’t. It just gave them 66 new ways to ignore each other. Ruby’s perspective is colored by the realization that we often use software as a shield to avoid the messy, uncomfortable work of human interaction. If the system is broken, we can blame the vendor. If the process is opaque, we can blame the ‘user interface.’ It’s a $2,000,006 insurance policy against accountability.

The Illusion of Efficiency

I find myself digressing into the history of our ‘Efficiency Drive’ of 2006. Back then, we thought the problem was the lack of data. We believed that if we could just see every movement of every dollar in real-time, the waste would evaporate. We were wrong. We didn’t need more data; we needed better judgment. But judgment is hard to scale. Judgment requires experience, intuition, and the ability to say ‘no’ to a bad idea. Software, on the other hand, is infinitely scalable. You can deploy a bad idea to 456 employees with the click of a mouse. You can enforce a nonsensical policy across 6 continents overnight. We have created systems that are perfectly optimized for a world that doesn’t exist-a world where every human interaction can be quantified, categorized, and resolved through a ticket-based system.

The real problem isn’t the code. The code is usually fine, if a bit bloated. The problem is that we treat software like a magic wand that can fix a culture of distrust. If you don’t trust your employees to buy a $56 lunch without 16 levels of digital approval, no amount of SaaS is going to save your company. You don’t have a tech problem; you have a trust problem. The software just makes that lack of trust more visible and more expensive. It crystallizes the dysfunction into a permanent, unchangeable architecture. Once you’ve spent $1,000,006 on a system, you can’t exactly admit that the logic behind it is fundamentally flawed. You’re stuck with it. You’re stuck with the 26-step approval process because that’s what the ‘Best Practices’ manual said you should do.

The Craft of Tools

I think about the craftsmanship involved in things that actually work. There is a reason why a well-made tool feels right in the hand. It doesn’t ask for your attention; it facilitates your intention. In a world of flickering screens and ‘smart’ features that make us feel stupid, there is something profoundly grounding about a process that has been refined over generations. It’s like the difference between a mass-produced, chemically-aged spirit and the deep, complex notes you find in Weller 12 Years, where the process is the point. You can’t automate the aging of a fine scotch. You can’t ‘disrupt’ the interaction between the wood and the liquid. It takes time. It takes a specific, human understanding of the environment. Our modern corporate environment has lost that sense of timing. We want the result without the process, so we buy the software and hope for a miracle.

Mistaking the Map for the Territory

We are currently in a cycle of digital avoidance. We buy tools to avoid having the difficult conversation about why our strategy is failing. We implement new platforms to avoid admitting that our communication is toxic. I remember a project back in 2016 where we spent 366 days implementing a ‘collaboration’ tool. We had 126 meetings about the tool. We hired 6 external consultants to train us on the tool. And at the end of that year, we were collaborating less than ever because we were all too busy managing our notifications and updating our status bars. We had mistaken the map for the territory. We thought the tool was the collaboration. It wasn’t. Collaboration is what happens when two people trust each other enough to share an unfinished idea. No software can force that into existence.

The True Cost of Status

Ruby J.-P. often points out that true financial literacy starts with realizing that the most expensive solution is rarely the best one. She told me about a non-profit that was struggling to manage their 46 volunteers. They were looking at a $16,000-a-year database solution. Ruby looked at their needs and told them they needed a whiteboard and a box of markers. They were furious. They wanted the status of the expensive software. They wanted to feel like they were part of the ‘Digital Transformation.’ They eventually bought the software. Six months later, they were 26 weeks behind on their reporting because no one could figure out how to log in. The whiteboard would have worked on day one. But the whiteboard doesn’t have a ‘Revolutionary’ marketing budget behind it.

“

We have traded the simplicity of a signature for a labyrinth of permissions.

The Chaos Reflected

My boss just messaged me. He’s asking why I hung up on him 26 minutes ago. I could tell him the truth-that the UI is a nightmare and the buttons are too small and I’m tired of being a cog in a $2,000,006 machine. But instead, I’ll probably just blame my internet connection. It’s the easier lie. It’s the lie the system expects. We are all performing this strange theater of efficiency, pretending that these tools are making us better, faster, and smarter, while we quietly struggle to perform basic tasks. I wonder if the architects of these systems ever actually use them. Do they ever have to click 16 times to prove they spent $56 on a sandwich? Or are they too busy designing the next ‘intuitive’ update that will move the buttons again?

The irony is that we are more connected than ever, yet we feel more isolated by the very interfaces that connect us. We are drowning in features but starving for functionality. We have 66 apps on our phones, 16 tabs open in our browsers, and a sense of overwhelm that never truly dissipates. We are waiting for the software to eventually solve the problems that we are too afraid to face ourselves. But the software is just a mirror. It reflects back our own chaos, our own indecision, and our own lack of purpose. If you put garbage into a $2,000,006 system, you don’t get ‘Digital Excellence.’ You just get very expensive garbage delivered at high speed.

I’m looking at the screen again. The progress bar has moved to 76 percent. I have 16 more reports to approve before I can even think about doing the work I was actually hired to do. My wrist still twitches. I think about the 456 other people in this company doing exactly the same thing right now. We are an army of highly-educated professionals spending our best hours serving a database. It feels like a tragedy, but we call it ‘Best Practice.’ Maybe the real transformation isn’t digital at all. Maybe the real transformation is having the courage to delete the software that doesn’t work and go back to the things that do. When was the last time you felt like your tools were actually on your side?