What Does a UX Designer Actually Do? A Realistic Day-to-Day Guide

If you are thinking about switching into UX design, you have probably asked yourself: what do these people actually do all day? The job title sounds broad. The LinkedIn posts make it look like endless sticky notes and Figma files. The truth is more interesting - and more varied - than either of those images suggests.

This post gives you a concrete, honest picture of the day-to-day work: the activities that fill a UX designer's week, the tools involved, how the role shifts depending on where you work, and what you will probably not be doing (despite what some job ads imply).

If you are earlier in your research and still working out what UX design even is, start here before reading on.

The core job, in plain English

A UX designer's job is to make sure a product - an app, a website, a piece of software - works well for the people who use it. Not just technically works, but feels intuitive, achieves what users are trying to do, and does not cause unnecessary frustration along the way.

To do that, you need to understand users, translate that understanding into design decisions, and then communicate those decisions to the engineers and product managers who build the thing. That loop - research, design, test, refine - is the engine of the role.

What fills a UX designer's week

User research

This is where good design starts. Before you draw a single screen, you need to understand who you are designing for and what problems they are actually facing.

In practice, that means:

Running user interviews - one-to-one conversations where you ask people about their goals, habits, and frustrations
Sending out surveys to gather broader patterns across a larger group
Conducting contextual enquiry - watching people use a product in their natural environment, not in a lab
Reviewing existing data: analytics, support tickets, customer feedback, session recordings

Research is not always a big formal project. At many companies, it happens in smaller bursts throughout the design process. You might spend a morning doing three short interviews to pressure-test an assumption before you commit to a design direction.

Synthesis and sense-making

Raw research data does not give you answers. It gives you material to work with.

After research, UX designers spend time organising what they found - grouping observations, identifying patterns, and pulling out the insights that actually matter. Common methods include affinity mapping (clustering related notes together), creating user personas, and writing up "how might we" questions that frame the design problem clearly.

This phase is often less visible than the design work, but it is where a lot of the thinking happens. Getting it wrong here means solving the wrong problem - which is expensive to fix later.

Workshops and collaboration

UX designers regularly run workshops with colleagues: product managers, engineers, marketers, customer service teams. The goal is usually to align on a problem, generate ideas together, or get buy-in on a direction.

You do not need a background in facilitation, but you do need to get comfortable running a room. Workshops range from short ideation sessions ("let's all sketch solutions for 20 minutes") to longer design sprints that compress weeks of work into a few days.

User flows and information architecture

Before you start designing individual screens, you need to map out the overall structure of the experience. This means:

User flows: step-by-step diagrams showing how a user moves through a product to complete a task
Information architecture: how content and features are organised and labelled, so users can find what they need

These are often created in tools like Figma or Miro, and they look deceptively simple. Getting them right requires holding a lot of complexity in your head: what the user knows at each step, what they are trying to do, and where things could go wrong.

Wireframing

Wireframes are low-fidelity sketches of screens - no colour, no final copy, no polished visuals. They show layout, structure, and basic content hierarchy, without the distractions of a finished design.

Good wireframing is fast and disposable. The point is to explore options quickly and get feedback before you invest time in a high-fidelity design. You might go through five or six versions of a layout before one feels right.

Prototyping

A prototype is a clickable, interactive version of your design that simulates how the final product will work. It does not need to be built in code - Figma prototypes are the industry standard, and they let you connect screens together, add transitions, and create a realistic user experience without involving engineers.

Prototypes range from very rough (a few screens linked together to test a single flow) to near-production quality (a fully interactive mock-up that looks finished). The level of fidelity depends on what you are trying to learn.

Usability testing

Once you have a prototype, you test it with real users. Usability testing is not about asking "do you like it?" - it is about watching people try to complete tasks and seeing where they get stuck, confused, or frustrated.

A typical session lasts 30-60 minutes. You observe, take notes, and resist the urge to help when a participant struggles (that struggle is the data). Afterwards, you synthesise the findings and use them to improve the design.

This cycle - design, test, learn, revise - can repeat many times before a feature ships.

Design reviews and handoff

When a design is ready to move forward, it goes through review. That might mean a critique with other designers, a sign-off conversation with your product manager, or a presentation to senior stakeholders.

After sign-off, you work with engineers to hand over the design. In Figma, that means annotating your designs with specifications: spacing, typography, interaction states, edge cases. Good handoff documentation saves a lot of back-and-forth during development.

Meetings and collaboration (the unglamorous part)

UX designers sit at the intersection of product, engineering, and business. That means a fair number of meetings: sprint planning, roadmap reviews, stakeholder check-ins, cross-functional syncs.

Some of this is genuinely useful. Some of it is overhead. The ratio depends heavily on the company culture. Either way, it is part of the job - the ability to communicate your thinking clearly to non-designers is as important as the design work itself.

How the role varies by company size

One of the most misunderstood things about UX design is how different it looks depending on where you work.

At a startup, you will probably be a generalist. Research, wireframing, prototyping, usability testing, visual polish - it all lands on you. You might also be doing some UI design, writing UX copy, and feeding into product strategy. The scope is wide, the resources are limited, and you will learn quickly.

At a mid-size company, there is usually more structure. You will have a team, possibly a design system, and clearer processes. There is more room to go deep on individual projects.

At a large tech company, UX roles often specialise. You might be a UX researcher who does not design screens at all. Or a product designer focused narrowly on a single part of a complex product. Collaboration with engineers and product managers is more formal, and the pace of change is slower.

Neither is better. They suit different working styles. If you like variety and autonomy, a startup or agency might appeal. If you prefer depth, clear process, and a strong design team to learn from, a larger company may be a better fit.

For more on how UX and UI responsibilities split across these contexts, this post on UX vs UI design covers the distinction in detail.

How seniority changes the work

Junior designers tend to focus on execution - taking a problem that has been framed for them and producing good design work. The expectation is strong craft skills and a willingness to take direction and iterate.

Mid-level designers are expected to own problems end to end: frame the problem through research, design the solution, test it, and ship it with limited supervision.

Senior designers spend more time in ambiguity - they help define what the right problems are, influence product strategy, mentor others, and make the case for design investment at a leadership level. The work shifts from "producing designs" to "shaping how the team thinks about design."

What UX designers typically do NOT do

A few things that often come up in job ads, but are not always part of the UX role:

Graphic design or brand work. UX design is about how things work. Visual design - brand identity, illustration, marketing materials - is a different discipline, though the skills can overlap.
Front-end development. Most UX designers do not write production code. A basic understanding of HTML and CSS is useful context, but it is not a requirement.
Writing all the product copy. UX designers often write placeholder copy and may have input on tone, but dedicated content designers or copywriters usually own the final words.
Running the business. You are not responsible for deciding what to build - that sits with product managers. You are responsible for designing it well, advocating for users, and flagging when a proposed direction has problems.

The tools of the trade

Figma is the industry standard for wireframing, prototyping, and design handoff - almost every UX team uses it. Beyond that:

Miro or FigJam for workshops, affinity mapping, and journey mapping
Maze, Maze, or UsabilityHub for remote usability testing
Notion or Confluence for documentation
Slack and Jira for communication and project tracking

Tools change. The underlying skills - research, problem-framing, clear communication, design judgment - do not. If you are learning UX today, focus on those, not on becoming a Figma power user from day one.

Is this the right career for you?

UX design suits people who are curious about how other people think, comfortable sitting with ambiguity, and good at explaining their reasoning. You do not need a design degree or a technical background - many of the best UX designers came from psychology, teaching, customer service, marketing, or other fields entirely.

If you are wondering whether it is a good career move financially and professionally, this post on whether UX design is a good career covers demand, salaries, and realistic timelines.

Ready to go deeper?

If this picture of the day-to-day resonates, the next step is seeing it in practice. Our free UX/UI masterclass walks you through a live design challenge so you can experience the process - not just read about it.

Join the free masterclass and see what the work actually feels like.

Or if you are ready to explore the full programme, take a look at our courses - including the Beginner UX Design course, which is built for people making exactly this kind of career change.