User Experience (UX) Design

What is UX design?

UX design is the discipline of shaping how people experience a digital product across every interaction: how they find it, how they learn to use it, how they accomplish their goals with it, how they feel while doing so, and whether they come back. It goes beyond the visual appearance of an interface and addresses the logic, flow, structure, and communication of an entire product experience.

The "user experience" in UX design refers to everything a person encounters when they use a product. The onboarding flow that introduces them to the product. The navigation structure that helps them find what they need. The error messages that tell them what went wrong. The search results that help or fail them. The checkout flow that makes a purchase feel straightforward or laborious. All of these are UX concerns, and UX design is the practice of making deliberate, research-grounded decisions about each of them.

UX design as a distinct practice emerged primarily from human-computer interaction research and grew significantly through the 1990s and 2000s as digital products became widespread. Don Norman popularized the term "user experience" while at Apple in the early 1990s to describe an approach to product design that centered on the quality of the human experience rather than on technology or features.

How does UX design differ from UI design?

The confusion between UX and UI is one of the most common misconceptions in product teams, and the distinction matters for understanding what work each discipline involves.

UI design (user interface design) is concerned with the visual and interactive layer of a product: the screens, components, typography, color, and layout that users see and interact with directly. A button's color, size, and label are UI concerns. Whether that button appears at the right moment in the user's task flow, is labeled in a way that matches the user's mental model, and produces the right outcome is a UX concern.

UX design encompasses the entire experience, of which the UI is one part. A product can have a visually polished UI and still deliver poor UX if the navigation structure doesn't match how users think, if the product doesn't solve the right problem, or if the flow to accomplish a key task requires too many steps.

The distinction isn't about hierarchy: neither discipline is more important than the other. They address different questions. UX asks whether the product does the right things in ways that serve the user. UI asks whether those things are presented clearly and attractively. Both are required for a successful product.

What does the UX design process involve?

UX design isn't a single activity; it's a process that spans the full lifecycle of product development.

• Research is the foundation. UX research methods include user interviews, contextual inquiry, surveys, usability testing, analytics analysis, and competitive analysis. Research establishes who the users are, what they're trying to accomplish, where they encounter problems, and what context they're working in. Without research, UX decisions are based on assumptions that may not hold.
• Information architecture is the organization and labeling of content and navigation. It determines how information is grouped, how navigation is structured, and what terminology is used to describe different parts of the product. IA decisions affect how easily users can find what they need and whether their mental models match the product's structure.
• Interaction design addresses how users navigate and manipulate the product: the flows, transitions, feedback mechanisms, and system states that define behavior. It asks how users move through the product, what the product communicates at each step, and how errors are handled and recovered from.
• Prototyping creates testable representations of design decisions at various levels of fidelity, from rough wireframes to interactive mockups. Prototypes allow the team to evaluate and test ideas before committing to full implementation.
• Testing, particularly usability testing, evaluates whether the design actually works for real users attempting real tasks. It generates evidence about what's working and what isn't, which drives iteration.

How does UX design contribute to business outcomes?

UX design's business impact is direct and measurable, even when design teams don't always measure it explicitly.

• Conversion is one of the most straightforward connections. A product with a clear, well-designed checkout flow converts a higher percentage of visitors into customers than one with a confusing or friction-laden process. A well-designed trial or freemium experience activates users into paying customers more reliably than one that leaves users confused about the product's value. These conversion differences translate directly to revenue.
• Retention is where UX design's long-term impact is most significant. Users who find a product easy to use and who regularly accomplish their goals with it are less likely to churn. Users who are frequently confused, encounter errors, or can't find features they need eventually stop using the product. Since customer lifetime value depends on retention, UX quality is a direct input to unit economics.
• Support cost reduction is a less visible but measurable impact. Products that communicate clearly, handle errors gracefully, and help users recover from mistakes generate fewer support tickets. Every support interaction that a better-designed product eliminates represents real cost savings.
• Brand perception is shaped significantly by product experience. A product that feels polished, thoughtful, and responsive to user needs creates brand associations that marketing can't fully produce or repair independently of the actual experience.

How is UX design practiced in Agile product teams?

UX design in modern agile teams differs from the traditional model where design was a distinct phase preceding development.

In integrated Agile teams, designers work alongside product managers and engineers throughout the product development cycle. Discovery and design work typically runs one to two sprints ahead of development, ensuring the team has a validated direction before committing engineering time to building. This is sometimes called dual-track agile or continuous discovery.

Rapid iteration is the norm rather than the exception. Designs are tested at lower fidelity earlier, feedback is incorporated faster, and decisions that would once require extended analysis are made with lighter research and validated empirically through A/B testing or short usability sessions.

The shift from waterfall to agile has generally been positive for UX practice because it creates more opportunities for user feedback throughout development rather than concentrating it at a final QA stage. The challenge is ensuring that velocity pressure doesn't eliminate the discovery work that gives design direction.

How is AI changing UX design?

AI has entered UX design practice at multiple levels, changing both the tools designers use and the types of products they design for.

On the tools side, AI is compressing several stages of the design process. Research synthesis tools like Dovetail use AI to cluster themes across interview transcripts and surface patterns across large qualitative datasets, reducing analysis time from days to hours. Design generation tools like Figma Make can produce interface layouts from text prompts, giving designers a starting point to critique and refine rather than a blank canvas to fill. Automated accessibility checkers flag contrast and labeling issues as designs are built rather than at a late-stage audit. Figma's 2025 AI report found that 78% of designers and developers believe AI boosts their efficiency, though fewer than half felt it makes them better at their jobs, pointing to the distinction between faster execution and better judgment.

On the product side, AI-powered features have created new UX design problems that the field is actively working through. When a product recommends, generates, or decides rather than simply responding to explicit user commands, the UX design must communicate what the system is doing, how confident it is, how users can verify its outputs, and how they can intervene when it's wrong. This area, sometimes called AI UX or explainable AI design, requires thinking through trust, transparency, and control in ways that traditional interface design didn't need to address. Users who've had bad experiences with AI features become less willing to try new ones, which makes getting the trust signals right from the first interaction consequential.

The net effect is that AI is handling more of the execution work in UX practice, which raises the value of the judgment that AI can't replicate: understanding what users actually need, knowing when a generated output is wrong for the context, and making the strategic decisions about what a product should and shouldn't do.