The cursor blinks at me with a rhythmic indifference that feels personal. I am currently staring at a digital field labeled ‘Regional Logistic Classification Code (Required)’ while trying to order a simple replacement part for a machinery assembly that hasn’t changed its design since 1996. I don’t know my regional logistic classification code. Nobody in the history of consumer purchasing has ever woken up and thought, ‘I can’t wait to input my internal accounting sub-sector today.’ Yet, here I am, trapped in a digital hallway designed by someone who clearly values the integrity of their database schema more than the time of the person actually funding their paycheck. I spent twenty-six minutes this morning rehearsing an argument with a customer service representative who hasn’t even answered my ticket yet, imagining the exact tone of righteous indignation I would use to explain why a mandatory field for a non-existent number is a form of soft violence against the user experience.

Most corporate rhetoric is a beautiful, thin veneer of ‘customer-first’ language that quickly dissolves when you touch the actual gears of the operation. We see it everywhere: the ‘we value your call’ recordings that play for 46 minutes, the ‘seamless integration’ that requires four separate logins, and the ‘intuitive design’ that assumes the user has a PhD in the company’s internal organizational chart. It’s a recurring nightmare where the customer is not a human being with a problem to solve, but a data-entry clerk who hasn’t been trained yet. Marcus H., a man I’ve known for 16 years who works as a mystery shopper for high-end luxury hotels, once told me that the true measure of a brand’s soul isn’t in the lobby flowers; it’s in whether the bedside light switch makes sense when you’re half-blind with jet lag at 2:06 AM.

Marcus once stayed at a boutique hotel in Zurich where the shower controls were so ‘innovative’ that they required a three-page laminated manual. The hotel claimed this was part of their commitment to a ‘bespoke sensory experience.’ Marcus, ever the pragmatist, pointed out that it was actually a commitment to the plumber’s convenience-the valves were cheaper to install in that specific, counterintuitive configuration. The guest’s confusion was an acceptable externality for the construction budget. This is the core of the problem: companies optimize for the reduction of internal ambiguity, not the reduction of external effort. They build systems that make the work of their departments-accounting, legal, logistics, marketing-easier to categorize, even if it makes the customer’s life 66 times harder.

When a form asks for information you don’t have, it’s usually because some department deep in the basement of a corporate headquarters needs that data point to balance a ledger or satisfy a compliance check. They could find that information themselves-they likely already have it in a different database-but that would require cross-departmental cooperation, which is harder than just making the customer do the work. It is easier to build a wall and put a hole in it than it is to build a bridge. We see this in the way products are categorized. If you’ve ever tried to find a specific item on a website and realized the categories make no sense, it’s because the website is organized by ‘Product Managers’ or ‘Internal Taxonomies’ rather than how a human uses the object.

I remember buying a specialized fountain pen a few months ago. The website didn’t organize them by ‘Calligraphy’ or ‘Daily Writing,’ but by ‘Nib Manufacturer Series 600’ and ‘Resin Batch 46.’ I am a writer, not a chemical engineer. I don’t know the resin batch. I know how the pen feels in my hand when I’m trying to find the right word for a feeling I haven’t quite named yet. But the company chose to mirror its factory floor on its digital storefront. They forced me to inhabit their world instead of them entering mine. This disconnect is where the ‘customer-first’ lie begins to bleed. We are told we are the center of the universe, but we are treated like a necessary nuisance that must be funneled through a pre-defined set of constraints.

This is particularly prevalent in industries with high technical complexity. You see it in logistics, in manufacturing, and in construction. People want a solution, but companies want to sell a SKU. The difference is profound. A solution acknowledges the messiness of the real world-the fact that a site might be uneven, or that a deadline moved up by 16 days, or that the person ordering doesn’t know the difference between a high-cube and a standard container. This is why I appreciate the approach taken by AM Shipping Containers. Instead of forcing the user to navigate a labyrinth of technical specs that serve internal inventory systems, the focus shifts toward the actual application. Whether it’s storage, housing, or specialized industrial use, the architecture of the interaction starts with the problem, not the internal convenience of the warehouse manager.

I often wonder if the people who design these broken systems ever use them as outsiders. Probably not. They have ‘admin’ access. They bypass the friction they created for the rest of us. There is a specific kind of arrogance in assuming that a customer’s time is an infinite resource to be mined. If you waste 6 minutes of 1,006 people’s time, you haven’t just lost a few minutes; you’ve stolen 100 hours of human life to save yourself the trouble of fixing a database error. It’s a theft that goes unpunished because it’s distributed so thinly that no single person feels the need to sue, even if everyone feels the need to scream.

Marcus H. once told me about a retail chain that tracked ‘customer engagement’ by how long people spent on their app. They were thrilled that the average session time had increased by 56 percent. Marcus pointed out that the increase wasn’t because people loved the app; it was because the ‘Checkout’ button had been moved to a hidden submenu during a recent update. They were celebrating their own incompetence as ‘engagement.’ This is the danger of metrics that aren’t grounded in empathy. You can measure the movement, but you can’t measure the frustration until it’s too late and the customer has moved on to someone who doesn’t treat them like a data-entry intern.

I realize I am being hypocritical. I criticize these systems, yet I stay. I fill out the 16 fields. I hunt for the ‘Regional Logistic Classification Code’ in the fine print of a manual I found in a PDF from 2006. I do it because, in the short term, I need the part. But the resentment builds. It’s a slow-burn erosion of brand equity. Every time a company makes me do their work for them, a little bit of the trust I had in them dies. Trust is built on the belief that the other party is looking out for your interests. When a process is designed for internal convenience, the company is explicitly stating that their interests come first.

I’ve been thinking a lot lately about the ‘rehearsed conversation’ phenomenon. You know the one-where you’re driving or showering and you’re explaining to an imaginary executive why their latest policy is stupid. It’s a symptom of powerlessness. We rehearse because we know that when we finally talk to a real person, they will be shielded by 6 layers of scripts and ‘I’m sorry, the system won’t let me do that.’ The ‘system’ becomes the ultimate scapegoat. It’s a ghost in the machine that takes all the blame while the people who designed it collect their bonuses for ‘optimizing internal workflows.’

We need a return to the messy, human side of business. We need systems that are comfortable with ambiguity and can handle the fact that customers are often confused, hurried, and tired. The best companies aren’t the ones with the most ‘rapid’ (excuse me, I mean the most efficient) processes, but the ones that absorb the complexity on behalf of the user. If a process is complicated, it should be complicated for the company, not for the person paying for the service. That is what actual service looks like. It’s the waiter who sees you’re in a hurry and brings the check with the food. It’s the shipping company that asks ‘What are you trying to do?’ instead of ‘What is your SKU preference?’

I once saw a sign in a small hardware store that said, ‘If we don’t have it, we’ll tell you who does.’ That’s a customer-first philosophy. It acknowledges that the customer’s goal is to fix a leaky pipe, not to give money to that specific store. By contrast, a corporate ‘customer-first’ strategy usually means ‘we will use AI to predict how much more we can charge you before you leave.’ It’s the difference between hospitality and extraction. Marcus H. always says that you can tell everything about a hotel’s management by the quality of the toilet paper. It’s a small, recurring expense that the guest notices 6 times a day. If they skimp there, they’re skimping everywhere you can’t see.

In the end, we are all just looking for a bit of friction-less grace in a world that seems determined to make every transaction a battle. We want to be understood without having to provide our 16-digit account number first. We want companies to realize that their internal convenience is their problem to solve, not ours to accommodate. Until then, I’ll keep staring at this blinking cursor, wondering if anyone will notice if I just type ‘666666’ into the mandatory field and see what happens. Maybe the system will break. Maybe it will finally ask me a question that matters. Or maybe, just maybe, it will send me the part I need and let me go back to my life, where the only regional classification that matters is the one that tells me I’m home.

I think back to that conversation I never had with the customer service rep. I would have told them that every field on a form is a potential exit for a customer. Every ‘Required’ asterisk is a hurdle. If you make the hurdles high enough, eventually, people will just stop running. And you’ll be left with a perfectly clean database, a beautifully organized warehouse, and absolutely no one left to buy what you’re selling. It’s a quiet death, one field at a time. The most dangerous thing for any institution is the moment it becomes more interested in its own reflection than in the faces of the people it was built to serve. We are more than our data points. We are more than our ‘Regional Logistic Classification Codes.’ We are human beings who just want the thing to work. Is that really so much to ask?