The assumption that technology becomes easier to use over time is a convenient lie. Professional builders create systems that solve their own problems. They do not create systems that solve the problems of the person at the other end of the wire. Innovation often functions as a mask for complexity. This mask allows the creator to feel clever while the user feels ignored.
Software designers live inside the logic of their own making. They spend eight hours a day navigating nested menus and symbolic icons. They begin to believe that a three-line icon is a universal symbol for a menu. It is not a universal symbol. It is a shorthand for people who have already been taught what it means.
The industry suffers from a false-consensus bias. Builders believe that their own fluency is the baseline for human intelligence. They mistake their specific technical training for common sense. If a user cannot find a button, the builder assumes the user is not paying attention. The builder rarely assumes that the button is hidden in a place that makes no sense.
CASE STUDY
The 3AM Interface Test
I spent this morning fixing a broken toilet at . The mechanism was a simple plastic float and a rubber flap. I understood the system because I have looked at many toilets. A person who has never seen the inside of a tank would find the parts confusing. They would see a chaotic arrangement of levers and water.
The designer does not expect the homeowner to be a plumber; the lever is the single point of contact.
The toilet designer does not expect the homeowner to be a plumber. The designer builds the tank so that the homeowner only has to push a single lever. The lever is the only point of contact. This is a successful interface. Most digital products require the user to open the tank and adjust the float just to get the water to run.
The Battle of Priorities
Digital builders prioritize the “edge case” over the “everyday case.” They add features that only five percent of people will ever use. These features clutter the screen for the other ninety-five percent. The interface becomes a battlefield of competing priorities. The user loses this battle every single time.
A designer sits at a desk and builds a registration flow. She has used this flow one thousand times during testing. She knows that the “submit” button will turn blue once the email is verified. She does not notice that the verification email takes to arrive. She does not notice because she is not waiting for it in a state of anxiety.
The actual user is often in a state of mild or high anxiety. They are trying to move money or find information or book a flight. They are worried about making a mistake. They are afraid that one wrong click will cost them a day of wages. The designer never accounts for this fear.
We see this gap most clearly in regulated industries where trust is the only real product. In these spaces, the user is looking for a sign that the system is stable. They want to know that their balance is accurate and their data is safe.
A platform like rca77 succeeds because it does not try to reinvent the wheel for the sake of a designer’s portfolio. It prioritizes the automated speed and the security that the user actually needs.
This person does not want to explore your “innovative” navigation system. They want to finish a task and go back to their life. They treat the screen like a tool, not a destination. Designers treat the screen like a canvas for their own artistic expression.
The Lessons of Animal Training
In my work as a therapy animal trainer, we rely on a process called shaping. We reward the animal for the smallest movement toward a desired behavior. We do not expect the dog to understand the final goal of the training session. We provide clear and immediate feedback at every step. If the dog is confused, we blame the trainer, not the dog.
Digital designers do the opposite of shaping. They provide a “tutorial” that the user skips because it is boring. They then drop the user into a complex environment without any feedback. When the user fails, the designer looks at the data and calls it “user error.” There is no such thing as user error in a well-designed system.
The Hierarchy of Error
The error is the assumption that the user is interested in the system at all. Most people do not want to “engage” with an interface.
They want the interface to disappear so they can reach the content on the other side. A bridge is successful when you do not think about the bridge while crossing the river.
The industry has built a lot of bridges that require the driver to stop and read a manual. These bridges are beautiful to look at from a distance. They are terrible to drive across when you are in a hurry. The builder sees the architecture. The driver sees the delay.
Expertise is a Blindfold
The more you know about how a thing works, the less you understand what it is like to not know. This is the curse of knowledge. It is a cognitive bias that makes it impossible to imagine what a beginner sees. Designers are the ultimate experts.
They see a “breadcrumb” and know it is a path to a previous page. A grandmother sees a list of words she did not type. They see a “modal” and know it is a temporary window. A cautious user sees a wall that has blocked their progress. The language of the builder is a foreign tongue to the resident.
A humble builder starts from the assumption that the user is tired and distracted. They assume the user has better things to do than learn a new layout. They design for the person who is trying to fix a toilet at .
Clarity vs. Minimalism
Simplicity is not a lack of features. Simplicity is the presence of clarity. It requires more work to make a system simple than it does to make it complex. Complexity is the natural state of any growing system. Clarity is a deliberate act of will.
We often mistake “minimalism” for simplicity. A screen with no buttons is minimal. It is also useless if the user does not know where to touch. True simplicity provides the right tool at the right time. It does not hide the tools in a drawer and ask the user to guess which drawer is which.
Hidden drawers & “clean” confusion.
Providing the right chair for the user.
The digital world is currently full of hidden drawers. We are told that this is “clean” design. It is not clean. It is empty. An empty room is only useful if you do not need any furniture. Most users are looking for a chair.
If you build a platform for everyone, you must design for the person who trusts the least. You must design for the person who has been burned by complex systems before. You must show them where their money is and how to get it back. Transparency is more important than a smooth transition animation.
The Language Gap
The industry will continue to fail as long as it hires people who love technology to design for people who just want to live. The two groups do not speak the same language. One group sees a playground. The other group sees a series of obstacles.
We must stop projecting the builder’s fluency onto the user’s experience. We must stop assuming that “obvious to me” means “obvious to everyone.” The gap between the creator and the consumer is where the frustration lives. That gap is a choice. We can choose to bridge it with humility.
“The lever is a promise to the homeowner but the float is a mystery to the plumber’s guest.”
Digital Obsolescence
The goal of any digital interface should be its own obsolescence. The best software is the software you use without realizing you are using it. You do not notice the oxygen in the room until it is gone. You should not notice the buttons on the screen until you need to press one.
When I train a dog to assist a person with a disability, I do not train the dog to be perfect. I train the dog to be predictable. Predictability is the foundation of trust. If the dog acts differently every time the door opens, the person cannot rely on the dog. Digital systems are often wildly unpredictable.
They change their layout during an “update.” They move buttons to increase “engagement” metrics. They hide the “cancel” button to prevent “churn.” These are the actions of a builder who views the user as an obstacle. A user is not an obstacle. A user is the reason the system exists.
Stable Tools for a Real World
We must return to the idea of the tool. A hammer does not change its shape while you are trying to hit a nail. A saw does not require a software update before it will cut wood. The tools we use in the physical world are stable and reliable. Our digital tools should be the same.
Market Specificity
A regulated environment like the Thai gaming market requires this stability. People are not there to admire the code. They are there for entertainment and the hope of a fair result.
They need the “fast deposit-and-withdrawal” to work every time without a hitch. If the system is too clever for its own good, it fails the person who is just looking for a moment of leisure.
The industry keeps building for the version of us that lives in a silicon valley office. It needs to start building for the version of us that is tired, or busy, or fixing a toilet at . That is the person who actually uses the world. That is the person who deserves a system that works.
We do not need more features. We need more empathy for the non-expert.
We need to remember that the person at the other end of the screen is not a builder. They are a human being trying to get something done. Let them do it. Get out of their way.
