Sarah’s eighth tab is spinning a frantic, pale-blue circle of death while the caller, a man named Leonard who just wants to know why his $48 subscription billed twice, begins to sigh with the heavy, rhythmic cadence of someone who has been on hold for exactly 118 seconds. He doesn’t know that Sarah is currently fighting a four-front war. Behind her professional, slightly-too-high-pitched ‘I can certainly help you with that’ voice, she is toggling between a legacy CRM that looks like it was designed in 1998, a Slack channel where her manager hasn’t replied in 28 minutes, a knowledge base with three conflicting articles on billing errors, and a password reset window for the accounting portal that just timed out for the third time this hour.

We talk about the customer journey as if it’s a paved road, a sleek architectural achievement of branding and UX, but for the people actually running the machinery, it’s a goddamn obstacle course through a dense thicket of uncooperative software. It’s hard to stay empathetic when your tools are actively gaslighting you. I’m writing this with a slight tremor in my left hand because, well, I just realized I accidentally liked my ex-girlfriend’s photo from three years ago-a sun-drenched shot of her in Maui-while I was doom-scrolling before this session. The digital footprint of our mistakes is permanent, yet our internal systems at work can’t even remember a customer’s last name between two different windows. The irony is so thick it’s hard to breathe.

The Front Stage vs. The Back Stage

Jasper B.K. understands this better than most, though he doesn’t work in tech. Jasper is a food stylist, a man who spends 18 hours a day making things look like what they aren’t. I watched him once in a studio in Queens. He was using a syringe to inject heavy cream into a bowl of cereal because real milk looks like watery nothing under the high-intensity lights. He used a blowtorch on a raw hamburger patty to give it those perfect, charred grill marks that suggest a backyard summer that never actually happened. Jasper’s whole existence is about the ‘Front Stage’-the image that reaches the public.

But the ‘Back Stage’? Jasper’s studio is a chaotic sprawl of industrial glue, motor oil (which he uses instead of maple syrup because it doesn’t soak into pancakes), tweezers, and half-melted plastic. If the customer-the person buying the burger-saw the motor oil and the tweezers, the illusion would shatter. This is exactly what’s happening in modern corporate architecture. The front stage is a beautiful, 2028-ready website, but the back stage is held together with the digital equivalent of motor oil and Jasper’s tweezers. When a customer calls, they are inadvertently peeking behind the curtain, and what they see is a support agent struggling to stitch together five broken systems just to find a tracking number.

The Empathy Paradox

Organizations treat poor customer experience as a frontline personality problem. They send Sarah to ’empathy training’ or give her a script that includes 18 different ways to say ‘I apologize for the delay.’ But you can’t ‘smile’ a broken API into working. You can’t ’empathize’ a 408 Request Timeout error out of existence. We are blaming the pianist for a piano that hasn’t been tuned since the Bush administration. The problem isn’t the person; it’s the architecture. How institutions arrange work for their employees eventually becomes how they treat the public. It is a fundamental law of organizational physics. If your internal data is fragmented, your customer’s experience will be fragmented. If your staff has to log into 8 different portals, your customer will have to repeat their story 8 different times.

There’s this weird obsession with ‘omnichannel’ support, which usually just means the company has 18 different ways to ignore you. They have a Twitter bot, a Facebook chat, an email alias, and a phone line, but none of those channels talk to each other. It’s like a person with multiple personalities where none of the identities share a memory. You tell the Twitter bot your problem, and when you finally get a human on the phone, they ask you to start from the beginning.

The Cleanup Problem

I’ve made mistakes. I’ve built workflows that were so complex they required a 48-page manual that nobody read. I’ve chosen software because the sales demo looked ‘remarkable’-wait, I promised myself I wouldn’t use that word-because the demo looked shiny, ignoring the fact that it didn’t integrate with our actual database. We chase the ‘New’ because the ‘New’ feels like progress, but true progress is often just cleaning up the ‘Old.’ We need systems that act as a single source of truth, something that allows a human being like Sarah to actually look Leonard in the digital eye and solve his problem without her computer fans spinning up like a jet engine.

When companies finally decide to stop the bleeding, they often look for a way to centralize the madness. They look for a partner that understands that fragmentation is the enemy of growth. This is where the value of a unified approach becomes undeniable, moving toward a reality where tools like ems89 represent the shift from fragmented chaos to streamlined utility. It’s about reducing the cognitive load on the employee so they can actually do the job they were hired for: being a human. We forget that every second an employee spends navigating a maze is a second they aren’t spent solving a human problem.

Jasper B.K. told me once, while he was meticulously gluing sesame seeds onto a bun with a pair of surgical tweezers, that the hardest part of his job isn’t the styling. It’s the cleanup. It’s the 108 minutes at the end of the day spent scrubbing motor oil off the floor and organizing his kit. He said that if he doesn’t organize his kit, the next day’s ‘beauty’ is impossible. Companies are great at the styling-the branding, the ads, the influencers-but they are terrible at the cleanup. They leave their internal systems to rot, layering new software on top of old like sediment, until the whole thing is a geological record of bad decisions.

The Architectural Imperative

I keep thinking about that Hawaii photo. Why does the interface make it so easy to make a mistake? Why is the ‘Like’ button a millimetre away from where your thumb naturally rests while scrolling? It’s an architecture designed for engagement, not for the human. Our internal work tools are the opposite; they are designed for… well, I’m not sure what they are designed for. Certainly not for speed. Probably for ‘compliance’ or because some procurement officer got a good deal on a bulk license for 2888 users.

If we want to fix the customer journey, we have to stop looking at the customer. We have to look at the agent. We have to look at the 8 tabs. We have to look at the fact that the ‘Knowledge Base’ hasn’t been updated since August 2018. We have to realize that when Sarah is frustrated, Leonard is frustrated. The employee experience is the shadow that the customer experience casts. You can’t change the shape of the shadow without changing the object that’s blocking the light.

Conclusion: Cleaning Up the Mess

I should probably apologize to Sarah. Not the support agent, the girl from Maui. But that would require another digital interaction, another ‘event’ in the architecture of our failed relationship. Instead, I’ll just sit here and think about Jasper’s tweezers. I’ll think about the 188 different ways we try to hide the mess instead of just cleaning it up. We are so busy trying to look ‘modern’ that we’ve forgotten how to be functional. It’s time to stop the maze-building. It’s time to let Sarah close seven of those tabs and just talk to Leonard. After all, he’s only asking for a simple fix, and it shouldn’t take a miracle to give it to him.