The blue light from Sarah’s monitor reflected off Ben A.’s glasses, creating a strobe effect that made his perfectly curated virtual background-a minimalist loft in Copenhagen-look like it was glitching through a digital storm. Ben A., a virtual background designer who spends 48 hours a week making sure CEOs look like they live in architectural digests, was currently watching a disaster unfold in the accounting department. He wasn’t there to design; he was there because the new software required ‘visual validation’ for every single entry, a process so convoluted it made his 128-layer Photoshop files look like finger paintings. Sarah’s hand hovered over the mouse, her index finger twitching. She was on click 18 of a sequence that used to be a single keystroke. The $2,000,008 Enterprise Resource Planning system-a beast of a program designed to ‘synergize global assets’-was currently being defeated by a simple travel reimbursement for a pack of pens that cost $8.

There is a specific kind of silence that fills a room when technology fails upward. It is the silence of 388 employees collectively realizing that their jobs just got harder in the name of efficiency. This new software didn’t just arrive; it descended like a digital fog, obscuring the workflows that had kept the company alive for 28 years. The assumption, whispered in boardroom meetings by consultants who hadn’t touched a ledger in a decade, was that technology solves human problems. They were wrong. More often than not, expensive software simply automates existing dysfunction and adds a costly layer of complexity that people secretly work around just to survive the day. I saw this firsthand last month during the 88-page training seminar. At one point, while the instructor was explaining how to ‘cascade the metadata,’ I actually leaned my head back, closed my eyes, and pretended to be asleep. Nobody noticed. They probably thought I was having a spiritual experience with the user interface. In reality, I was just trying to escape the realization that we had spent a fortune to build a digital labyrinth.

The Canyon of Misalignment

Software procurement is rarely about the person clicking the button. It is about the person signing the check, and those two people haven’t spoken to each other in 18 months. When the gap between the decision-maker and the tool-user becomes a canyon, you end up with systems that require 48 minutes of data entry for 8 seconds of actual work. We invest in these tools before understanding the people who use them, assuming a set of algorithms can replace institutional knowledge. It is a profound disrespect for the craft of the employee.

Ben A. knows this better than anyone. He builds the illusions we live in during our Zoom calls, but even he can’t mask the frustration of a system that treats every human input as a potential error. He once told me that his favorite background is a simple, empty wooden table. ‘It’s the only thing that doesn’t require an update,’ he muttered while Sarah finally reached the 28th screen of her reimbursement form.

For those who truly value the marriage of craft and utility, exploring curated selections like Old rip van winkle 12 year reveals a truth that tech companies often ignore: the quality of the finish matters just as much as the substance itself. You wouldn’t serve a legendary spirit in a glass that leaks, yet we ask our most talented employees to pour their expertise into software that drains their spirit by the hour.

Complexity as Tax

The tragedy is that the company will never see those 48 minutes as a metric of success. They will only see the $2,000,008 line item on the balance sheet and wonder why the ‘digital transformation’ hasn’t yielded the 28% increase in productivity they were promised. We have entered an era where complexity is mistaken for capability. We add 18 new features to a program because a competitor did, without asking if a single person on the front lines needs them.

I made a mistake early in my career where I advocated for a system that looked amazing in the demo but was a nightmare in practice. I was seduced by the 48-page brochure and the promise of ‘seamless integration.’ I failed to realize that ‘seamless’ is usually code for ‘we hid all the buttons you actually need.’