I am currently hovering my cursor over a button labeled ‘Execute Batch Submission’ and I am genuinely afraid that if I click it, the building’s HVAC system will shut down in some weird, legacy-code accident. There is no reason for this fear, of course, other than the fact that the interface looks like it was designed by someone who holds a deep, personal grudge against the concept of joy. The font is a jagged, unaliased sans-serif that seems to be vibrating at 16 hertz. The background is a shade of ‘government grey’ that makes my eyes feel like they are being rubbed with dry toast. I have spent the last 46 minutes trying to submit a request for a single box of black ink pens, and yet, here I am, lost in the sixteenth sub-menu of an Oracle portal that appears to have been built during the era of the floppy disk and never looked at again by a human eye.

If my personal phone’s apps behaved this way-if Spotify required me to fill out a 26-field metadata form before I could play a song, or if Instagram asked for my manager’s digital signature before I could post a photo of a lukewarm latte-I would throw the device into the nearest body of water. But in the office, we accept it. We trudge through these digital swamps because we have no choice. It is a captive market, and in a captive market, the user is not a customer; the user is a resource to be managed, or perhaps just a nuisance to be tolerated.

The Friction of Illogical Structure

I recently alphabetized my spice rack. It took 6 hours. I started with Anise and ended with Za’atar, though I realized halfway through that I’d misplaced the Oregano and had to shift 36 jars to the right just to accommodate the ‘O’ section. It was tedious, yes, but it was logical. There was a system that respected the physical reality of the jars and the linguistic reality of the alphabet.

Enterprise software has no such respect. It is a spice rack where the Cinnamon is hidden behind a false panel in the basement, and to access the Salt, you have to prove you’ve been trained in high-pressure sodium management. The friction isn’t accidental. It’s structural. We are forced to adapt to the machine’s limitations because the machine was never designed to adapt to ours.

“It is easier to convince a pack of wolves to cross a highway bridge than it is to get my expense report through the final stage of approval.”

Ava K.-H., a wildlife corridor planner I know, deals with this on a tectonic scale. She spends her days mapping the movement of lynx and elk across fragmented landscapes, trying to find the paths of least resistance. Animals, she tells me, are the ultimate UX testers. They won’t climb a 26-degree incline if there’s a flatter route 126 meters away. They find the flow. But when Ava has to log her field hours into the state-mandated resource management system, she is forced into a digital bottleneck that makes no biological sense. She has to categorize a sighting of a red-tailed hawk under ‘Avian Asset – Predatory – Secondary’ and then wait 116 seconds for the database to fetch the appropriate sub-category.

The Buyer vs. The User

Why is it like this? The answer is a cynical one, but it’s the only one that fits the data. Consumer software is designed for the user because the user is the one with the credit card. If the app is hard to use, the user leaves. But enterprise software is designed for the buyer-the CFO, the CTO, the Head of Procurement.

These people do not use the software. They look at a spreadsheet of features, a list of security certifications, and a price tag that ends in 6 zeros. They want ‘compliance.’ They want ‘enterprise-grade security.’ They want a ‘single source of truth.’ They do not care if the ‘Submit’ button is buried under four layers of modal windows because they will never be the ones clicking it. The person signing the check is fundamentally disconnected from the person clicking the mouse.

The Erosion of Dignity

This disconnect creates a culture of low-grade contempt. When a company forces its employees to use tools that are broken, slow, or incomprehensible, it is sending a message. It is saying: ‘Your time is not valuable. Your frustration is an acceptable cost of our administrative efficiency.’ We talk about ’employee engagement’ and ‘office culture’ as often as we talk about user experience, but the real culture is found in the tools.

I recall a time I accidentally deleted an entire project folder because the ‘Save’ icon and the ‘Delete’ icon were both represented by different shades of blue squares that were exactly 16 pixels wide. I felt like a fool, until I realized that the mistake wasn’t mine-it was the designer’s. Enterprise software is a city made entirely of 90-degree sidewalks with fences on either side. It ignores the desire paths of the human mind.

The Alternative: Designing for Existence

There is an alternative, of course. It’s the philosophy that design should be human-centric from the foundation up, not as a decorative afterthought. We see this in industries that haven’t been entirely swallowed by the ‘compliance first’ beast.

Take the way we think about our physical environments. In the realm of architecture and construction, there’s a growing movement toward modularity and user-focused layouts. For instance, the team at Modular Home Ireland understands that a house isn’t just a collection of square footage to be ‘procured.’ It’s a space where a person actually has to exist, move, and breathe.

They design for the resident, not the bank that issues the mortgage. If enterprise software took a page from that book-if it considered the ‘livability’ of its interface-we wouldn’t be losing 106 hours of productivity every year to purely administrative friction.

The Expertise Trap

I once spent 46 minutes on a support call for a CRM that refused to recognize the existence of the letter ‘Q’ in customer names. The support agent, a very kind person who clearly hated the software as much as I did, admitted that the bug had been known for 126 weeks. It hadn’t been fixed because it wasn’t a ‘priority.’ The buyers didn’t care about the letter ‘Q.’ They cared about the quarterly reporting module, which worked perfectly (on the buyer’s end, at least).

We need to stop accepting ‘it’s just business software’ as an excuse for bad design. The barrier between ‘professional’ and ‘personal’ tech is a lie. We are the same humans with the same brains and the same dopamine receptors, whether we are on a Zoom call or scrolling through a news feed. The friction of bad tools doesn’t stay at the office; we carry it home.

Small Acts of Rebellion

I’ve started a small rebellion in my own office. When the software asks me for a ‘Reason for Request’ on a $6 purchase, I no longer write ‘Required for project documentation.’ I write:

“

To preserve my remaining sanity.

“

I don’t think anyone reads it. In fact, I’m 96% sure that the field is never even indexed in the database. But it makes the 46 clicks feel a little less like a surrender. It reminds me that I am a person, not just a data point in a CFO’s efficiency report. I am still waiting for that ‘Execute Batch Submission’ button to respond. It’s been 166 seconds. Maybe it’s not the HVAC system that will shut down. Maybe it’s just me.

The Broken Contract

In the end, we are all just looking for a path through the woods. Whether we are planning wildlife corridors, alphabetizing spices, or trying to buy a box of pens, we want the world to make sense. We want our effort to be proportional to the outcome. When enterprise software breaks that contract, it breaks something in us. It tells us that the machine is more important than the operator.

And until the buyers start caring about the users-until the CFOs start asking, ‘How does this feel to use?’ instead of just ‘What does this cost?’-we will continue to be trapped in this brutalist digital architecture, clicking our way through the grey, waiting for the button to finally, mercifully, click back.