"So what do you actually do all day?" It's the question designers hear at family dinners, weddings, and parents' meetings. The short answer ("I design app and website experiences") never satisfies — it doesn't show the how, it doesn't show the rhythm of the craft, it doesn't show the 27 micro-activities that make up a real work week.
This article is the long answer. Instead of listing what a UX Designer does in the abstract — we've already done that here — let's look at three real days in three different contexts: one at a US SaaS scale-up, one at a design agency, one as a senior freelancer. Same craft, very different rhythms.
What you'll learn:
- How a UX Designer's day changes depending on the company context
- Recurring activities and episodic ones
- How much time is actually spent "designing in Figma" (spoiler: less than you think)
- How deep work and collaboration alternate
- The signs of a productive day vs a wasted one
Day 1: Mid-level designer at a SaaS scale-up
Context: Designer with 3 years of experience at an 80-person US fintech scale-up, product team with 2 PMs, 2 designers, and 12 engineers. Hybrid remote, 2 days in-office.
8:30 AM — Laptop open. A quick Slack scan of messages left by teammates in other time zones overnight. No meetings in the first hour.
8:45 AM — Opens the day's ticket in Linear: define the password recovery flow for the mobile app, which has a 62% success rate (target: 85%+). Reopens existing research findings in the Notion repository.
9:00 - 10:30 AM — Deep work block #1. Low-fidelity wireframes in Figma for 3 alternative flow hypotheses. Silent work, Slack closed, macOS Focus mode on. This is the only window of the day where actual design production happens.
10:30 - 10:45 AM — Product team daily stand-up. 15 minutes, video on, async update already posted on Slack ahead of time. Each person speaks for 60 seconds: what I did yesterday, what I'll do today, what's blocking me.
10:45 - 11:30 AM — Critique session with the team's other designer. I show the 3 password recovery hypotheses, she shows the week's work on the design system. Mutual, non-hierarchical feedback. 45 minutes of shared design thinking.
11:30 AM - 12:30 PM — Review of the case study for the new push notifications feature. The other designer is presenting it Friday to the extended team; I'm helping clarify the narrative. Time spent on communication, not design — but it's a part of the craft nobody ever tells you about.
12:30 - 1:30 PM — Lunch break. Outside the house, 20-minute walk. If I skip the walk, the day visibly gets worse after 3 PM.
1:30 - 2:00 PM — Slack reading + triage. Figma comments, PM requests, engineer questions about the design approved last week. I batch-reply to everything.
2:00 - 3:00 PM — Meeting with the Product Manager. Review of the 3 password recovery hypotheses. We discuss priorities, technical constraints, timelines. One hypothesis gets cut (too expensive), two survive. We decide to test one in a quick usability test by Friday.
3:00 - 4:30 PM — Deep work block #2. Refining the chosen hypothesis for testing. Adding states (loading, error, success), microcopy, transitions. Clickable prototype ready.
4:30 - 5:00 PM — Test setup in Maze: writing the 3 tasks participants will perform, sending the link to the research team's recruited user panel.
5:00 - 5:30 PM — Final Slack window. Checking the US West Coast colleagues' comments that just started rolling in. Quick response to 2 questions. Closing pending Linear items.
5:30 PM — Formal close. Laptop shut, notifications silenced until morning. The discipline of actually closing matters more than the discipline of opening.
How the day breaks down
- Pure Figma design: 3 hours (30%)
- Synchronous meetings and communication: 2h 15min (22%)
- Async review and comments: 1h 15min (13%)
- Triage and admin: 1h (10%)
- Planning / setup deep work: 1h 30min (15%)
- Breaks and recovery: 1h (10%)
The surprising stat: the designer spends less than half the day in Figma. The rest is all process, communication, coordination, and reflection.
Day 2: Designer at a multidisciplinary design agency
Context: Designer with 5 years of experience at a 40-person NYC agency serving B2B and B2C clients. Portfolio of 3-6 concurrent projects.
9:00 AM — Arrives at the office. The agency runs in-person by cultural choice; remote is allowed 1-2 days per week.
9:15 - 9:45 AM — Coffee and informal catch-up with the 3 other designers on the team. Today's topic: a project that went into crisis yesterday (client asked for a last-minute overhaul).
9:45 - 10:30 AM — Status call with one of the clients for the week's main project: redesigning the member area of an insurance portal. The client talks for 40 minutes; the designer takes notes and rephrases the requests in design terms.
10:30 AM - 12:00 PM — Deep work block on the portal project. Finalizing the flows for 3 sub-sections. Headphones on, no interruptions.
12:00 - 12:45 PM — Quick sync with the portal project's PM: alignment on budget, remaining hours, risks. Agencies work to fixed budgets; hour tracking is part of the craft.
12:45 - 2:00 PM — Team lunch. Agencies still have a strong shared-lunch culture. Conversation covers design, clients, trends, and who saw what on Dribbble.
2:00 - 3:30 PM — Internal workshop with copywriters to define the tone of voice for the portal's member area. Physical whiteboard, sticky notes, animated discussion. Output: a voice & tone doc with 5 key examples.
3:30 - 5:00 PM — Jumping to a second project (a mobile app for a food company): reviewing prototypes built by a junior colleague, written feedback inside Figma, small rework of 2 screens.
5:00 - 6:00 PM — Back to the portal. Preparing materials for tomorrow morning's client presentation: 15 selected screens, speaker notes, presentation script.
6:00 - 6:30 PM — Close-out: Slack, email, notes for tomorrow morning. Logging off.
How the day breaks down
- Pure design: 4 hours (38%)
- Direct client: 40 min (6%)
- Internal coordination (PM, team): 1h 15min (12%)
- Workshops and structured collaboration: 1h 30min (14%)
- Feedback and review: 1h 30min (14%)
- Breaks: 1h 15min (12%)
Key differences from the scale-up: more variety (3 projects in a single day), more time with external clients, more fixed-budget time management, less deep research, more finished deliverables in less time. The rhythm is more fragmented but also more stimulating for those who don't love the monotony of a single product.
Day 3: Senior freelance designer
Context: Designer with 8 years of experience, 3 years freelancing. Two fixed clients (one US, one German) + a spot project. Works from home, fully autonomous time management.
7:30 AM — Wakeup, breakfast, 45 minutes of professional reading (Nielsen Norman Group, Smashing Magazine, a book chapter). Not billable time but investment in personal growth.
8:30 - 9:00 AM — Computer on. Checking email, both clients' Slack, any tickets. Planning the day on a physical to-do list (long-held habit: digital for deliverables, analog for personal rhythm).
9:00 - 11:30 AM — Long deep work block. US client: designing the new onboarding for an HR SaaS. Two and a half hours of consecutive Figma work, no meetings. This is the freelance senior's superpower: protecting long concentration windows.
11:30 AM - 12:00 PM — Active break: 20-minute walk. For a freelancer, managing your body is part of managing the business.
12:00 - 1:00 PM — Call with the German client. Review of project progress, alignment on next milestone. English call, 45 effective minutes.
1:00 - 2:00 PM — Lunch and break.
2:00 - 3:30 PM — Second deep work block. German client: refining an analytics dashboard. Figma + small exploratory research on similar competitor patterns.
3:30 - 4:00 PM — Admin: last month's invoice to issue, a quote for a new client to close, replies to 2 LinkedIn inquiries from companies. A freelancer spends 15-20% of their time on non-project but necessary activities.
4:00 - 5:30 PM — Work on the spot project: a landing page redesign for a US startup. Flat-fee payment, contained hours, fast deliverable.
5:30 - 6:00 PM — End-of-day wrap-up. Updating projects in the tracking system (Toggl for hours, Notion for tasks). Closing both clients' Slack workspaces.
6:00 PM — Stop. A freelancer who doesn't impose discipline on their hours ends up working 10-12 hours a day and burns out in 18 months. Discipline is professional defense, not a luxury.
How the day breaks down
- Pure design: 6 hours (55%) — the senior freelancer defends more deep work than anyone
- Direct client: 45 min (7%)
- Admin and business: 30 min (5%)
- Professional reading: 45 min (7%)
- Breaks and recovery: 1h 20min (12%)
The defining characteristic: the senior freelancer has total control over their time. But the "luxury" of autonomy is paid for with zero safety net, end-to-end business management, and a level of discipline few employees manage to sustain.
What all three days have in common
Three constant patterns regardless of context:
- Deep work is the source of value. All three profiles protect 3-6 hours of solitary concentration per day. Without those hours, the design work flattens.
- Collaboration comes second, not third. After deep work, the most productive time is structured feedback: critiques, reviews, design reviews. Not email, not generic meetings — direct engagement with real work.
- "The rest" grows with seniority. Admin, coordination, strategy, mentorship — all activities that increase as you become senior. At principal/lead levels they can reach 60-70% of your time, leaving only 2-3 hours a day for pure design. For some that's a challenge; for others it's the real reason they choose to stay IC (individual contributor).
The signs of a productive day
Four checks to tell if your day is going well:
- Did you get at least 2 hours of uninterrupted deep work? If no, the day was scattered.
- Did you make at least one design decision defensible with data? If no, you only "executed."
- Did you communicate a decision to someone? Design is always a collective act; decisions made but not communicated are wasted.
- Did you actually close at the end of the day? If Slack is still open at 10:30 PM, the day didn't end — it overflowed.
Frequently asked questions
How much time does a UX Designer actually spend in Figma?
On average 30-50% of the day for mid-level roles. Less for seniors (more reviews and strategy), potentially more for juniors who don't yet carry coordination responsibilities. A senior freelancer with protected time can reach 55-60%. The idea that a designer "stays in Figma all day" is a myth.
Are there a lot of meetings in a UX Designer's job?
It depends on the context. A scale-up with an async culture has 1-2 hours of meetings per day. A traditional agency can have 3-4. Large enterprises with many stakeholders can push past 5 hours. Negotiating your own calendar is a skill you learn over years — and it makes the difference between burnout and sustainability.
Does a UX Designer work with engineers and product managers every day?
Yes, with both. The best designers have constant dialogue with engineers (to understand what's feasible) and with product managers (to understand what makes business sense). That's one reason the isolated designer "drawing in a room" hasn't existed for at least 10 years.
Is it a stressful job?
It depends heavily on the company and team. Places where design is respected and measured offer sustainable work with good work-life balance. Places where the designer is the last link in the chain, chasing others' decisions, are frustrating. The choice of first post-study company weighs enormously on the quality of your first 2-3 professional years.
What does a UX Designer do on weekends?
In companies with a healthy culture, nothing. Maybe read an article, attend an online event, but real work happens in the 5 weekdays. Those who regularly work weekends are either making bad choices (taking on too many projects, not knowing how to say no) or are inside a company with a toxic culture — in both cases the problem needs to be addressed, not normalized.
Next steps
If this realistic picture appeals more than the romanticized version of the craft, the next step is figuring out how to get there:
- Read what a UX Designer does for the complete picture of role and skills
- Study the 12-month roadmap for the operational path
- Explore the salaries in the field to understand the return on investment
CorsoUX's complete course trains you with the same rhythm and method as the designers working in the days described above, with senior mentors who live those days themselves.
