User experience is the overall experience a person has while using a product, shaped by usefulness, clarity, effort, trust, performance, accessibility, and how well the product handles success and failure.
User experience is what happens when product decisions meet a real person trying to accomplish something.
Consider a file upload. The default screen might be clear and visually polished. But the experience also includes what happens when the file is too large, the network drops, the user lacks permission, the upload partially succeeds, or the user comes back later.
Those moments collectively shape whether the product feels dependable or frustrating.
Does the product solve a problem that matters to the user?
Can the user complete the intended task effectively and without unnecessary effort?
Does the product respond quickly and predictably enough for the context?
Does the user understand what will happen, especially around money, permissions, data, and irreversible actions?
Can people with different abilities and ways of interacting use the product?
Do labels, instructions, confirmations, and errors make the product’s meaning clear?
When something goes wrong, can the user understand the problem and continue?
User experience is the experience itself.
UX design is the practice of researching, structuring, designing, testing, and improving the product in order to influence that experience.
A useful analogy is health and medicine: health is the condition, while medicine is one discipline used to improve it.
The user interface is the surface a person interacts with. User experience is what it is like to use the product through that interface over time.
A clean UI can still produce poor UX if a payment fails without explanation, a workflow is too slow, or an important setting is impossible to find.
Usability is an important part of user experience, but it is narrower.
A tool can be easy to use and still create a weak overall experience if it solves the wrong problem, feels untrustworthy, performs badly, or creates unwanted consequences.
No single metric captures the entire experience. Teams usually combine several kinds of evidence:
Metrics need context. A longer session can indicate engagement in one product and friction in another.
Visual quality matters, but an attractive interface cannot compensate for broken logic.
Users experience transitions, waiting, previous choices, and consequences across screens.
The way a product handles errors often matters more to trust than the happy path.
What users say should be compared with what they can actually do and what they continue doing.
Removing friction from one step can create confusion or risk later.
Parts of it are perceived differently by different people, but teams can still measure task success, behavior, error rates, performance, and recurring patterns.
No single function owns all of it. Product, design, engineering, content, support, operations, and leadership decisions can all affect the experience.
No. Customer experience usually includes the wider relationship with a company, such as sales, billing, support, and service. UX is often focused more directly on using the product.
User experience is the accumulated answer to a user’s question: what is it like to rely on this product to get something done?
Every useful shortcut, confusing label, delay, state, and recovery path contributes to that answer.
UX design · User interface · Product design · Interaction design · Usability
For a deeper product-level example, read The Unseen Layers of App User Experience.