The haptic vibration of my father’s thumb hitting the glass screen for the 17th time is a rhythmic, dull thud that vibrates through the sofa cushions. I have my eyes squeezed shut, pretending to be asleep, because if I open them, I will have to explain, for the 47th time this month, that the three horizontal lines in the top-left corner are actually a door. He is tapping the logo. He is tapping the empty white space. He is looking for a way out, or perhaps a way in, and the software is staring back at him with the cold, sterile blankness of a gallery wall. To him, the phone isn’t a tool; it is a riddle wrapped in an enigma, designed by someone who assumes that everyone born before 1997 possesses the same telepathic link to the Silicon Valley zeitgeist.

I’ve spent 27 years watching people navigate physical spaces as a queue management specialist. My name is Camille J.D., and my entire professional life is dedicated to the science of flow-the way bodies move through turnstiles, the way eyes seek out exit signs in a crowded terminal, and the way a poorly placed stanchion can trigger a micro-riot in a post office. I know that if you put a door handle on a door that is meant to be pushed, someone will try to pull it. That isn’t the user’s fault; it’s a failure of affordance. Yet, in the digital realm, we have spent the last 17 years gaslighting an entire generation of users into believing that if they can’t find the ‘settings’ menu, it’s because they are ‘tech-illiterate.’ We call our designs ‘intuitive,’ but that word is a violent lie. Nothing is intuitive. Everything is learned.

The Illusion of Intuition

We talk about the ‘intuitive’ nature of an interface as if it were a biological imperative, like breathing or blinking. It isn’t. When a designer says an app is intuitive, what they actually mean is that it follows a set of conventions established by a specific group of wealthy, Western developers over the last 37 years. If you grew up with a mouse in your hand, you know that a blue underlined word is a portal. If you grew up with a touch screen, you know that a long press might reveal a secret. But these are not instincts. They are scars of habit. My father doesn’t have those scars. To him, the screen is just glass. There is no depth, no layering, and certainly no reason to believe that a ‘hamburger’ icon-a symbol that looks more like a stack of pancakes than a navigation tool-contains the sum total of the application’s functionality.

In my line of work, if I hide the entrance to a queue behind a decorative plant, the system collapses within 7 minutes. In software design, we call that ‘minimalism’ and give it a design award. We have reached a point of digital arrogance where aesthetics have completely cannibalized utility. We hide buttons because they are ‘ugly.’ We remove labels because they ‘clutter the UI.’ We replace clear, text-based instructions with 87 different icons that all look like variations of a square with an arrow. It is a form of gatekeeping masquerading as sophistication. We have built a world of hidden gestures-swipes, pinches, and three-finger taps-that function like secret handshakes for the initiated, while leaving everyone else standing outside in the cold.

Cultural Arrogance and the ‘Clean’ Look

This arrogance is particularly visible when we try to export these design languages across cultures. What works for a user in San Francisco, who has been conditioned by 17 iterations of the same operating system, fails miserably in markets where the digital leapfrog occurred differently. In Thailand, for instance, the mental model for digital interaction often favors high-density information and explicit visual cues over the ‘clean’ (read: empty) look favored by Western elites. People there don’t want a mysterious blank canvas; they want a dashboard that looks like a stickpit-vibrant, functional, and honest about what it does. Platforms that succeed in the Thai market, like สมัครจีคลับ, understand that reliability stems from visible, predictable pathways rather than abstract minimalism. They respect the user’s time by not making them play a game of ‘find the button’ just to access a service.

I remember a specific instance during a consulting gig at a major metropolitan airport. They had installed these sleek, touch-screen kiosks for check-in. The designers were very proud of the ‘seamless’ glass front. There were no buttons, no slots, just a glowing screen. I sat in a chair and watched 137 passengers approach those kiosks. Every single one of them hesitated. They hovered their hands over the glass like they were trying to read a crystal ball. Why? Because the kiosk didn’t tell them what it was. It didn’t have the ‘scent’ of a check-in desk. It was just an object. Eventually, the airport staff had to tape paper signs to the $7,777 kiosks that said ‘CHECK IN HERE’ with a giant hand-drawn arrow. That paper sign was the ‘intuitive’ design the digital team forgot to build.

Designing for the 93%

We are currently in a cycle of design where the ‘power user’ is the only person who matters. We design for the 7% of people who spend 17 hours a day on their devices, and we treat the other 93% as an afterthought. We’ve decided that if a user has to think for more than 7 seconds, it’s their brain that’s the problem, not our code. But as a queue manager, I can tell you that the brain is never the problem. The environment is the problem. If the environment doesn’t provide the right signals, the system fails. And right now, our digital environments are failing the very people they claim to serve. We are building digital labyrinths and calling them parks.

I find myself constantly contradicting my own professional ethics. I love my minimalist phone. I love the way the icons are perfectly spaced and how the animations glide at 127 frames per second. But then I see Camille-not me, but the version of me that isn’t a specialist-trying to use a modern ‘smart’ washing machine that has a touch interface instead of a dial. I see her standing there, staring at a flashing ‘E07’ error code, trying to figure out which combination of invisible buttons will make the water drain. There is no dial to turn. There is no physical feedback. It is just a flat piece of plastic that refuses to acknowledge her existence. In that moment, the ‘intuitive’ future feels like a prison. We have traded the tactile certainty of a click for the ghostly uncertainty of a ‘tap-and-hold.’

Radical Clarity: The Path Forward

What would a truly intuitive interface look like? It would probably be very ‘ugly’ by current standards. It would have buttons that look like they can be pressed. It would have labels-actual words, in the user’s primary language-instead of ambiguous glyphs. It would follow the ‘Rule of 7,’ where no more than 7 options are presented at once, and each one is clearly distinguished from the others. It would acknowledge that a user’s attention is a finite resource, not something to be harvested through ‘engagement’ loops and hidden menus. It would be radical clarity. It would be a design that doesn’t require a 27-page manual or a 17-minute YouTube tutorial to understand how to change the font size.

I finally ‘woke up’ on the sofa. My father was holding the phone out to me, his face a mask of quiet defeat. ‘It’s stuck,’ he said. He had accidentally activated the ‘one-handed mode’ by swiping down on the bottom edge of the screen-a gesture he didn’t know existed and couldn’t possibly have discovered through logic. The screen had shrunk to half its size, leaving a vast black void at the top. To him, the phone was broken. To a designer, it was a ‘feature.’ I took the phone, swiped it back to normal, and handed it back without a word. I felt like a priest performing a ritual for a god he no longer believes in.

Cognitive Accessibility and Honest Tools

We need to stop worshipping at the altar of the ‘clean UI.’ We need to start designing for the person who is tired, the person who is 77 years old, the person who is using their phone in the rain while holding an umbrella, and the person who just wants to get a simple task done without feeling like an idiot. Digital accessibility isn’t just about screen readers and high-contrast modes-though those are vital-it’s about cognitive accessibility. It’s about ensuring that the ‘path’ through an application is as clear as a marked trail in a forest. If you have to explain the design, the design has already failed. If the user feels stupid, you are the one who failed the IQ test. We aren’t building art; we are building tools. And a tool that hides its own handle isn’t a masterpiece-it’s a hazard.

As I walked into the kitchen to make a coffee, I noticed the clock on the microwave. It has a physical knob. You turn it to 47 seconds, and you press ‘Start.’ There is no mystery. There is no ‘hamburger’ icon. It has survived 17 years of daily use because it respects the fundamental laws of human interaction. It doesn’t try to be a phone. It doesn’t try to be ‘intuitive.’ It just is. Perhaps we should spend less time trying to make our software ‘smart’ and more time making it honest. Because at the end of the day, when the glow of the screen fades, all we really want is to know where we are and how to get where we’re going without feeling like the world has left us behind in a pane of glass.