One of the strangest experiences in technology is watching somebody use a system you've built.
Everything seems obvious.
Until it isn't.
You know where the button is.
They don't.
You know what the error message means.
They don't.
You know which field is required.
They don't.
Within minutes, somebody who has never seen your product will find a completely different way to interpret it.
And that's usually where the real design work begins.
The people building a system understand it better than anyone else.
That sounds like an advantage.
Often it's the source of the problem.
Once you know how something works, it becomes surprisingly difficult to imagine not knowing.
You stop seeing decisions.
You stop seeing assumptions.
You stop seeing the invisible knowledge you've accumulated along the way.
The interface feels obvious because your brain is filling in all the missing context.
Users don't have that luxury.
They only see what's in front of them.
A button is a prediction.
A menu is a prediction.
A workflow is a prediction.
Every design decision contains an assumption about what somebody will do next.
Most usability issues happen when those predictions are wrong.
The designer expects one path.
The user takes another.
The designer expects one interpretation.
The user sees something completely different.
Neither side is irrational.
They're simply operating with different information.
Designers often study screens.
Users study outcomes.
They aren't interested in navigation structures.
They want to submit the form.
They aren't interested in information architecture.
They want to find an answer.
They aren't interested in elegant interaction patterns.
They want to finish the task and get on with their day.
This sounds obvious.
Yet many products are still designed around how the system works rather than how people think.
When enough users make the same mistake, something interesting happens.
The mistake stops being theirs.
It becomes yours.
If one person struggles, perhaps they weren't paying attention.
If hundreds of people struggle, the interface is telling a different story than the one you intended.
Good design isn't about preventing every error.
It's about making the right action feel like the natural one.
Accessibility is often discussed as a checklist.
Contrast ratios.
Keyboard navigation.
Screen reader support.
Those things matter.
Underneath them sits a deeper idea.
Accessibility asks a simple question.
Who did we assume would use this?
Every time a product excludes someone, there is usually an assumption hiding underneath the decision.
The more assumptions we make about users, the smaller the audience becomes.
Think about products people love using.
Most don't feel impressive because they contain more features.
They feel impressive because they remove uncertainty.
People know where to click.
They know what happens next.
They know how to recover if something goes wrong.
The complexity still exists.
It's simply been hidden behind thoughtful design.
That is much harder than adding another feature.
Every usability session eventually produces the same feeling.
Humility.
A user will misunderstand something that seemed impossible to misunderstand.
A workflow that felt elegant suddenly looks confusing.
A feature you were proud of goes completely unnoticed.
These moments can be uncomfortable.
They're also incredibly valuable.
Because users are not revealing flaws in themselves.
They're revealing blind spots in our assumptions.
The name suggests a relationship between people and technology.
In practice, it's often a relationship between people and the people who built the technology.
Every interface contains decisions.
Priorities.
Assumptions.
Beliefs about how users behave.
The computer simply delivers those decisions.
That's why great design feels empathetic.
Not because it is technically sophisticated.
Because somebody took the time to understand what another person might experience.
Technology keeps changing.
Screens change.
Devices change.
Interaction models change.
The underlying challenge remains remarkably consistent.
Can you understand a person whose experience is different from your own?
Every successful interface answers that question a little better.
And every frustrating interface reminds us what happens when we stop asking it.