Is UX Design Stressful?

Watching engineering simplify my designs. Not because they're wrong to do it. Because they usually have valid technical reasons. But the thing that makes a design good is often the thing that's hardest to build. Last month I designed a progressive disclosure pattern for our settings panel. Instead of showing all 30 options at once, the panel would reveal sections contextually based on what the user had already configured. It tested well. Users completed the setup flow 40% faster in the prototype. Engineering looked at it and said, "We can't do the contextual reveal without refactoring the state management layer. That's a three-sprint effort." So we shipped all 30 options at once. The same settings page that tested poorly. The same wall of toggles.

My engineering partner, Vlad, was apologetic about it. He said, "I wish we could build it your way." I believe him. But the outcome is the same whether the reason is good or bad: the version users experienced in testing is not the version they'll use in production. And that gap is where my stress lives. Not in Figma. In the difference between the design that works and the design that ships.

Having no seat at the table. I've been at this company for three years. The product strategy meetings include the VP of Product, the VP of Engineering, the head of sales, and the CEO. Design is not in the room. We hear about strategy decisions after they've been made. Then we're told to "design the experience" for a feature that was scoped, prioritized, and committed to a customer before anyone asked whether it was the right thing to build.

Last quarter, sales committed to a custom reporting module for a Fortune 500 client. $800,000 deal. The commitment was made in a sales call. No research. No discovery. No design input. I found out when a Jira epic appeared in my queue with a note from the PM: "Design needed for custom reporting module. Timeline: six weeks." I asked what the user needs were. The PM said, "The client wants to export data to PDF with custom branding." I asked if we'd talked to the actual users at the client company. He said, "The buyer is the VP of Operations. He wants PDF exports." The buyer. Not the user. The person who signs the check, not the person who uses the software.

I designed the PDF export feature. It works fine. I have no idea if the people who actually use our software at that company need it or want it. I'll never know. That's the stress. Not the work. The irrelevance. I'm a senior UX designer and my job is to put a UI on decisions that were made without me.

Being the entire design team. There are 45 people at this company. I am the only designer. The only one. I do UX research, interaction design, visual design, the design system, icon design, marketing page layouts, pitch deck graphics, and occasionally the CEO asks me to "make the investor update look nicer." I am the design department and the marketing design team and the brand team and the presentation team and sometimes the front-end CSS person when engineering is behind.

Last week I was in a user interview at 10 AM, designing a clinical workflow screen at 1 PM, fixing a responsive layout bug at 3 PM, and creating social media graphics for a conference at 5 PM. Four completely different types of work requiring four completely different skill sets. And none of them got my full attention because I was switching between them all day.

My manager, the head of product Anil, says, "You're incredible, we couldn't do this without you." Which is true. And also means they should hire a second designer. They won't. The Series A money went to engineering. Design gets one person and a Figma license and the expectation that one person can do the work of three. Anil knows this. He's put "hire designer #2" in the roadmap for Q3. Q3 has been the target quarter for a second designer since I started. It's been Q3 for two years.

Stakeholder feedback that's actually just personal preference disguised as strategy. Our CPO, Diane, reviews every major design before it ships. Last month I presented a redesigned account overview screen. Clean layout, clear hierarchy, the key metrics at the top, transaction history below. Diane looked at it for about ten seconds and said, "Can we make the balance number bigger? I want it to feel more impactful."

The balance was already 32-pixel type. I'd sized it based on the visual hierarchy and the amount of information on the screen. Making it bigger would push the transaction list down and require scrolling on smaller phones. I explained this. Diane said, "I hear you, but I think bigger is better here. Let's try it." Which means: do it my way. "Let's try it" in executive language is not an experiment. It's a directive with plausible deniability.

I made it bigger. 44 pixels. The transaction list now starts below the fold on an iPhone SE. We shipped it. Nobody complained because nobody who uses our app has an iPhone SE except me, because I test on one. But the design is worse. I know it's worse. Diane doesn't know and doesn't care because the thing she cared about, the big impressive number, is there. And next quarter when we redesign it again, nobody will remember that the balance was 32 pixels and worked fine before Diane made it 44.

The layoffs. I've been through three rounds in eleven years. 2020, 2023, and 2024. The 2023 round, I survived but my entire team was cut. Three designers, gone. I was told to "absorb their projects." I went from managing three people and two client accounts to managing zero people and five client accounts overnight. My salary didn't change. My title didn't change. My workload doubled.

But the real stress is the ambient fear. Even when layoffs aren't happening, you know they could. Every time there's an all-hands meeting that isn't on the regular schedule, I feel my stomach drop. Every time the CEO says "we need to talk about the business," I start thinking about whether my portfolio is up to date. I've started keeping my resume current at all times. I update it quarterly. I have three portfolio case studies polished and ready. I maintain relationships with three recruiters. This is maintenance work for my own career survival and I do it on my own time because the company that might lay me off certainly isn't going to give me time to prepare for it.

My husband, Greg, says I'm catastrophizing. Maybe. But I've watched 40 colleagues get walked out in three years. The ones who weren't prepared took months to find new jobs. The ones who were prepared took weeks. I intend to be in the second group. And the energy I spend on that preparation is energy I'm not spending on my actual work, my family, or sleeping.

AI taking my job. I know that's the cliche answer. I know every thinkpiece says "AI won't replace designers, it'll augment them." But I'm 27. I'm junior. I do the work that AI is going to be best at replacing first: wireframes, basic UI layouts, screen flows. The conceptual stuff, the research, the strategy, that's harder to automate. But that's also the stuff senior designers do. I'm not a senior designer. I'm the person who turns a PM's requirements into a Figma mockup. And I've seen what Figma's AI features can do. What Galileo can do. What Vercel's v0 can do. It's not as good as me yet. But it's getting better every month and I've only been doing this for eighteen months.

My senior designer, Katya, says I should focus on skills that AI can't replicate: user empathy, stakeholder management, design strategy. She's right. But those are skills that take years to develop and I'm in a race against tools that are improving quarterly. I lie awake sometimes and do the math. If I need five years to become a strategic designer, and AI is improving at the current rate, will there still be junior designer roles in 2028? 2029? I don't know. Nobody knows. And the not knowing is the thing that sits in my chest at 1 AM on a Tuesday when I should be sleeping.

I haven't told Katya about the 1 AM part. She'd say I'm overthinking it. She's probably right. She's also 38 and has a decade of relationships, strategic skills, and institutional knowledge that makes her irreplaceable in ways I can't replicate by just working harder. I'm replaceable. I know it. Every junior designer knows it. We just don't say it because saying it makes it more real.