The cursor is a stuttering ghost on the screen, flickering in and out of existence as the progress bar for the new expense reporting portal stalls at 47 percent. I am sitting in a room that smells faintly of industrial lemon cleaner and desperate compliance. My left foot is cold. Ten minutes ago, I stepped in a puddle of something-water, I hope-while wearing only my socks in the breakroom, and that damp, clinging sensation is now the primary lens through which I view the world. It makes me impatient. It makes me want to burn things down, starting with this software.
“It’s more secure!” the trainer chirps. She is standing at the front of the room, pointing at a slide that looks like it was designed in 1997. She’s been saying that for 37 minutes. This is the third training session this week. We are being taught how to use a tool that requires 17 clicks to do what the previous tool did in seven. There is no logic to the architecture. To upload a receipt, you have to navigate to a sub-menu, click ‘Initiate,’ then ‘Confirm,’ then ‘Verify Identity,’ then ‘Select Source,’ and finally-if the gods of the intranet are smiling-you can upload a JPEG that the system will inevitably claim is too large.
The Business Model of Hostage-Taking
This is the great lie of the modern enterprise. We are told that we live in an era of ‘user-centric design’ and ‘frictionless experiences,’ but if you work for a company with more than 107 employees, you know that is a fantasy. You are a hostage. You are using software not because it is good, not because it helps you work, but because some executive at the 47th floor of a glass tower had a very pleasant round of golf with a sales representative from a legacy conglomerate.
I used to think this was a mistake. I used to think that if the C-suite just saw how much time we wasted, they would change it. I was wrong. The disconnect isn’t an accident; it’s the business model. In the world of enterprise sales, the person who writes the check is never, ever the person who has to click the buttons. The buyer values ‘compliance,’ ‘scalability,’ and ‘integrated ecosystems’-words that sound impressive in a board meeting but translate to ‘slow,’ ‘bloated,’ and ‘impossible to navigate’ for the rest of us. The person buying the software is looking at a spreadsheet of 237 features. They don’t care if 230 of those features are broken or unintuitive, as long as they can check the box that says they exist.
Sellability vs. Usability
The Human Cost
“
Arjun leans over to me. His eyes are bloodshot. “I found 107 ghost employees in a construction firm last month,” he whispers, “but I cannot figure out how to change my password on this thing without it locking me out for 7 days.”
– Arjun M.-L., Investigator
I look at my damp sock and think about the sheer volume of human potential being liquidated in rooms like this. We are essentially paying people to fight with their tools. It’s like hiring a master carpenter and then forcing them to build a house using a spoon and a heavy rock, while a consultant stands over them saying, “The spoon is more enterprise-grade!”
There is a profound psychological cost to this. When you force people to use tools that don’t respect their time, you are telling them that their time doesn’t matter. You are telling them that their expertise is secondary to the ‘process.’ Over a 7-year contract, that message erodes a culture. It turns innovators into bureaucrats. It turns people like Arjun, who should be hunting down $77,777 in fraudulent claims, into people who spend their Tuesday afternoons wondering if they should just quit and become a goat farmer.
The cruelty of the interface is the loudest silent scream in the office.
Risk Aversion: The Real Security Blanket
But here is the contradiction I’m wrestling with: I hate this. I loathe it. And yet, I understand why it happens. Large organizations are terrified of risk. A small, nimble tool that everyone loves is a ‘security risk’ in the eyes of a Chief Information Officer who is one data breach away from early retirement. They would rather buy the 47-ton behemoth that is impossible to use but has a ‘Global Support Agreement’ and a 700-page compliance manual. They are buying insurance, not productivity.
The Shifting Focus
End-User Hearts
Primary Stakeholder
Hard Metrics
Quantify the Loss
Technical Proof
Developer Buy-in
Transparency in Infrastructure
In the world of infrastructure and communication, where the stakes are high, you see this tension most clearly. Developers, the ones who actually have to integrate the APIs and ensure the messages land where they are supposed to, are tired of the old ‘golf course’ deals. They want tools that work. They want to see the performance metrics for themselves. This is why a company like
makes so much sense in this landscape; they give the technical users the transparency and data they need to justify a better choice to the people holding the purse strings. It’s about arming the hostages so they can negotiate their own release.
The Question That Froze the System
User Input Required
I realize I’ve been staring at my wet sock for too long. The trainer is asking if there are any questions. Arjun raises his hand.
“If this tool is designed to make us more efficient,” Arjun asks, his voice surprisingly calm, “why has it taken me 7 minutes to find the exit button?”
The trainer pauses. Her smile doesn’t falter, but her eyes go cold. “That’s a great question, Arjun! We’ll cover navigation in Module 7, which starts after the lunch break.”
There is a collective groan in the room, a low-frequency vibration of 47 souls losing another piece of their will to live. I think about the $777 million dollar valuation of the company that made this software. I think about the sales rep who is probably on a boat right now, celebrating the 7-year renewal they just signed with our CEO. And then I think about my sock. It’s still wet. It’s still cold. It’s a small, persistent misery that reminds me I’m alive, which is more than I can say for this software.
The Hierarchy of Needs (In Enterprise)
Compliance, Scalability
Checkboxes, Renewals
Time Wasted, Sanity
The Path to Liberation
We are often told that technology is a neutral force, but that’s a lie. Technology carries the values of its creators and the priorities of its buyers. When software is built for the buyer and not the user, it is an act of soft authoritarianism. It is a way of saying that the person at the top matters more than the experience of the thousand people at the bottom. It turns work into a series of unnecessary obstacles, a gauntlet of 17-click tasks that serve no purpose other than to satisfy a requirement that no one remembers creating.
I wonder what would happen if we all just stopped. If Arjun just closed his laptop and walked out. If I took off my wet sock and threw it at the projector. What if we demanded that our tools be as good as our talents?
System Response Time
7 Seconds
It feels like 7 years.
The Final Acceptance
Instead, I click. I click for the 107th time today. The screen refreshes. A spinning wheel appears. It’s been spinning for 7 seconds. I look at Arjun. He’s staring at the ceiling now, probably imagining those 107 ghost employees living a better life somewhere, free from mandatory training and ‘secure’ portals that don’t work.
The Damp Victory
Maybe the software isn’t broken. Maybe it’s doing exactly what it was designed to do: remind us exactly where we stand in the hierarchy of the machine. But my sock is starting to dry, and for some reason, that feels like a small, quiet victory in a world that wants to keep us damp and compliant.
Why do we accept this? Because the cost of change is always presented as higher than the cost of misery. But eventually, the math changes. Eventually, the friction becomes fire. And when that happens, the people who have been clicking through the 17-step menus will be the ones who decide which towers stay standing and which ones get deleted.