UX (User Experience)
May 31, 2026 Reading time ≈ 7 min
What is UX
UX (User Experience) is the sum of impressions, thoughts, and emotions a user has while interacting with a product, service, or system.
It is not just "is the button easy to click" - it is the entire journey: from the first touch to completing the task.
Bad UX - people leave before reaching their goal.
Good UX - they solve their task without friction and come back.
UX is connected to customer experience (CX), usability, and the customer journey. It is measured through metrics (GCR, abandonment rate), surveys (SUS, SEQ, NPS), and usability tests. In SurveyNinja you can run surveys about how convenient a product is - after purchase, sign-up, or using a feature. More on this - UX in research.
UX is not only the interface. It is the perception as a whole: speed, clarity, predictability, emotional response.
Definition
UX (User Experience) - the holistic experience of a user when interacting with a product, system, or service. It covers usability (the ease of reaching goals), perception (aesthetics, trust), efficiency (speed, number of steps), and emotions. UX is focused on the user's tasks: "can they reach their goal quickly and without frustration?". Its link to CJM - the experience at every stage of the journey affects the overall outcome. It is measured through feedback, satisfaction surveys, usability tests, and behavioral metrics. Its link to NPS, CSAT, CES.
In short: "how a user feels when using a product" - from the first click to the result.
Why measure UX
Reduce churn - a bad experience at checkout, sign-up, or setup leads to abandoned carts and product churn. Prioritize improvements - metrics and surveys show where the journey "breaks". Compare options - an A/B test with UX metrics (GCR, SEQ) helps choose the better scenario. Prove the value of UX - numbers for management: "after simplifying the form, GCR rose by 15%". A user focus - without measurement the team relies on assumptions, with measurement - on data.
UX vs UI vs usability
UI (User Interface) - the visual part: buttons, forms, menus. UX is broader - it includes the UI, but also logic, scenarios, expectations, and context.
Usability - the ability of a product to be effective, efficient, and satisfying in its context of use (ISO 9241). UX includes usability plus the emotional component, trust, and value.
UX - the overarching concept. You can have a beautiful UI and bad UX - if the user does not understand where to click, or the process takes too long.
How to measure UX
Behavioral metrics.GCR - the share of those who completed the task out of those who started. Abandonment rate - where people drop off. Completion rate - how many finished the scenario. Conversion - how many reached the goal out of everyone. Analytics shows "where it breaks", surveys show "why".
Satisfaction surveys. NPS - "would you recommend it?". CSAT - "how satisfied are you?". CES - "how easy was it?". Short surveys after key actions: purchase, sign-up, contacting support.
Usability scales.SUS (System Usability Scale) - 10 questions, score 0-100. SEQ (Single Ease Question) - one question after a task: "How easy was it?". UEQ (User Experience Questionnaire) - 26 items across six dimensions. UMUX-Lite - a short version for quick measurements.
Usability testing. Observing users: you give a task and watch where they stumble. A qualitative snapshot - specific problems. Combine it with surveys: the test reveals "what", the survey - "how bad" at scale.
Questions for a UX survey
SEQ. "How easy was it to complete the task?" - a 1-7 scale. Short, right after the action. A good predictor of scenario success.
NPS. "Would you recommend the product to friends?" - 0-10. A single question about loyalty, tied to the overall experience.
CES. "How easy was it to [interact with the company / place an order / find information]?" - for scenarios with friction.
Open-ended. "What got in the way?", "What would you improve?", "What did you like?" - qualitative feedback. Combine them with SEQ or NPS: first the rating, then the open question.
2-5 questions - a typical length for a post-action survey. Longer - a risk of fatigue and a low completion rate. SUS (10 questions) - when you need a comparable usability score against benchmarks.
Link to CJM and persona
Customer Journey Map - the user's path from awareness to goal. At each stage there are its own expectations, touchpoints, and possible friction points. The UX team optimizes the experience at the key stages. Persona - who we are optimizing for. Different personas - a different experience: a beginner and an expert, a mobile and a desktop user. Segment your surveys - compare UX across segments.
Common mistakes
Designing for yourself. Developers and designers know the product. The user does not. Test on real users, not on colleagues.
Metrics alone without context. GCR dropped - but why? Surveys and usability tests give the "why". Metrics are a signal, qualitative methods are the explanation.
A survey after a long scenario. 20 steps, and at the end "Rate the convenience" - the respondent is tired or has already forgotten the details. Survey after a specific task or run a short SEQ right away.
Ignoring mobile users. UX on desktop and in a mobile app is different. Separate measurements per platform.
Too early or too late. A survey a week after the action - the respondent has forgotten the details. Right after - they may be under the influence of emotions. The optimal point is within minutes or hours of completing the task.
Example: why survey after checkout
An online store. Analytics: 60% of those who add to cart drop off before paying. Checkout GCR - 40%. It is unclear why. They launched a short survey after a successful payment and after an abandoned cart (email after 2 hours). SEQ + "What got in the way?" / "What would you improve?". Result: 35% pointed to "a complicated delivery form", 28% - "delivery cost that was not obvious until the end". They simplified the form and moved the delivery cost to the cart stage. A quarter later GCR rose to 55%. The survey provided direction - without it they would have been guessing blindly.
UX surveys in SurveyNinja
Create a survey after a target action: placing an order, signing up, using a feature. Questions: SEQ ("How easy was it?" 1-7), NPS, an open-ended "What got in the way?" or "What would you improve?". Hidden variables - pass the traffic source, page, and interface version for segmentation. A short survey - 2-5 questions - means a higher completion rate. A long SUS - when you need a comparable usability score. Export to Excel - analysis by cohorts and sources.
Link to product and CustDev
Customer Development - testing hypotheses through conversations with users. UX research complements it: testing prototypes, evaluating scenarios, uncovering pain points. Qualitative methods - interviews, usability tests - give depth. Quantitative surveys give scale and trends. Both are needed for a full picture of UX.
Case: SUS before and after a redesign
A SaaS service for accountants. A redesign of the dashboard - new navigation, simplified forms. Before: SUS 52 (below average, benchmark 68). A survey of 200 active users. After the redesign - SUS 71. Separately they surveyed those who switched to the new version in the first month: an open question "What was confusing?" - frequent answers were "finding reports", "setting permissions". They reworked those blocks. The next measurement - SUS 76. A regular SUS made it possible to measure the effect of the redesign and find points for targeted improvements.
When to run UX surveys
After key actions: placing an order, signing up, the first setup, contacting support, canceling a subscription. During a redesign - before and after, to measure the effect. During an A/B test - a survey as a complement to metrics: not only "which version converts better", but also "which one feels simpler". Once a quarter or every six months - a general survey about the product experience (SUS, NPS) for trends. Do not survey everyone indiscriminately - choose relevant moments and segments.
UX (User Experience) - the holistic experience of a user when interacting with a product. It is measured through metrics (GCR, abandonment), surveys (SUS, SEQ, NPS), and usability tests. Its link to CJM, persona, CX. In SurveyNinja - surveys about convenience after key actions.
Published: May 31, 2026
Mike Taylor