Stop Saying “UI/UX”
TLDR: UI and UX are separate practices. “UI Designer” and “UX Designer” are two different roles. An individual can be a “UX Generalist” who practices research, requirements, conceptualization, AND visual design of pixel-perfect interfaces. Additionally, the order of the term “UI/UX” prioritizes visual design. Software and app design practice should always start with the UX process to understand and validate requirements before considering what it will look like.
Say UX first because “UX First”
About five years ago, I started to see the title “UI/UX Designer” pop up on job boards. Then, shortly after, I started seeing it on people’s resumes to cater to roles like that. And then, I began to hear it from clients’ and stakeholders’ mouths. The smashed-up title has always irked me because it is backward.
As a UX Generalist, I do both UX research and UI design, but the research always comes first. You need to understand what you are building before you can visualize what it will be. You do research first, then you create the interface — UX, then UI.
What “UI/UX” communicates to practitioners
When a potential client, a co-worker, or a stakeholder says “UI/UX,” I see it as a red flag. It communicates two things:
- You value the visual — what it will look like over what the product will do
- You don’t understand how the process works
If this describes you, that is OK! This is the reason I’m writing this article. Maybe people just don’t know, and they are willing to learn.
Think about why you say “UI/UX”
UX and UI are two separate practices. Some possible reasons that people conflate the two practices might be:
- People likely say “UI/UX” because that is what they have heard from others and haven’t thought much about it, or
- Some say “UI/UX” because they think the interface or the visual design is all we do (it’s not). I have run into plenty of people in my career who have thought that “UX is just glorified Graphic Design” (it’s not), or
- Both start with “U,” so that might lead some to think they are the same role
Let’s demystify that final bulletpoint.
“U”
The “U” might throw people off. In both cases, the “U” stands for “User”. Both practices center around creating products with the end user in mind.
“X”
The “X” is for “Experience.” It is a complicated word to be assigned to a title. What it means in this use is “Problem Solver.” Someone who goes into a situation with a lot of ambiguity performs research, clarifies, and documents both problems users have and requirements for how a product can solve those problems.
“I”
The “I” stands for “Interface”. This is the physical or digital thing that users interact with, like a software application or a banking machine. Interfaces don’t need to be complex, and they don’t need to look beautiful. However, users tend to assign more value to interfaces that look good.
The Difference
UX Designer = dives into complexity to define requirements for a product and what the shape of the product will be.
UI Designer = takes requirements and creates a good-looking interface for users to complete tasks.
Generalist = defines the problem, creates a functional interface, and makes it look good.
It clarifies the differences if you think about it compared to another practice. Architect / Interior Designer. Two roles. An Architect figures out the needs of the building, how many rooms, bathrooms, etc., defines the structure, and creates blueprints for Engineers to build from. An Interior Designer determines the look and feel of the interiors of the building — color, texture, switch colors, etc.
Conclusion
The practice of User Experience and User Interface Design are two separate roles. Combining them by saying “UI/UX” communicates to those who work in either that you don’t fully understand what you are asking for. It is essential to start with research, understanding, and empathy for the people using the product. This is “UX,” and it should always happen at some scale before starting any aesthetic design. If you must combine the two titles, the order is “UX/UI,” but really, it is “UX > UI” or “UX” then “UI” — no slash needed.
It would be best to understand what you are asking for and when. You need “UX” when you need research to understand more about what needs to be built or improved, to create and increase confidence in project requirements, and to test these requirements back with the users’ needs and the business’s wants. You need “UI” after you have defined product requirements validated with users and vetted with your engineers. This is where they will apply existing design systems and create high-fidelity designs for the intended final product.
The images used in this article were created using MidJourney
