What UX Design Actually Is

UX design has become one of the most sought-after creative careers to switch into. It blends problem-solving, psychology, and design; it pays well (US salaries commonly range from roughly 80,000 dollars into the 150,000-plus range with experience, per industry salary surveys); and the US Bureau of Labor Statistics projects employment of web and digital interface designers to grow about 7 percent from 2024 to 2034, faster than average. It also welcomes switchers from many fields, psychology, marketing, graphic design, writing, research, customer support, because understanding people is as central as any tool.

But UX is widely misunderstood. Many newcomers think it means "making things pretty" in a design app, which is a small and late part of the real work. Starting with the wrong picture makes it hard to learn the craft or break in.

This cursus builds an accurate, practical understanding of the field:

• This lesson: what UX design actually is, and how the work is structured.
• Research (Lesson 2): understanding users and defining the real problem.
• Design (Lesson 3): information architecture, wireframes, prototypes, and UI basics.
• Evaluation (Lesson 4): usability testing, heuristics, accessibility, and how to break in.

We start by defining UX and clearing up its most common confusion, the difference between UX and UI, because that distinction shapes everything about how the job is understood.

UX stands for user experience: how a person feels and what they are able to do when they use a product. The term was coined by cognitive scientist Don Norman, whose book The Design of Everyday Things is a foundation of the field. His key idea is broader than screens: good design is about how well a thing works for the human using it, whether that is a door, a stove, or an app.

UX design, then, is the practice of designing products so they are useful, usable, and satisfying for the people who use them. It spans the entire experience:

• Useful: does it solve a real problem the person has?
• Usable: can they accomplish their goal easily, without confusion or frustration?
• Satisfying (even delightful): is the experience pleasant rather than annoying?

Norman's famous everyday example is a door you cannot tell whether to push or pull, a "Norman door." The failure is not the person's; it is the design's, because it gave the wrong signals. That reframing is the heart of UX: when users struggle, blame the design, not the user. A good experience makes the right action obvious and the task effortless.

Crucially, UX is about far more than looks. A beautiful product that is confusing to use has bad UX; a plain one that is effortless has good UX. UX concerns the whole journey, can users find what they need, understand it, complete their goal, and feel good doing it, which is why it starts long before anyone opens a design tool.

The most common confusion in the field is between UX and UI, often lumped together as "UI/UX." They are related but distinct.

• UX (user experience) is the overall experience and how the product works for the user: the structure, the flow, whether it solves the problem, whether tasks are easy. It is about how it works.
• UI (user interface) is the visual and interactive surface the user touches: the layout, colors, typography, buttons, icons, spacing. It is about how it looks and feels to interact with.

An analogy: in a house, UX is the architecture, does the layout make sense, are the rooms where you need them, does living there work; UI is the interior design and finishes, the paint, fixtures, and style. You need both. A gorgeous interior in a badly laid-out house is frustrating to live in; a great layout with ugly, inconsistent finishes feels unpleasant and untrustworthy.

Some designers specialize in one; many roles, especially at smaller companies, expect both, hence "UI/UX designer." For a switcher, the key point is that UX is the foundation and UI is built on it. This cursus centers on UX thinking, the research, structure, and usability that make a product genuinely work, and covers UI fundamentals as the layer that expresses it well.

The core philosophy of UX is user-centered design: you design for the actual people who will use the product, based on understanding their needs, not for yourself and not for what the team assumes.

This sounds obvious but is constantly violated, because of a trap every designer must overcome: you are not your user. Designers know their product deeply, are comfortable with technology, and understand the intended logic, so what feels obvious to them is often confusing to real users who lack all that context. Designing from your own intuition quietly builds products that work for you and fail for everyone else.

User-centered design counters this with a discipline:

• Understand real users: who they are, their goals, their context, and their frustrations, learned by studying them, not guessing (the subject of Lesson 2).
• Design for their needs and mental models, the way they expect things to work, not the way the system happens to be built.
• Test with real users and let their behavior, not the team's opinions, judge whether the design works (Lesson 4).

The mindset shift is humbling and powerful: your opinion about the design matters far less than how real users actually respond to it. A UX designer replaces "I think this is intuitive" with "let's find out how users experience it." This evidence-over-ego stance, grounding design in real user understanding rather than internal assumptions, is what most separates professional UX work from just decorating screens, and it runs through every remaining lesson.

UX is not a nice-to-have polish; it is a business driver, which is why companies pay well for it. The connection is direct: the experience determines whether people can and will use a product, which drives the numbers a business cares about.

Concretely, good UX pays off through:

• Conversion and revenue. If users cannot figure out how to sign up or check out, they leave, and the sale is lost. Smoothing those flows directly lifts conversion.
• Retention. A frustrating product gets abandoned; a pleasant, effortless one keeps people coming back. Experience is a major driver of whether users stay.
• Reduced support costs. A confusing product generates support tickets and complaints. An intuitive one reduces them, people do not need help to do obvious things.
• Trust and reputation. A polished, coherent experience signals credibility; a clumsy one makes users doubt the whole product.
• Cheaper development. Getting the design right through research and testing before building avoids the expensive rework of building the wrong thing, echoing the same logic that drives product discovery and project planning.

Don Norman's field has a long-standing observation that fixing a usability problem after launch costs far more than catching it in design, which is why testing early is an investment, not a delay.

For a career switcher, this framing matters twice: it explains why the role is valued and paid well, and it tells you how to talk about your work, in terms of user and business outcomes (conversion, retention, satisfaction), which is exactly what employers want to hear.

UX work follows a process, and the most well-known model is the double diamond, from the British Design Council. It captures a rhythm of diverging (exploring broadly) and converging (narrowing to a decision), done twice, once to find the right problem, once to find the right solution.

The four phases:

• Discover (diverge): explore widely to understand users and the problem space, research, observe, gather insight without jumping to solutions.
• Define (converge): synthesize what you learned into a clear, specific problem statement, the right problem to solve.
• Develop (diverge): explore many possible solutions to that problem, sketch, ideate, prototype broadly.
• Deliver (converge): narrow to the best solution, refine it, test it, and ship it.

The two diamonds embody the central UX discipline: first solve the right problem, then solve the problem right. The first diamond (discover, define) is problem-finding; the second (develop, deliver) is solution-building. Beginners rush to the second, jumping to designing screens, before doing the first, which is how you end up beautifully solving the wrong problem.

This maps neatly onto the cursus: Lesson 2 is the first diamond (research and defining the problem), Lesson 3 is developing solutions (structure, wireframes, prototypes), and Lesson 4 is delivering and validating (testing, refining, accessibility). Real work is not perfectly linear, you loop back as you learn, but the double diamond gives you the mental structure of how UX designers actually move from a fuzzy problem to a validated product.

Pull it together into a working picture of UX and the path in.

UX design is the practice of making products useful, usable, and satisfying by understanding real users and designing for them, with UI as the visual layer that expresses it. It is grounded in user-centered design (you are not your user), justified by business value (conversion, retention, trust), and structured by a process like the double diamond (find the right problem, then build the right solution).

What makes someone good at it:

• Empathy and curiosity about people, the core raw material.
• Structured problem-solving, moving from fuzzy problem to clear solution.
• Evidence over ego, letting real users judge the work.
• Communication, explaining and justifying design decisions.
• Craft, in the tools and visual fundamentals (Lesson 3).

For a career switcher, the encouraging summary: UX is a learnable discipline built substantially on understanding people, so backgrounds in psychology, research, writing, teaching, support, or any people-centered field transfer strongly. The visual-tool skills are learnable; the user-centered mindset is the heart, and you can start building it now.

The standard way to break in, developed across the cursus, is to learn the process, practice it on a real project, and assemble a portfolio that shows your thinking, not just pretty screens but the problem, your research, your decisions, and the outcome. The rest of the cursus builds exactly that capability, starting with the foundation of it all: understanding users through research.

UX work moves through two diamonds: discover and define to find the right problem, then develop and deliver to build the right solution, diverging to explore and converging to decide in each, all grounded in real users.