Introduction
Customer experience (CX) is a customer's overall perception of a company, formed by the cumulative effect of every interaction across products, service, marketing, and support. A customer's relationship with a company is not one interaction but a hundred: the ad, the trial, the invoice, the support chat, the product itself, the cancellation flow. Customer experience is the sum of those encounters as the customer perceives them, and CX is the discipline of understanding and improving it across every touchpoint, not just the ones product teams own. It overlaps with user experience and is regularly confused with it. This article covers what CX means, how it differs from UX, the metrics and methods it runs on, and how experience research feeds it.
What is Customer Experience?
Customer experience (CX) is the customer's overall perception of a company, formed by the cumulative effect of every interaction with it, across channels, departments, and time. The definition that shaped the field came from a 2007 Harvard Business Review article by Christopher Meyer and Andre Schwager, which framed customer experience as the customer's internal and subjective response to any direct or indirect contact with a company: direct contacts like purchase and service, indirect ones like advertising, reviews, and word of mouth. Two features of that framing matter. CX is perceived, so the customer's account is the measure, not the company's process map; and it is cumulative, so a brilliant product wrapped in a hostile billing experience still yields poor CX.
CX and UX
User experience concerns a person's interaction with a specific product or service; customer experience concerns the whole relationship with the organization. UX is a subset: the product's usability, utility, and pleasure are a major component of CX, alongside sales, support, pricing, communications, and brand. The teams differ accordingly. UX research lives with product and design and studies behavior inside the product, often through testing and interviews; CX programs usually sit with marketing or a dedicated experience function and study the relationship through journey mapping, voice-of-customer feedback, and relationship metrics. The confusion is expensive when a great UX score is read as great CX (users love the app and hate the company) or when CX metrics are used to judge design details they're far too coarse to see.
The Metrics and Their Limits
CX runs on three families of survey metric. NPS (likelihood to recommend, a relationship-level loyalty proxy), CSAT (satisfaction with a specific interaction, asked immediately after it), and customer effort score (how easy the company made it to resolve a need, a strong predictor of loyalty in the service context). Each is a single-item proxy for a latent construct, with the limits that implies: sensitive to timing and framing, vulnerable to response bias and who answers, and useless without the verbatims and follow-up that explain movement. Operational data (churn, repeat purchase, support contact rates) supplies the behavioral counterweight, and the honest CX program triangulates the two.
Improving CX Through Research
1. Map the journey from the customer's side.
Stages, touchpoints, emotions, and pain points as customers experience them, built from research rather than from org charts; the map's value is in the handoffs between departments that nobody owns.
2. Instrument the moments that matter.
Transactional metrics at key touchpoints, relationship metrics on a cadence, with open-ended questions attached so that scores arrive with reasons.
3. Close the loop.
Feedback that changes nothing trains customers to stop giving it; the program's credibility rests on visible responses, individually (following up detractors) and structurally (fixing what the themes reveal).
4. Go deeper where the metrics point.
A dip at a touchpoint is a research prompt: interviews with the affected customers, or a quick study walking through the interaction on video, to learn the mechanism. Platforms that let a CX team recruit real customers and collect recorded answers in days (the shape of a Ballpark study) make this loop fast enough to run on every significant movement.
5. Connect experience to outcomes.
Analyze which experience factors predict retention and expansion (driver analysis), so investment follows evidence rather than the loudest complaint.
In Short
Customer experience is the whole relationship as the customer perceives it, cumulative across every touchpoint, with product experience as one large part. Map it from the customer's side, measure the moments with metrics that carry their reasons, close the loop visibly, research the mechanisms behind movement, and tie experience to outcomes. UX makes the product good; CX asks whether the company is, and only the customer can answer.
Further reading
For the discipline's foundations:
Articles:
1. Understanding Customer Experience - Harvard Business Review
Meyer and Schwager's defining article: what CX is, why companies misread it, and how to build the monitoring that reveals it.
2. UX vs. CX - Nielsen Norman Group
The clearest short treatment of where user experience ends and customer experience begins.