The cursor flickers, a tiny white heartbeat against the harsh blue of a spreadsheet that has grown to 55 columns wide. It is 2:15 AM, and the silence of the office is so heavy it feels like a physical weight on the shoulders of the person sitting there, illuminated only by the glow of three mismatched monitors. This is the ‘seamless’ experience in its raw, unedited form. On the front end, a customer just clicked a button and received a confirmation. It was easy. It was elegant. It was a lie. Behind that single tap, an operations specialist is manually reconciling a settlement mismatch that the automated system tripped over five hours ago. They are currently hunting for a missing string of characters in a CSV export that looks more like a digital graveyard than a financial record. I know this because I have been that person, staring at the screen until the pixels start to swim, wondering when the ‘future’ actually arrives and when we just started pretending the machines were smarter than they are.

We are living in an era where convenience is the ultimate currency, but we rarely ask who is paying the minting fees. We market ‘frictionless’ as if it were a law of nature, a byproduct of clever code and sleek UI/UX design. But in reality, friction is a conserved quantity. If you remove it from the user’s palm, it has to go somewhere else. Usually, it settles in the lower back of an ops manager or the frayed nerves of a support agent who has to explain why the ‘instant’ transfer is taking 25 hours. I recently cleared my browser cache in a fit of desperate superstition, hoping it would fix a routing error that had no business existing in a modern stack. It didn’t work. It never does. It’s the digital equivalent of shaking a polaroid-a ritual performed to feel in control of a process that has become too opaque to truly manage.

João D., a fragrance evaluator I met during a particularly strange project in Lisbon, once told me that the most expensive perfumes are the ones that smell like nothing at first. They are designed to sit on the skin and wait, absorbing the wearer’s heat before they bloom. He called it ‘the labor of the invisible.’ João D. spends 45 hours a week sniffing base notes that most people would find repulsive-damp earth, civet, fermented woods-just to ensure that the final product feels effortless. He told me that if a customer can smell the work, the perfumer has failed. The digital world has adopted this same ruthless philosophy. If the user can see the 15 API calls, the three database handshakes, and the manual verification step, the ‘magic’ is broken.

This creates a bizarre paradox where the more advanced our systems become, the more we rely on human ‘glue’ to keep the edges from fraying. We see this in every industry that promises immediacy. The delivery app that shows a biker moving across a map is often hiding a chaotic kitchen where 25 different tablets are screaming for attention, and a harried manager is trying to figure out why the system accepted an order for a dish they ran out of five days ago. The ‘convenience’ is a veneer. Underneath, there is a frantic, manual re-arrangement of reality to match the promise made by the interface. It’s a performance. We are all participating in a grand theater of efficiency where the actors are exhausted and the stagehands are working double shifts.

I’ve spent 15 years watching technology solve problems only to create a more sophisticated class of headaches. We build a tool to automate X, but then we need five people to manage the tool that automates X, and those five people need a manager to oversee the integration of that tool into the legacy system that nobody understands anymore. It’s a recursive loop of complexity. And yet, when we talk about success, we point to the ‘user journey.’ We measure the milliseconds it takes for a page to load, but we don’t measure the minutes of sleep lost by the person who has to fix the database at 3:45 AM.

This is why operational design is the only thing that actually matters in the long run. You can have the most beautiful app in the world, but if your back-end processes are held together by Scotch tape and prayers, you aren’t selling a product; you’re selling a debt. Reliability is a quiet virtue. It’s not flashy. It doesn’t make for a great ‘revolutionary’ keynote speech. But it is the difference between a system that serves its users and a system that consumes its workers. True excellence in this space is found when the operational integrity matches the front-end promise. Platforms like U9play succeed not because they’ve eliminated complexity-nobody truly can-but because they’ve built the infrastructure to handle it without passing the exhaustion down the line. It’s about building a house where the foundation is as polished as the foyer.

There is a specific kind of arrogance in thinking we can code our way out of human effort. Every time we claim a process is ‘fully automated,’ a red flag should go up. Automation is great for the 95% of cases that follow the rules. But life, and business, happens in the other 5%. That 5% is where the weird errors live, where the ‘unlikely’ edge cases congregate, and where the human element is non-negotiable. When we ignore that, we end up with systems that are brittle. They look great until they hit a bump, and then they shatter because there’s no one left who knows how to pick up the pieces.

I remember a particular Tuesday when I was trying to explain to a client why their ‘one-click’ reporting tool was taking 55 minutes to generate a PDF. They were furious. ‘It’s just data!’ they shouted. ‘Why is it so hard?’ It was hard because the data was coming from four different sources, one of which was an Excel sheet maintained by a guy named Gary who had been on vacation for two weeks and hadn’t updated his formulas. The ‘one-click’ was a facade. The reality was Gary. And Gary is the unsung hero of the modern economy. We have built a world that runs on Garys, and then we spend all our time trying to figure out how to fire Gary and replace him with an AI that doesn’t understand why the formulas are broken either.

João D. once showed me a bottle of raw ambergris. It smelled like the ocean if the ocean had a bad cold. It was oily, pungent, and frankly, a bit gross. ‘Without this,’ he said, ‘the rose water is just juice. This is what makes it hold. This is the weight.’ We are currently trying to build a world of rose water without the ambergris. We want the lightness without the weight. We want the speed without the friction. But without the weight, nothing lasts. Without the friction, there is no traction.

I catch myself falling for the trap all the time. I get frustrated when a video takes more than five seconds to buffer, forgetting that I am currently pulling high-definition data from a satellite or an underwater cable across a distance I couldn’t walk in a year. The convenience has spoiled my sense of scale. It has made me ungrateful for the miracle of the ‘invisible.’ We need to start valuing the people who manage the complexity instead of just the people who hide it. The ops specialist with the cold coffee at 2:25 AM deserves a seat at the table where the ‘vision’ is discussed, because they are the ones who know exactly how much that vision actually costs.

If we keep moving the friction around without ever actually reducing it, we’re just building a bigger and bigger spring that is eventually going to snap. We see the signs already: burnout, systemic failures, the ‘ghosting’ of service industries. You can only ask people to absorb so much complexity before they run out of room. We need to design for the back-end as much as we design for the front-end. We need to make the labor sustainable, not just invisible.

Is the convenience we enjoy worth the exhaustion we’ve outsourced, or have we just stopped looking at the bill because it’s being sent to someone else’s address?