Table of Contents
Do not index
Do not index
Read time: under 5 minutes
How UX teams learned to stop telling the truth
Design is supposed to make things clearer. However, the more design meetings I attend, the more confused I become. It’s not the tools, the tech, or even the tight deadlines.
It’s the language. The well-polished, carefully crafted, totally useless language we keep using to avoid telling the truth.
Somewhere along the way, we traded honesty for performance.
We stopped saying what we meant. We started dressing up indecision as flexibility. We labeled chaos as collaboration. And instead of calling out bad ideas or unfinished work, we wrapped them in shiny phrases that sounded thoughtful enough to slide by.
It worked. Too well, actually. Now we’re stuck in this loop of saying a lot without really saying anything at all.
And we all do it.
Senior designers are trying not to step on toes. Juniors are afraid to admit they’re lost. PMs are running damage control. Stakeholders are hoping to move fast without sounding reckless.
We hide behind phrases like "we're still validating" or "just a high-level overview," because it feels safer than confronting the mess out loud.
But that safety is fake.
That kind of language doesn’t protect the work; it just delays the fallout. The more we rely on soft talk, the harder it becomes to make progress. Decisions stall. Feedback becomes a guessing game. Teams spin in circles because nobody wants to be the first to say, "This isn't working."
It’s a form of theater.
A polite performance we all agree to participate in, so we can move on with our day. It keeps things pleasant on the surface, but underneath, it chips away at trust. The kind of trust that makes real collaboration possible. The kind of trust that gets good work shipped.
So let’s break the fourth wall for a minute. Let’s talk about the lines we deliver and the meaning behind them. Because if we can’t even be honest with each other, we’re not going to be much help to the people we’re designing for.
Join 11,253+ Designers for FREE weekly UX Insights
Every Wednesday, I send out 1 actionable framework to grow your UX career 🌱 — No fluff. Always 2 minutes or less.
What UX designers say vs. What they actually mean vs. What happens anyway
Let me break the fourth wall. Because if we can't be honest with each other, we won't help the people we're designing for.
ㅤ | What we say | What we mean | What happens |
When projects go wrong | "This is just a first iteration." | "We didn't have time to think this through. Please don't critique it too hard." | That exact version gets shipped. The bugs go live. Your name is on it. |
ㅤ | "We'll test and iterate." | "We'll launch it and hope it doesn't explode. We probably won't test anything." | The feature tanks. Users complain. Everyone acts shocked. |
ㅤ | "We'll revisit this after launch." | "We will never look at this again." | The rushed version stays live. For years. |
When teams can’t decide | "We need stakeholder alignment." | "Everyone disagrees and we're hoping another meeting will fix it." | People nod. Cameras stay off. You leave with even less clarity. |
ㅤ | "We're still exploring." | "No one wants to make a decision yet. So we'll keep noodling." | Deadlines get closer. Exploration turns into stalling. A half-baked version gets rushed through. |
ㅤ | "This is a high-level overview." | "We didn't land on anything concrete, so here's a vague deck with lots of arrows." | Someone asks a specific question. You break into a cold sweat. |
When communication breaks down | "We want to hear feedback from everyone." | "We've already made the decision, but we want you to feel included." | Feedback gets collected, summarized, and ignored. |
ㅤ | "We're open to all ideas." | "I'm not going to do the hard work of evaluating them." | Ideas get dismissed without consideration. The loudest voices win. Innovation dies quietly. |
ㅤ | "Let's keep communication open." | "I'm going to ignore your emails until it's convenient." | Misunderstandings multiply. Deadlines get missed. People resent each other. |
When responsibility gets fuzzy | "We all share responsibility for this project." | "I'm going to do the bare minimum and blame you if it fails." | Resentment builds. Team morale tanks. The project barely survives. |
ㅤ | "Take the lead on this feature." | "I don't want to deal with it, so it's your problem now." | You get stuck juggling more tasks while others coast. |
ㅤ | "We value transparency." | "We'll share just enough info to look good but keep the messy stuff hidden." | Everyone's in the dark about real issues. Problems fester until they explode. |
When deadline looms | "Let's take a look Monday morning with fresh eyes." | "It's Friday 5pm. My brain has left the building." | Monday comes. No one opens the file. Everyone pretends it never happened. |
ㅤ | "We're committed to deadlines." | "We'll push features out unfinished and hope no one notices." | Technical debt skyrockets. User frustration grows. The cycle repeats. |
ㅤ | "We're optimizing for business goals." | "It's probably a dark pattern, but marketing said we need more conversions." | Short-term gains, long-term damage. Users bounce. The dashboard looks good for a while. |
Why honest communication matters
The words we use shape the work we do.
If we’re constantly softening our language to avoid discomfort or hiding behind vague promises, we’re not helping anyone. Not our teams. Not our stakeholders. And not our users.
Design is messy. It’s full of unknowns, dead ends, trade-offs, and sometimes, uncomfortable people behaviors. That’s exactly why it needs a clear, honest conversation. Not bravado. Not buzzwords. Not corporate theater.
We don’t need more polished updates. We need more uncomfortable truths.
We need to call out when laziness hides behind “open to ideas” but means “I don’t want to think.” When “shared responsibility” actually means “pass the blame.” When “transparency” is just a mask for silence.
This doesn’t mean you have to be blunt or rude. You don’t need to burn bridges or fight everyone in Figma comments. But you do need to start saying what you mean, especially when you notice toxic patterns creeping in. Even when it feels awkward. Especially when it feels awkward.
Once you stop pretending, real progress starts.
You make decisions faster. You call out bad behavior before it becomes a culture problem. You learn from actual mistakes instead of sugarcoating them. You build trust with people who know you'll tell it like it is, not just what they want to hear.
And maybe, just maybe, you put on fewer performances, call out the real issues, and ship better work instead. The users deserve that. Your team deserves that.
And honestly, you deserve that too.
Whenever you're ready, there are 4 ways I can help you:
1. Junior Designer Bundle: Transition into UX and craft an unforgettable portfolio & get hired.
2. Senior Designer Bundle: Become a design leader with systems to build healthier, happier teams.
3. UX Portfolio Critique: In less than 48 hours, get your 30-minute personalised video of brutally honest feedback.
4. Job Sprint Course: Stand out in an unpredictable job market by building a memorable personal brand and a killer job search strategy.
