In this episode, discover the UX Pathway that Eric Meyer followed, a Web Standards Advocate at Igalia.
Big Take Away
If I boiled the entire interview down to one UX principle, it would be: Don’t make the user solve the problem you could solve for them. And a second principle follows: Your job isn’t simply to create an interface. Your job is to absorb complexity, anticipate change, and make the experience easier for the people who depend on what you create.
1. Help people. That is the throughline.
This is probably the strongest theme in the entire conversation.
Eric repeatedly describes himself as “support class”. Whether he is writing documentation, creating CSS support charts, answering questions, building tools, writing books, or helping colleagues, his instinct is to take something difficult and make it easier for someone else.
His career advice ultimately comes down to:
“If you can find ways to help people…”
He sees helping as one of the most fundamentally human things we do.
And he connects this to the idea of standing on the shoulders of giants: we benefit from what others have shared, and our responsibility is to give other people something they can stand on.
Big idea:
Your career doesn’t have to start with building a personal brand. Start by being useful.
2. Put the burden on yourself, not the user
This may be the most important UX principle to come out of the conversation.
Eric references Jeremy Keith’s formulation:
If a problem can be placed on either the user or the developer, put it on the developer.
For Eric, that’s the job. Developers and designers are supposed to deal with complexity so users don’t have to.
This idea shows up repeatedly:
- CSS support charts removed complexity for developers.
- His CSS books removed the need for readers to decipher specifications.
- Responsive design removes device-detection decisions from users.
- His browser-based banner tool removes technical requirements from coworkers.
- Professional translation removes the burden of deciphering bad machine translation from readers.
Big idea:
Don’t make users participate in the complexity of your system.
3. It’s not your fault. But it is your responsibility.
This is one of the strongest lines in the interview conceptually.
Technology changes. Devices change. Screen sizes change. Browsers change. Interfaces get disrupted by things you didn’t anticipate.
Eric’s point is that you may not be responsible for causing the change, but you are still responsible for dealing with its impact.
That is a powerful distinction for UX:
Fault asks:
“Who caused this?”
Responsibility asks:
“Who is going to make this work for the person using it?”
This applies well beyond technology.
4. UX is bigger than the interface
Eric gives a very simple definition of UX:
“It’s the experience that a user of a thing has.”
But he immediately expands that beyond design. UX includes the context in which the design is experienced.
His car touchscreen example makes this especially clear.
A touchscreen might have an excellent interface, but putting that interface into a moving vehicle can create a terrible, even dangerous, experience.
So:
Good UI ≠ Good UX
Context matters.
Environment matters.
Stress matters.
Physical limitations matter.
Consequences matter.
Big idea:
You cannot evaluate an experience by looking only at the interface.
5. Design for people when things go wrong
The beach/mobile phone story and the discussion about forms reinforce another important theme: people don’t use technology under ideal conditions.
Forms are difficult under normal circumstances. Put someone in a high-stress situation and those problems become dramatically worse.
This connects directly to Eric’s broader philosophy:
The people using our products aren’t always sitting comfortably at a desk with plenty of time and attention.
They may be:
- stressed
- distracted
- confused
- using a different device
- dealing with an emergency
- operating under physical constraints
- encountering something the designer never anticipated
Big idea:
The real test of an experience isn’t necessarily how it works when everything goes right. It’s how it behaves when life gets messy.
6. Build things that remove friction
Eric doesn’t just talk about helping. He repeatedly builds things to make helping easier.
The CSS support chart is a great example.
He didn’t simply complain that browsers implemented CSS inconsistently. He:
- Tested the browsers.
- Documented the results.
- Created a database.
- Built a publishing system.
- Made the information available to everyone.
Later, he created a browser-based banner maker because requiring everyone to have a Mac and know Keynote created unnecessary barriers.
Big idea:
When you encounter recurring friction, don’t just work around it. Build something that eliminates it.
7. Share what you learn
Eric’s career essentially became a feedback loop:
Learn → solve → document → share → help people → become known → get new opportunities → learn more
His CSS support chart led to articles.
The articles led to O’Reilly.
The book led to speaking opportunities.
Speaking and community involvement created more connections.
This is particularly interesting because Eric didn’t initially set out to build a personal brand.
He was simply sharing what he had learned.
Big idea:
Teaching can be a career accelerator without being the goal.
8. Luck matters more than we like to admit
Eric is unusually candid about this.
He acknowledges hard work, knowledge, and talent, but repeatedly says luck played a significant role in his career.
The timing mattered enormously.
He entered the web when:
- the community was small
- there were only a handful of places people gathered
- useful information could quickly gain attention
- CSS was new
- the web itself was still emerging
He explicitly says that if he had started ten years later, the same pathway probably wouldn’t have existed.
Big idea:
Career success isn’t purely meritocratic. Hard work matters, but timing, access, connections, circumstance, and luck matter too.
9. Don’t confuse today’s path with tomorrow’s path
Eric makes an important distinction when giving career advice.
He says his specific career path is closed because the conditions that created it no longer exist.
But the principle behind the path remains available.
You probably can’t become “the next Eric Meyer” by repeating what Eric did.
But you can:
- find problems
- solve them
- help people
- share what you learn
- build a reputation around being useful
Big idea:
Don’t copy someone’s career. Copy the principles that made their career work.
10. AI should be evaluated by who carries the burden
This is where the AI discussion connects directly back to the UX philosophy of the entire interview.
Eric isn’t simply “anti-AI.” His objection is to using technology in ways that push problems onto users.
He argues that much of what is currently called AI is actually LLM-based autocomplete, and that LLMs are being applied to problems they aren’t necessarily suited for.
His translation example is particularly relevant:
Company:
“We need this in four languages.”
Bad solution:
Run it through an LLM.
Now the reader has to deal with the mistakes.
Better solution:
Put the burden on the organization and have it professionally translated.
Big idea:
The question isn’t simply “Can AI do this?”
The better UX question is:
“Who experiences the consequences when AI gets it wrong?”
11. Use technology where it is actually good
Eric makes an important distinction between different kinds of AI.
He points to speech recognition such as Whisper as an example of AI being extremely useful for a specific task. He also sees potential in translation when multiple technologies are combined appropriately.
His argument isn’t “don’t use AI.”
It’s closer to:
Use the right technology for the right problem.
Don’t automatically put an LLM in front of every problem simply because it’s currently fashionable.
12. The web keeps changing, so adaptability is part of the job
Eric’s career spans enormous technological changes:
CSS
→ browsers
→ web standards
→ responsive design
→ mobile
→ new screen sizes
→ new interaction models
→ AI
The web is particularly difficult because unlike print or television, its “canvas” never really settles.
Top Themes:
- Be the helper.
- Put the burden on yourself, not the user.
- It’s not your fault, but it is your responsibility.
- Share what you learn.
- Don’t follow someone else’s path. Follow the principles that made the path work.
Leave a Reply