Forrester Research has published estimates that put the return on UX investment as high as $100 for every $1 spent — a number worth treating as illustrative rather than gospel, since ROI varies wildly by product and the methodology behind these figures is rarely disclosed in full. But the direction of the claim holds up across almost every account from teams who've actually measured it: fixing a usability problem before launch is dramatically cheaper than fixing it after thousands of people have already hit it. That gap is the entire business case for UX.
"UX" gets used as if it's a team, a phase, or a deliverable. It's really a set of questions applied continuously throughout a product's life:
These questions apply whether or not a company has anyone with "UX" in their title. A three-person startup answering "does the person using this understand what to do next" honestly, every time it ships something, is doing more real UX work than a ten-person team with a dedicated UX department that never asks the question at all. The title is a resourcing decision; the practice is a habit.
Jakob Nielsen published these in 1994 and they've held up remarkably well as a checklist for evaluating any interface:
Most teams have more UX problems identified than time to fix them. A common prioritization method is RICE — Reach (how many users are affected), Impact (how much it affects them), Confidence (how sure you are about the first two numbers), and Effort (how long it takes to fix), combined into a single comparable score. A fix that affects 80% of users with high impact and low effort will always outrank a fix that affects 2% of users, even if the second one is more interesting to work on. For example, a fix reaching 10,000 of 12,000 monthly users with high impact and two days of engineering effort scores far higher under RICE than a fix reaching 200 users with the same impact and effort — even though the second fix might be more interesting to build.
"Good UX" doesn't mean the same thing in every context, because the cost of confusion varies enormously by industry. In consumer social apps, the priority is usually reducing friction to the point of near-invisibility — every extra tap between a user and the core action (posting, swiping, scrolling) measurably hurts engagement, so UX work there leans heavily on micro-optimization and testing. In fintech and healthcare, the priority shifts toward trust and error prevention — a confusing step during a wire transfer or a medication dosage entry isn't just an inconvenience, it's a liability, so UX work there leans toward redundant confirmation, clear error states, and conservative design choices over novelty.
Enterprise B2B software sits somewhere in between: users are often required to use the tool for their job regardless of how it feels, which removes some of the competitive pressure toward polish, but the complexity of the underlying workflows makes information architecture the dominant UX challenge rather than micro-interactions. A UX designer moving from a consumer app to an enterprise tool often has to unlearn the instinct to simplify everything down to one obvious action, because enterprise users frequently need power and configurability that a stripped-down consumer flow would hide.
The Baymard Institute's ongoing checkout research has tracked average cart abandonment rates around 70% across e-commerce sites for years, and a meaningful share of that is attributable to usability friction rather than price sensitivity — unnecessary account creation requirements, unclear shipping costs, and confusing form validation being recurring, fixable causes. Treat the exact percentage as directional; the pattern — that structural friction quietly costs more revenue than most teams estimate — is the part worth internalizing.
A concrete illustration: a mid-sized SaaS company found that "how do I reset my password" was consistently one of its top support ticket categories, despite a working reset flow. A review found the reset email was landing in spam for a meaningful share of users, and the confirmation screen gave no indication of what to do if the email didn't arrive. Two small fixes — a visible "check your spam folder" note, and a resend button with a countdown — cut that ticket category by roughly a third within two months, with no new features and no redesign required.
The most common pushback against investing time in UX questions is that there isn't time — the roadmap is full, the deadline is fixed, and asking "does this make sense" feels like an unaffordable luxury. In practice, the cheapest version of UX practice is not a luxury: reading the last twenty support tickets in a category before building a fix, or asking three colleagues unfamiliar with a feature to try it cold, takes under an hour and routinely catches problems that would otherwise cost days of rework after launch. The expensive version — formal research studies, dedicated headcount — is optional. The cheap version, treated as a non-negotiable habit, is where most of the actual return comes from.
None of this requires a UX title on an org chart. It requires treating "does this make sense to someone who didn't build it" as a real question, asked often enough that the answer stays honest.
They overlap but aren't identical. UX typically refers to the experience of using a specific product or interface. CX is broader — it includes UX plus everything else: sales interactions, support calls, billing, onboarding emails. Good UX is one input into good CX, not the whole of it.
By treating it as a practice rather than a role: running a handful of short user interviews before building a new feature, testing prototypes with 5 real users before shipping, and reviewing analytics for drop-off points after launch. None of this requires a specialized title, just deliberate time set aside for it.
Watch five real users attempt a core task without helping them. Wherever they hesitate, ask a clarifying question out loud, or click the wrong thing, you've found a UX problem — usually faster and more reliably than any amount of internal debate about what "feels off."