The popular image of a UX designer's workday involves headphones, Figma on a large monitor, and an unbroken stream of creative work punctuated by the occasional design critique. The reality is more fragmented, more interpersonal, and considerably more varied than that image suggests. Depending on your seniority, your employer type, and the current phase of whatever product you are working on, a single week might include user research sessions, a sprint planning meeting, a stakeholder presentation to the VP of Product, two rounds of design critique, detailed component specification work in Figma, and an afternoon spent synthesising interview data in a research repository.
UX design is fundamentally a collaborative discipline. Designers do not create products alone -- they translate user needs and business goals into design solutions that engineering teams build, that product managers prioritise, that data teams measure, and that stakeholders sponsor. The work of maintaining those relationships and keeping design decisions visible and well-reasoned is a substantial part of every designer's week, and it increases as seniority grows.
This article maps what UX designers actually do across a typical week: the activities, the meetings, the tools, and the cognitive work. It distinguishes how a junior designer's day differs from a senior one, and how the in-house product company experience differs from agency and freelance arrangements.
"Design is 10% creating things and 90% communicating why. The first time I understood that was when my beautifully crafted prototype got cut in sprint planning because I had not explained the user problem to the engineers convincingly enough." -- Anonymous senior product designer, NN/g UX Podcast Episode 189 (2023)
Key Definitions
Design Sprint: A time-boxed product development framework, typically five days, in which a team defines a problem, generates solutions, prototypes, and validates with users. Popularised by Google Ventures and the book 'Sprint' by Jake Knapp.
Design Review: A structured critique session in which a designer presents work-in-progress to peers, product managers, or engineering partners for feedback. Reviews are most valuable when the work is still malleable.
Stakeholder Presentation: A meeting in which design decisions are presented to business decision-makers who control resources and priorities. Requires different communication skills than peer critique.
Research Repository: A centralised database of user research findings -- interview transcripts, usability test recordings, survey data -- that enables teams to build on previous learning rather than repeat it.
Handoff: The process of delivering design specifications to engineering for implementation. In modern workflows, this happens via Figma's dev mode, which generates code annotations and measurements automatically from design files.
How a UX Designer's Time Is Actually Allocated
Research from the NN/g 2024 UX Careers Survey finds that designers spend roughly:
| Activity | Junior Designer | Senior Designer |
|---|---|---|
| Creating/iterating design artefacts | 45-55% | 25-35% |
| Meetings and collaboration | 20-25% | 30-40% |
| Research activities | 10-15% | 20-25% |
| Documentation and communication | 5-10% | 10-15% |
| Professional development and mentoring | 5-10% | 5-10% |
These percentages shift significantly by seniority. Junior designers spend more time in Figma; senior and principal designers spend more time in meetings, on communication, and on the upstream problem-framing work that determines what gets designed before any design work begins.
Monday: Research and Discovery
A typical Monday morning for a UX designer working on a SaaS product begins with a brief team standup -- five to fifteen minutes in which each person states what they are working on and whether anything is blocked. After standup, a designer midway through a discovery phase might spend the morning reviewing interview recordings from the previous week.
UX research synthesis is rarely glamorous: it involves reading transcripts, tagging recurring themes, building affinity maps in FigJam or Miro, and writing up a concise findings document that other stakeholders can actually read. This synthesis work is where the quality of research lives -- raw interview data is not useful until it is organised into patterns.
A junior designer at this stage is executing a methodology that someone else scoped. A senior designer has written the research plan, recruited the participants, and is now synthesising independently with a view to presenting recommendations to the broader product team.
The afternoon might include a one-on-one with the product manager to align on what the research findings mean for the upcoming sprint, and preparation time for a design review scheduled for Tuesday.
Tuesday: Design Critique and Iteration
Design critiques are among the most valuable and most poorly run meetings in product organisations. Done well, a design critique exposes assumptions, catches usability problems before they become engineering costs, and creates shared ownership of design decisions. Done poorly, they become either rubber-stamp sessions or unstructured preference discussions.
A senior designer presenting at a critique will typically: set context by restating the user problem and constraints, present the design in stages from high-level to detail, explicitly call out decisions they are uncertain about and where they want feedback, and end by summarising what changes they plan to make based on what they heard.
A junior designer often presents too much in too little time, skips the problem framing, and responds to critique defensively rather than curiously. This is normal -- it takes two to three years of regular critique participation to become comfortable and skilled at both giving and receiving design feedback.
After a critique, the rest of Tuesday is likely spent iterating: updating wireframes in Figma based on feedback, exploring alternative solutions to specific problems the critique surfaced, and documenting the rationale for decisions made.
Wednesday: Stakeholder Meetings and Political Work
Wednesday in many product organisations means cross-functional syncs. A designer working on a key product initiative might attend: a product trio meeting with their PM and engineering lead; a design team meeting to share work across different product areas; and a stakeholder update -- a presentation to a director or VP on the design direction.
Stakeholder meetings are where political skill becomes visible. A designer who can explain the 'why' behind design decisions in business language -- connecting UX choices to conversion rates, support ticket reduction, customer retention, or net promoter score -- is dramatically more effective at securing the space and resources for good design than one who speaks only in the language of user empathy.
This is the dimension of UX design that most bootcamp curricula under-prepare students for. The mechanics of Figma and the methods of research are teachable. The ability to navigate organisational dynamics, maintain relationships with sceptical stakeholders, and make the case for design investment requires years of real practice.
Thursday: Deep Work and Prototyping
Experienced designers know that Thursday and Friday afternoons are often the most productive time for deep, focused design work -- the early part of the week is front-loaded with meetings, and the later part of the week is when calendar pressure eases enough for sustained creative thinking.
Deep work for a UX designer in execution mode means building interactive prototypes in Figma: designing the complete user flow for a feature end to end, specifying states (empty, loading, error, success), annotating edge cases for engineering, and preparing the design for handoff.
A junior designer's Thursday might be spent almost entirely in Figma -- executing a defined brief, building out screens to a specification established by a senior designer, and learning the mechanics of the tool and the design system. A senior designer's Thursday involves more judgement: deciding what is in scope and what is out, which edge cases need to be designed versus can be handled with engineering conventions, and what the right level of detail is for a handoff document.
Friday: Documentation, Learning, and Team Rituals
Most product companies end the week with some form of review meeting -- a sprint review, a demo, or a team retrospective. Designers typically present work completed during the sprint and participate in retrospectives where the team reflects on what went well and what to improve.
After any team rituals, Fridays are good days for documentation, professional reading, and portfolio maintenance. Experienced designers who maintain active Notion portfolios or personal design blogs find that writing about their work clarifies their thinking and generates career opportunities.
Junior vs Senior: The Key Differences
| Dimension | Junior Designer | Senior Designer |
|---|---|---|
| Primary focus | Execute defined briefs | Frame problems before design begins |
| Figma time | High | Moderate |
| Stakeholder communication | Limited | Central |
| Research ownership | Support role | Leads and owns |
| Design critique | Presents to peers | Critiques peers and mentors juniors |
| Ambiguity tolerance | Low | High |
| Pushback on briefs | Rarely | Expected |
The transition from mid-level to senior is less about gaining new technical skills and more about expanding the scope of problems you are willing to engage with and the confidence with which you navigate ambiguity.
Agency vs In-House vs Freelance
In-house product companies: Designers work on a single product over extended periods, developing deep knowledge of the user base, the codebase constraints, and the design system. The depth enables better design decisions over time. In-house roles are most common for designers who want meaningful impact on a specific product and a defined career path.
Design agencies: Agency designers work across multiple client projects. A single month might involve research for a healthcare client, a visual redesign for a retail brand, and a service design workshop for a government department. This breadth accelerates skill development but limits depth. Agency work requires strong project management and client communication skills.
Freelance: Freelance designers operate as independent consultants with full scheduling flexibility and significantly higher overhead -- business development, invoicing, client relationship management, and professional isolation are all real costs. Successful freelance UX designers typically specialise in a particular domain or type of work to justify higher rates.
Practical Takeaways
Before idealising a specific work environment, talk to designers currently working in it. The gap between how companies present their design culture in job descriptions and how it actually operates is substantial. Ask interviewers: "Can you walk me through a recent decision where design influenced a product change?" and "How do you handle situations where engineering says a design is not feasible?" The answers are revealing.
Protect your deep work time deliberately. The meeting culture at most product companies defaults to more meetings rather than fewer. Blocking two or three hours of focus time on the calendar -- consistently and visibly -- is a skill that experienced designers develop and junior designers often neglect until burnout forces the conversation.
References
- Nielsen Norman Group. (2024). UX Careers Report 2024. nngroup.com/reports
- Knapp, J., Zeratsky, J., & Kowitz, B. (2016). Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days. Simon & Schuster.
- Buley, L. (2013). The User Experience Team of One. Rosenfeld Media.
- Gothelf, J., & Seiden, J. (2021). Lean UX, Third Edition. O'Reilly Media.
- UXPA International. (2024). UX Practitioner Survey 2024. uxpa.org
- Figma. (2024). State of Design Tools 2024. figma.com/blog
- Dovetail. (2024). The State of User Research 2024. dovetail.com/ux-research
- Portigal, S. (2023). Interviewing Users: How to Uncover Compelling Insights, 2nd Edition. Rosenfeld Media.
- Larson, W. (2021). An Elegant Puzzle: Systems of Engineering Management. Stripe Press.
- NN/g UX Podcast. (2023). Episode 189: Designer Roles and Responsibilities. nngroup.com/podcast
- Interaction Design Foundation. (2024). UX Designer Job Description and Responsibilities. interaction-design.org
- Springboard. (2024). What Does a UX Designer Do All Day?. springboard.com/blog
Frequently Asked Questions
How much of a UX designer's day is spent designing visuals?
Less than most people expect. Junior designers spend 45-55% of their time in Figma. Senior designers spend only 25-35% on artefact creation -- the rest goes to research, stakeholder communication, and design critique.
Do UX designers have a lot of meetings?
Yes, especially at in-house product companies. Design reviews, sprint ceremonies, stakeholder syncs, and research sessions can consume 3-5 hours per day. Meeting load is one of the most commonly cited sources of designer dissatisfaction.
How does a junior UX designer's day differ from a senior one?
Junior designers spend more time executing defined briefs in Figma. Senior designers spend more time framing problems, running research, and influencing product strategy -- before any design work begins.
Is UX design better at agencies or in-house?
Agency work offers variety and faster early skill development. In-house roles offer deeper product ownership and more impact on a single product. Most designers develop a clear preference based on whether they prefer breadth or depth.
Do UX designers write code?
Most do not write production code. Designers work in Figma and hand off specifications to engineers via Figma's dev mode. Basic HTML/CSS familiarity is valued but not required at most companies.