Noah P. leaned his forehead against the cold, brushed-steel door of the service elevator on the 12th floor. It was 4:12 AM, and the building was breathing in that heavy, mechanical way that only skyscrapers do when they think no one is listening. My hands were still shaking slightly, a residual tremor from the 32 minutes I’d spent wrestling with a busted ballstick valve in my own bathroom just an hour prior. There is something profoundly honest about a toilet overflow at 3:00 AM; it doesn’t ask you to verify your identity or walk you through a three-step onboarding process before it stops ruining your floorboards. It just demands a wrench and a bit of sweat. But here I was, an elevator inspector with 22 years of grease under my fingernails, staring at a high-resolution touchscreen that refused to let me bypass the ‘Safety Greeting’ despite the fact that I’ve performed this exact inspection 112 times this year.
We have entered an era where the shortest distance between two points is a curated detour. Designers call it a ‘user journey,’ but for those of us standing in the dark with a toolkit, it feels more like a hostage situation.
We are marched through ceremonial sequences-pop-ups that congratulate us for existing, tutorials that explain the location of the ‘Close’ button as if it’s a hidden treasure, and confirmation prompts that ask ‘Are you sure?’ as if we haven’t been sure since the moment we opened the app. It is a bureaucratic design habit that has metastasized across every digital interface, born from a desperate need to make friction look like intentionality. If you add enough screens, you can call it an ‘experience.’ If you remove them, you’re just a utility, and apparently, being useful isn’t nearly as prestigious as being an experience.
The Digital Handshake vs. Copper Contact
I remember the old relays. They were loud, clunky, and had exactly 2 settings: working or broken. There was no ‘journey’ to getting a lift to move from the lobby to the 52nd floor. You pressed a button, a copper contact snapped shut, and physics took over. Today, that same action triggers a digital handshake that involves 12 different API calls and a splash screen that reminds you to ‘Enjoy the ride.’ It’s a performance. We are obsessed with the ceremony of access because we’ve confused the process of providing care with the appearance of it. We think that by slowing the user down, we are showing them how much work we did.
[The Arrogance of the Forced Pause]
It’s the digital equivalent of a waiter grinding pepper over your salad for 22 seconds longer than necessary; it doesn’t make the salad better, it just makes you look at the waiter.
This arrogance is particularly grating when you’re operating on 2 hours of sleep. I spent 42 minutes yesterday trying to update the maintenance logs for a hydraulic lift in the warehouse district. The software insisted on showing me a ‘New Features’ carousel. I didn’t want new features. I wanted to log a hairline crack in a piston that could, if left alone for another 12 days, turn this building into a crime scene. But the ‘journey’ required me to acknowledge the new dark mode toggle before I could access the safety report. It’s a strange kind of madness to build a wall between a professional and their work and then paint that wall a friendly shade of blue.
‘); background-repeat: repeat-x; background-size: 100px 100%;”>
The True Meaning of Delight
Designers often talk about ‘delight.’ They want to delight the user at every turn. But they forget that for a lot of us, delight is simply the absence of them. Delight is being able to fix a toilet at 3:02 AM without the flapper valve asking for a rating on the App Store. Delight is an elevator that goes up because I told it to, not because I finished a tutorial. We’ve inherited this clutter because nobody in the boardroom has the courage to suggest that maybe, just maybe, the user knows what they’re doing. We treat every returning user like a bewildered toddler entering a hall of mirrors for the first time. It’s patronizing, and it’s expensive.
Collective Time Lost to Friction (Per Year)
The Aesthetic Lie
I’ll admit to a certain hypocrisy here, though. Last night, after the plumbing disaster, I sat on my bed for 22 minutes and meticulously organized the icons on my phone. I moved the weather app 2 millimeters to the left because it felt ‘balanced.’ I am just as prone to the aesthetic lie as anyone else. I crave the order that a well-designed journey promises, even as I curse the friction it creates. We want the world to be a series of clean, logical steps because the alternative-the raw, unmediated chaos of a broken pipe or a failing elevator motor-is terrifying.
In the real world of heavy machinery and high-stakes infrastructure, the most effective systems are those that stay out of the way. When I’m looking for precision and a lack of ceremony, I find myself gravitating toward organizations that value directness over decoration.
This philosophy of making access direct rather than ceremonious is exactly what ems89champions in their approach. They seem to understand that the user isn’t there to admire the architecture of the app; they’re there to get a job done.
It’s a rare perspective in an industry that usually rewards the person who adds the most buttons, not the one who removes the most obstacles.
“
I once saw a design document that referred to the ’emotional arc’ of an elevator ride. I almost threw my clipboard into the pit. There is no emotional arc to vertical transportation. There is only the arrival.
The Straight Line is a Revolutionary Act
It takes a significant amount of ego to believe that a user wants to ‘journey’ with your software. Most people want to use it as little as possible. The goal should be to disappear. But disappearing doesn’t get you a promotion at a design agency. Adding a ‘gamified progress bar’ to a simple form does. We have incentivized complexity under the guise of engagement. We measure ‘time on page’ as a metric of success, when for the user, ‘time on page’ is often a metric of frustration.
Engagement vs. Efficiency
High Engagement (Bad)
52 Sec
Time to Override
VS
High Efficiency (Good)
1 Sec
Time to Override
If it takes me 52 seconds to find the emergency override, that’s not ‘high engagement’-that’s a failure of moral proportions. Noah P. doesn’t care about your brand story when the car is stuck between floors 22 and 32.
Learning from the Pipe
I think back to that 3:00 AM toilet fix. There was no manual. No ‘getting started’ guide. Just the physical reality of a brass nut and a rubber washer. It was difficult, yes, but it was honest. There was no artificial friction designed to keep me in the bathroom longer than necessary. Digital design could learn a lot from plumbing. A pipe doesn’t care if you like its ‘aesthetic.’ It just moves the water. We need more digital pipes and fewer digital amusement parks. We need to stop pretending that every interaction is a ‘journey’ and start admitting that most are just chores that we should be helping people finish as quickly as possible.
122
Decibel Note of Competence
The sound of arrival, not ceremony.
As I finally got the elevator to move, the motor hummed a steady, 122-decibel note of competence. I watched the floor numbers tick up-12, 22, 32. No pop-ups. No animations. Just the heavy, reliable movement of steel. I wondered how many other people were out there at this hour, fighting with ‘user journeys’ that were actually just roadblocks. We’ve built a world of digital red tape and called it innovation. But eventually, the ceremony has to end. The user has to be allowed to arrive. Are we building paths that lead people where they need to go, or are we just building more fences so we can feel important while we hold the gate open?
