I am currently hovering my cursor over a button labeled ‘Submit for Reconciliation,’ and I have no idea if clicking it will refund my lunch money or delete the entire western regional database. This is my 23rd attempt at processing a single receipt. The receipt is for a $13 sandwich-a sourdough melt that was honestly a bit dry-but the emotional cost of this transaction is mounting into a debt I can never repay. My screen is a kaleidoscope of 43 distinct menu items, each with its own nested sub-menu, blinking with a desperate need for my attention. I am Kendall B.K., a disaster recovery coordinator by trade. My entire career is dedicated to managing chaos, predicting the unpredictable, and pulling order from the wreckage of failed systems. Yet here I am, defeated by a web-based expense portal that seems to have been designed by a committee that hates the concept of time itself.

We have reached a point in the history of human productivity where we require half an hour of instruction to explain how to give a company a picture of a piece of paper so they can give us back our 13 dollars. This is not a tool. A hammer is a tool. A shovel is a tool. You pick them up, you understand their weight, and you apply them to the world. This software is a landscape, a dense and prickly thicket that requires us to clear a path every single time we want to walk through it. We are no longer using tools; we are serving them.

The Era of the Software Janitor

This shift is not accidental. In the world of enterprise software, complexity is frequently marketed as a feature, a sign of ‘robust capability.’ If a program can do 103 different things, it is perceived as more valuable than a program that does 3 things perfectly, regardless of whether the user only ever needs those 3 things. We have entered the era of the ‘software janitor.’

In every department, from accounting to disaster recovery, high-salaried professionals are spending 13 to 23 percent of their workweek performing digital maintenance. We are cleaning up data entries, mapping fields that don’t talk to each other, and navigating ‘dependency ecosystems’ that feel more like hostage situations.

The Labyrinth and the Gaslight

“I spent 43 minutes yesterday trying to change my password, a process that required two-factor authentication from a device I no longer own and a security question asking for the name of a childhood pet I never had. It is a labyrinth.”

The designers of these labyrinths are quite proud of them. They talk about ‘user engagement’ and ‘dwell time.’ They want us to stay inside the software. But for someone like me, who deals with literal disasters, this digital friction is dangerous. When a server farm in Ohio is underwater, I don’t have 13 minutes to figure out which ‘workspace’ I need to be in to alert the engineering team. I need the friction to disappear.

But true literacy is the ability to read the room, and the room is screaming for simplicity. We are drowning in ‘solutions’ that require more work than the problems they were meant to solve. It is a cycle of dependency where the software vendor becomes a permanent fixture in your budget.

The Value of the Lever Over the Dashboard

We need software that respects the fact that we have lives outside of its interface. I don’t want to be a power user. I want to be a person who gets his work done and then goes home to play with his 3 dogs. The current trajectory of software development is a direct threat to that desire.

This person is likely someone with a Master’s degree, earning 93 thousand dollars a year, who spends their Monday morning clicking through a 13-step verification process just to approve a vacation request. This is a massive misallocation of human talent.

The Breaking Point

For 33 minutes, I watched a progress bar crawl across the screen while the temperature in the server room climbed toward 103 degrees. I was paralyzed by the very system that was supposed to empower me. We have built a world where the gatekeepers are made of code, and they are frequently asleep at the wheel.

It takes 103 hours of thinking to remove 3 minutes of friction, but that is the work that actually matters. Until then, I will be here, staring at my $13 sandwich receipt, wondering if I should just pay for it myself rather than spend another 23 minutes in this digital purgatory.

The Hidden Cost

There is a hidden cost to all this ‘efficiency.’ It is the cost of the things we don’t do because we are too busy managing the software that was supposed to help us do them. We don’t brainstorm. We don’t innovate. We don’t take the time to look at the big picture because we are too focused on the tiny, broken pixels right in front of our faces.

This is why I find myself gravitating toward companies that prioritize the actual user experience over the aesthetic of complexity. It is about curated confidence. You want to know that when you buy a solution, it actually solves the thing without demanding a tribute of your sanity. For instance, in the realm of home climate, finding a direct and honest approach is like finding an oasis. I recently looked into minisplitsforless because they understand this fundamental truth.

We have allowed our lives to be cluttered by the very things that promised to organize them. It is time for a radical return to the basics. It is time to value the lever and the valve over the dashboard and the dropdown. It is time to stop being software janitors and start being humans again.

I’ll click the ‘Submit’ button now. I’ll pray to the 3 gods of Silicon Valley that it works. If not, I suppose I’ll just force-quit and start again for the 63rd time. It’s my job, after all. Or at least, it’s what my job has become. I used to save the world from disasters. Now, I just try to save myself from the menu screen.