What Is UX Design? A No-Jargon Guide for Founders

UX design is one of the most jargon-heavy disciplines in the tech industry, which is ironic given that clarity is supposed to be one of its core values. The term gets used to mean everything from user research to visual design to content strategy — which makes it nearly impossible to have a productive conversation about what you actually need.

This is a jargon-free explanation of what UX design means for software products.

The Clean Definition

UX design (user experience design) is the practice of designing how users interact with and move through a software product.

It answers: what can users do in this product, how do they do it, and what happens at each step?

UX design is concerned with the functional layer of a product — the flows, the navigation, the task completion paths, the error handling, the states. It determines:

• Whether users can find what they need without getting lost
• Whether the path from intent to completion is as short as possible
• Whether errors are clear and recoverable
• Whether new users can figure out the product without training or support

UX design doesn't determine what the product looks like — that's UI design's job. But it determines the underlying structure that UI design makes visible.

Why UX Is More Than Just "Usability"

"Usability" is a necessary but insufficient description of UX design. Usability means users can complete tasks. UX design is concerned with the full arc of the experience — from the moment users arrive at the product, through their first use, through becoming proficient users, and including how they interact with the product in edge cases (errors, empty states, loading states, unexpected conditions).

For B2B software, this arc looks like:

1. First impression — does the product clearly communicate what it does and what to do first?
2. Onboarding — can a new user get to their first "value moment" without help from the support team?
3. Task completion — can users complete their primary tasks consistently, without getting stuck or making errors?
4. Error recovery — when something goes wrong, do users understand what happened and what to do next?
5. Feature discovery — do users find and use more of the product's features over time, or stay in a small subset?
6. Proficiency growth — does the interface support both new and experienced users, or optimise for one at the expense of the other?

UX design is the discipline that addresses all six. Skipping any of them produces a product that fails at that stage for a specific segment of users.

The Information Architecture Layer

The most impactful layer of UX design for B2B software is information architecture — how the product's features are organised and what's accessible from where.

Information architecture determines:

• What's in the primary navigation
• What's nested under each navigation item
• What appears on the main dashboard vs. what's in a secondary view
• What settings are global vs. contextual

The most common B2B SaaS information architecture failure: organising features by the internal system (the way the backend is structured) rather than by the user's mental model (the way users think about their tasks).

A user who wants to "see my recent activity" doesn't know whether to look in "Feed", "Log", "History", or "Activity" — four labels that might mean the same thing to the product team but mean different things to a new user. The UX designer's job is to choose the organisation that matches how users think about their work, test that assumption with real users, and iterate.

Interaction Design: The Detail Layer

Interaction design is the UX sublayer that determines exactly what happens at each step of a flow:

• What does clicking a button do?
• How does a form validate — inline as the user types, or on submission?
• What happens if two users try to edit the same record simultaneously?
• How does a file upload communicate progress?
• What does the product do while a slow API call is processing?

These decisions are invisible when done correctly. They're extremely visible when done incorrectly — a form that only validates on submission and loses the user's input on error is a UX failure that causes real frustration and support tickets.

The interaction design decisions that matter most in B2B software are often the edge cases: what happens in error conditions, what happens in slow network conditions, what happens when data is missing or ambiguous, what happens when a user tries to take an action they don't have permission for.

UX and the Cost of Churn

The business case for UX investment is most directly measured in churn. Users who can't complete their primary tasks either stop using the product or use it minimally — which prevents the expansion and renewal that drive SaaS ARR.

The Forrester data point is specific: 70% of SaaS user churn is attributable to poor usability. This is not users who complained about bad UX — it's users who simply stopped showing up, without any clear attribution signal in your analytics. Churn attributed to "lack of engagement" or "product didn't fit our needs" is often a UX failure in disguise: the product had the features the user needed, but the UX made those features hard enough to use that the user gave up.

The ROI of fixing UX problems is therefore measured in reduction of silent churn — users who would have churned without attribution who instead find the product useful enough to continue.

The Difference Between UX and UI — In Practice

The distinction is clearest in examples:

UX problem: The user can't find the "Team Members" settings because they're nested three levels deep under "Account > Workspace > Manage Users" instead of being accessible directly from the main navigation.

UI problem: The "Team Members" settings page looks like it was designed in 2019 — different typography from the rest of the product, a layout that uses full-width tables instead of the card-based layout everywhere else.

Both are real problems. The UX problem causes users to not find a feature they need. The UI problem causes users to perceive the feature as low-quality. Fixing the UX problem (moving the menu item to a more obvious location) requires no visual design changes. Fixing the UI problem (updating the visual treatment) requires no structural changes.

In practice, the same designer often handles both — but the problems are diagnosed and solved differently.

What Good UX Looks Like for B2B SaaS

The markers of good UX in a B2B software product:

1. New users reach their first value moment without support — the onboarding flow gets them to the first meaningful action within the first session
2. Primary tasks have obvious paths — users don't need to explore to find common actions
3. The navigation matches users' mental models — features are where users expect to find them
4. Empty states are informative, not blank — when there's no data, the product explains why and what to do about it
5. Errors are specific and actionable — "Email address already in use. Sign in or use a different email." not "Something went wrong."
6. The product gets faster to use over time — keyboard shortcuts, default selections, and progressive disclosure support experienced users without confusing new ones

---

If you're seeing high churn, low activation, or users stuck on specific steps in your product, those are UX signals worth diagnosing before they compound. Book a free 30-minute design review and we'll look at your product specifically.

Frequently Asked Questions

Related reading: What Is UI Design? · What Is Product Design? · How Product Design Affects SaaS Conversion Rates