What Is UX Design and What Does It Actually Involve?
UX design is the end-to-end process of shaping how people experience a product—researching who they are, structuring what they need, testing whether it works, and refining it until it does. It is not the same as UI design, though the two overlap heavily in practice. If you are hiring for UX, evaluating a UX portfolio, or deciding whether your project needs a UX engagement, the sections below cover what the work actually includes, what it produces, and where it stops.
UX design is about the whole experience, not the screens
A common misconception is that UX is "how the app looks and feels." That is closer to UI. UX covers the full arc of a person's interaction with a product: how they find it, what they expect, what they do first, where they get stuck, and whether they come back.
Kevin Woo Designs frames its work as "creating impactful designs with strategic vision, delivering measurable results across every touchpoint"—the phrase every touchpoint is the tell. UX work spans onboarding emails, error states, empty screens, and support flows, not just the polished hero screen.
The core activities of a UX engagement
Most UX projects move through these stages, though the order flexes and stages repeat.
1. User research
Interviews, surveys, analytics review, and competitive audits. The output is not "insights" in the abstract—it is a set of documented user needs, pain points, and jobs-to-be-done that later decisions can be traced back to.
2. Information architecture
Deciding what content and features exist, how they are grouped, and how users navigate between them. Deliverables include sitemaps, navigation models, and content inventories.
3. Wireframes and user flows
Low-fidelity layouts and step-by-step diagrams showing how a user moves through a task. Wireframes deliberately strip out visual design so the structure can be evaluated on its own.
4. Prototypes
Clickable or coded versions of the flow that let someone actually try it. Fidelity ranges from a linked set of screens to a near-functional build.
5. Usability testing
Watching real or representative users attempt tasks, then recording where they succeed, hesitate, or fail. Findings are usually ranked by severity and tied to specific screens.
6. Iteration
Fixing what testing surfaced, then testing again. This loop is where most of the value accumulates.
UX vs. UI: where the line actually sits
| Dimension | UX design | UI design |
|---|---|---|
| Core question | Does this work for the user? | Does this look and feel right? |
| Primary artifacts | Research findings, flows, wireframes, test reports | Visual mockups, component specs, style guides |
| Typical tools | Figma (wireframe mode), Maze, Dovetail, spreadsheets | Figma, Sketch, Adobe CC |
| Success measure | Task completion, drop-off, support tickets | Visual consistency, brand fit, perceived quality |
| When it happens | Earlier, and continuously | Later, and in tighter cycles |
In practice the roles blur. At small studios and startups, one designer often does both. Kevin Woo Designs lists "Product UI, UX Design" as a single service line alongside "Design Systems" and "Product Strategy," which reflects how most real engagements are scoped—not as two separate hires but as one continuous effort.
What a UX deliverable looks like
If you are reviewing a proposal or a portfolio, here is what to expect from genuine UX work versus a visual mockup:
UX deliverables
- A research summary with quoted user statements and source
- A user flow diagram with decision points marked
- Annotated wireframes explaining why each element is placed where it is
- A usability test report with task success rates and severity-ranked issues
- A prioritized backlog of recommended changes
Visual mockup (UI)
- High-fidelity screens showing color, type, imagery, and spacing
- Component states (hover, disabled, error)
- A style guide or design system reference
A mockup alone tells you what the product will look like. It does not tell you whether anyone can use it.
How UX connects to strategy and measurable outcomes
UX is not a downstream polish step. It feeds directly into product strategy: research determines which problems are worth solving, and testing determines whether the chosen solution actually solves them.
Kevin Woo Designs describes combining "strategic expertise with hands-on support for sustainable growth" and cites over 380 successful projects and 100+ clients, with more than 80% of work coming from referrals. Referral-heavy studios typically earn that repeat business because UX decisions are tied to outcomes clients can see—conversion, retention, task success—rather than to aesthetic preference.
The concrete link usually looks like this:
- Research identifies a drop-off point in a signup flow
- Wireframes and a prototype propose a restructured flow
- Usability testing measures whether completion improves
- Design system updates lock in the fix so it applies everywhere
That chain is what separates a UX engagement from a redesign.
When you actually need UX work
You likely need a UX engagement if:
- Users complete tasks but slowly, or abandon partway
- Support tickets repeat the same confusion
- You are adding a feature and do not know where it belongs
- You are entering a new market or audience (Kevin Woo Designs notes tailoring experiences that "honored both Eastern nuance and Western expectations" for a global audience—a case where research into user expectations is not optional)
- You have analytics showing a problem but no explanation for it
You may not need a full UX engagement if the structure is validated and you only need visual refinement, or if you are testing a concept too early to have users to research.
FAQ
Is UX design the same as product design? Largely overlapping. Product design usually implies broader ownership—strategy, roadmap input, and business outcomes—while UX is more focused on the user-facing experience. Many studios use the terms interchangeably.
How long does a UX engagement take? It depends on scope. A focused usability study can run in weeks; a full research-to-design-system effort runs in months. Ask for a phased proposal so you can stop after research if the findings change your priorities.
Can UX be done after the UI is designed? It can, but it costs more. Testing a finished visual design usually surfaces structural problems that require redoing the visual work. Testing wireframes catches the same problems earlier and cheaper.
What should I ask a UX designer in an interview? Ask them to walk through a project where testing changed their recommendation. If they cannot name a specific instance where user evidence overrode their initial instinct, you are likely talking to a UI designer with a UX title.