The human reality · work changes by team
What does a UX designer
actually do?
UX work can include understanding needs, mapping a journey, sketching or prototyping, testing assumptions and working through constraints with a team. The job title alone does not tell you how much research, UI craft or delivery work a role contains.
The screen is only part of the work
Find the snag.
Then work with the people around it.
O*NET describes collaboration and work-context characteristics for a broader web and digital-interface occupation. UX teams may include product managers, researchers, writers, engineers, data specialists, accessibility partners and customer-facing staff; smaller organizations combine several responsibilities in one role.
Constraints are part of the design: an existing system, a deadline, legal or privacy requirements, development effort and evidence that is incomplete. A practitioner has to make those limits visible instead of presenting a prototype as if it had already solved them.
A project rhythm, not a timecard
Four recurring moves.
Often revisited.
This editorial sequence synthesizes broad task descriptions; it is not a claim that every designer or project follows four neat stages.
- Understand
Find the user’s task
Gather context, review existing evidence and identify the question the team has not answered yet.
Possible output
A problem statement with knowns, assumptions and open questions. - Explore
Make the flow visible
Map steps and alternatives; sketch interactions before investing in detailed screens.
Possible output
A journey, flow or prototype the team can discuss. - Check
Look for friction
Review edge cases and, where appropriate, ask people to try a prototype without leading them.
Possible output
Observed issues, feedback and what the test cannot establish. - Deliver
Resolve the details
Discuss feasibility with engineers, document behavior and support quality checks after implementation.
Possible output
A clear handoff and a list of questions to monitor after release.
A little occupational context—with boundaries
Digital work is collaborative.
But these figures are not UX-only.
O*NET survey answers describe respondents in the wider Web and Digital Interface Designers occupation. They can help frame questions about collaboration; they do not show how every UX team works.
How important is contributing to a team?
Share of respondents selecting each answer in O*NET Work Context.
How to use it: prepare to communicate and make decisions with others, but ask the employer how research, product, design and engineering responsibilities are actually shared.
O*NET OnLine · Work Context · Web and Digital Interface Designers (15-1255.00). Percentages are response shares for one question—not percentages of time or proof of a specific UX team's practices.
One title, different centers of gravity
Read the verbs
in the job description.
The mix below is an editorial lens for comparing postings, not official job categories. One role may sit between several columns.
| If the posting emphasizes… | You may spend more time on… | Ask the team… |
|---|---|---|
| Research and discovery | Interview planning, synthesis, journey maps, evidence and opportunity framing. | Who recruits participants? How are research findings used in product decisions? |
| Interaction and service flows | Information architecture, task flows, states, prototypes and cross-channel journeys. | What happens when the normal path fails or the service is unavailable? |
| UI and design systems | Visual interface details, component libraries, responsive behavior and handoff. | How much of the role is interface craft versus discovery? Who maintains the system? |
| Product strategy | Prioritization, opportunity framing, metrics and trade-offs with product partners. | Which decisions can the designer influence, and what evidence supports them? |
Follow the question
that matters to you.
What UX designers earn
U.S. wage data for the broader digital-interface occupation, with its limits made explicit.
Read this guide Explore this questionIs UX design growing?
See the national projection and annual openings without mistaking either for local vacancies.
Read this guide Explore this questionHow to enter UX design
Compare degrees, projects and portfolio evidence against the roles you actually want.
Read this guide Explore this questionWhat AI may change
A task-level reading of official evidence—not an individual replacement score.
Read this guide Try the workMake a booking flow clearer
Respond to one visitor question, revise the information order and handle a full session in an original fictional UX exercise.
Open the work sampleSources and scope
O*NET work-context survey results represent respondents selecting a stated answer, not time spent or a universal UX workday. Role settings and responsibilities differ.
- U.S. Bureau of Labor Statistics · Web Developers and Digital Designers ↗
- O*NET OnLine · Web and Digital Interface Designers (15-1255.00) ↗
Occupational information on this page is adapted from O*NET OnLine, sponsored by the U.S. Department of Labor, Employment and Training Administration (USDOL/ETA), under the CC BY 4.0 license. Ikigain has adapted and interpreted the information; USDOL/ETA has not approved, endorsed or tested these modifications. O*NET® is a trademark of USDOL/ETA.
Sources checked 28 September 2026. Where official sources use the broader Web and Digital Interface Designers occupation, they do not isolate UX designers. U.S. figures are not a local-market or other-country estimate.
Saved paths and work-sample notes stay in this browser. Fictional exercises are for exploration, not professional assessment.