The pairing comes up constantly in job descriptions, project kickoffs, and team conversations: “UI/UX design.” Almost always in that order. And almost always with the assumption that UI is the visual stuff – colors, fonts, layout – while UX is… something related to usability, maybe.
I want to push back on that, because the order matters, and the definitions people use tend to miss the point entirely.
UX Is Not About the Screen
User experience is about a person’s life. Not just the few seconds they’re looking at your application.
Think about ride-sharing apps. Before Uber and Lyft, getting somewhere meant standing outside, waiting for a cab that might or might not show up. You didn’t know who the driver was. You didn’t know the route they’d take. You weren’t sure if they’d accept your form of payment. There was real anxiety in that experience, and most of it had nothing to do with an app.
What made those services genuinely good wasn’t the color of a button. It was that they removed anxiety from a real-life situation. You know in advance who’s picking you up, what their rating is, exactly when they’ll arrive, and your payment is already handled. You can sit down and keep working or reading without glancing out the window every thirty seconds.
That is user experience. A person living their life, having an interaction with a service, and continuing to live their life. The experience wraps around the entire moment, not just the screen.
UI Is About the Conversation
User interface, on the other hand, is specifically about how a person communicates with a system. What information are you giving it? What is it giving back to you?
If the color red on your bank statement means you’re below your balance, that’s UI. Not because red looks nice, but because it’s the system communicating meaning to you. The interface is the conversation.
Here’s a concrete example I use when explaining this: say a customer service rep needs to look up a customer, but the system only allows that lookup by driver’s license number. The person standing at the counter has their passport (yes, they’re at an airport, and the passenger has buried their driver’s license away!). There’s no way to proceed. That’s a UI failure. Not a visual failure. A conversational failure. The system couldn’t receive the information the person actually had.
Who enters what, and what the system says back — that’s the interface. Colors are just decoration unless they’re carrying meaning in that conversation.
Why the Order Matters
UX comes before UI, because you have to understand the experience you’re trying to create before you can design the interface that enables it.
In the ride-sharing example: the experience we’re optimizing for is reducing commuter anxiety. That goal, once understood, starts driving specific interface decisions. Can someone book a ride on behalf of another person? What happens if the passenger doesn’t have their phone? Those questions don’t come from graphic design. They come from thinking about the experience first.
In our work, user stories drive this. The “in order to” part of a story captures the value — the experience we’re trying to give someone. The “as a / I want to” part describes how they’ll interact with the system to get there. Experience first, then interface.
And Then, Maybe, the Colors
Visual design matters. But it earns its place at the end of this sequence, not the beginning. Once you know what experience you’re creating and how a person will interface with the system to get there, visual choices become purposeful rather than decorative.
The mistake is skipping the first two layers and going straight to “make it look good.” You can build something that looks polished and still creates the exact anxiety you were supposed to eliminate, because you never asked who needs what, when, or why they might be standing at a counter with a passport instead of a driver’s license.
What I’m learning is that the experience doesn’t live in the software. It lives in the person using it, before and after they ever touch a screen. The interface is just where we have our brief conversation with them.
Leave a Reply