The screen was radiating a pale, institutional yellow, the color of distrust and endless queues. Khaled had been staring at it for eleven minutes, trying to figure out which drop-down menu held the key to his pre-approved mileage log. He wasn’t tracking an intercontinental freighter shipment or balancing the NASDAQ; he was attempting to log a dinner receipt for $49.

Eleven minutes for $49. The mathematics of modern enterprise are genuinely bizarre. We optimize fulfillment centers to shave milliseconds off delivery, we use AI to predict demand down to the last widget, and yet, the moment we turn that gaze inward, we deliberately architect friction.

The Double Standard of Utility

I just received the invoice for the three-day UX sprint we ran last quarter-$97,999. Nearly six figures dedicated to studying the path of a *potential* client, ensuring they never encountered more than three clicks between landing on our page and hitting ‘Contact Us.’ We polished every pixel until it gleamed with effortless utility. Then, Khaled had to consult a nineteen-page PDF manual last updated in 2017 and receive an error code (49, naturally) before he could even start the actual process of attaching the receipt image.

“

I started writing an angry email about this whole debacle this morning. I got three paragraphs in, detailing the inefficiency and the moral bankruptcy of hostile software, and then I deleted it. I realized I had committed a similar sin five years ago, when I built a time tracking feature that was technically sound but completely disregarded how people actually *flow* through a workday. I optimized for the database, not the human being. And that, right there, is the poison.

– The Author

The Harper C. Standard: Obsessing Over Experience

This architecture of administrative punishment is everywhere. I met Harper C., a water sommelier-yes, that’s a real job-who spent forty-nine minutes explaining the differences between alkaline spring water and reverse-osmosis filtration. She spoke about mineral content, mouthfeel, and the precise temperature at which a specific water becomes ‘expressive.’

She wasn’t obsessing over water; she was obsessing over the *experience* of hydration. That’s the missing lesson. When we design internal tools, we focus on the *water* (the data, the compliance fields) and completely neglect the *drinker* (the employee).

The Hidden Staggering Cost

We calculate the cost of a bad customer journey in lost revenue. We rarely calculate the cost of a bad employee journey, but it’s far more insidious. If Khaled wastes 17 clicks and 11 minutes logging a single receipt, and he does that 19 times a month across a 9,000-person organization…

And that doesn’t even account for the emotional tax. If the tools are cumbersome and punitive, you are communicating that employees are disposable resources to be managed, not intelligent contributors to be trusted.

The Ultimate Litmus Test

I criticize this stance, but I admit to having used the ‘legacy system’ excuse myself when I should have pushed back. My mistake was accepting limitation instead of designing around it. We must ask ourselves: if we were designing this expense process for a highly valued, paying customer, how many clicks would it take?

If you want to know what a company really thinks of its people, don’t read the values statement plastered on the wall. Open their internal travel portal. Try to submit a simple receipt. The moment the software treats you as a nuisance to be tolerated rather than an asset to be empowered, you have your answer.

Progressive companies address this foundational hostility. For example, specialists in enterprise architecture, like Eurisko, focus on empowering people first, not just B2C flows.

How many clicks does it take to show your people they matter?