CX vs UX
Key Takeaways
- UX is the quality of using one product. CX is everything a customer experiences with the company. - Every UX problem is a CX problem. Most CX problems are not UX problems. - The dividing line is who has to change: if the fix ships in the interface, it is UX work. - UX has a clear owner in most companies. CX ownership is the reason CX programmes stall.
User experience is the quality of using a specific product, service or interface. Customer experience is the whole relationship: the ad that set the expectation, the signup, the invoice, the support queue, the renewal, and the product in the middle of it.
The two get confused because they overlap where customers spend most of their attention. A person struggling with a checkout flow is having a bad UX and a bad CX at the same moment. The difference shows up in what it takes to fix.
CX
UX
billing
support
policy
renewal
A boundary test that works
Ask where the fix lands.
If the fix is a change to a screen, a flow, a label or an interaction, it is UX work, and a product team can ship it. If the fix requires someone outside the product team to change how they work, a policy to change, a handoff to be rebuilt, or a price to move, it is CX work.
Run that test on a real complaint and it separates cleanly. “I could not find the export button” is UX. “I was told three different things by three different people” is CX. “The trial ended without warning and my data was locked” is CX with a UX component: the warning could have shipped in the product, but the policy that locks data did not come from a designer.
What each discipline measures
UX teams measure task success, time on task, error rates and usability test results. The unit of analysis is a task.
CX teams measure satisfaction and effort at journey stages, retention, and the volume and cost of contacts. The unit of analysis is a relationship over time.
This is why the two functions can report opposite results in the same quarter. A redesign can lift task success while retention falls, because the reason people leave has nothing to do with the interface.
CX
UX
Scope
The full relationship across every touchpoint
One product, service or interface
Unit of analysis
A journey over time
A task
Typical owner
Shared across service, product, marketing and operations
Product and design
Typical measures
Satisfaction and effort by stage, retention, contact volume
Task success, time on task, error rate
Fix ships as
Policy, process, staffing, product change
A product change
Who owns which decision
UX decisions have an owner in almost every company: a design team inside a product organization.
CX decisions frequently have none. The work crosses service, billing, product, marketing and operations, so improving it means asking a team outside your reporting line to change something they are already measured on. That is the reason CX programs stall, and it is a governance problem rather than a research problem.
FAQ
Yes. UX is one component of customer experience, covering the product moments. CX includes those moments plus everything around them.
Yes, and it is common. Rewriting a refund policy, changing how a handoff works between two teams, or publishing pricing that was previously hidden are CX improvements that never touch the interface.
Rarely. UX belongs with the product team that ships the interface. CX needs an owner senior enough to change process across functions, which is a different job.