Table of Contents
- Stakeholders don’t care about UX
- Mistake #1: Treating stakeholders like students
- Mistake #2: Forcing understanding instead of creating pull
- Mistake #3: Explaining design instead of showing its utility
- How to build UX advocacy that actually sticks
- What actually worked for me
- 1. Training without preaching: “What is UX”
- 2. A monthly newsletter that did one thing well
- Why these worked when “education” didn’t
- Design advocacy is a political arena (whether we admit it or not)
- What actually changed my approach to stakeholder buy-in
Do not index
Read time: under 7 minutes
Stakeholders don’t care about UX
At some point, most designers working in a non-design organization reach the same conclusion:
“They don't get UX. We need to educate them.”
It sounds reasonable. Generous, even. If people understood what we do, why research matters, how design decisions compound, why "just make it pretty" misses the point—things would be better.
So we build decks. We schedule workshops. We explain process diagrams that took years to internalize. And then something strange happens.
People nod. They say "this is interesting." But nothing changes.
Design is still looped in late. Decisions still get made elsewhere. And "education" quietly turns into frustration.
This is the mistake: We treat education as neutral and in non-design organizations, it isn't.
Designers often approach stakeholder education like a classroom problem:
- They don't know → we teach
- They understand → behavior changes
But organizations don't run on knowledge alone. They run on incentives, authority, time pressure, and politics, whether we like that word or not.
When you try to educate stakeholders, you're not just sharing information. You're 1) questioning how decisions are made, 2) challenging existing expertise and 3) implying something could have been done better.
That makes education a political act, even when your slides are calm and well-designed.
Most designers don't fail at stakeholder education because their content is wrong. They fail because they misunderstand the arena they're stepping into.
Mistake #1: Treating stakeholders like students
One of the fastest ways to lose influence is to sound like a teacher in a room full of adults who already have power.
This usually shows up as:
- “Let me walk you through our UX process.”
- “Here’s why users behave this way.”
- “Research shows that…”
Even when correct, this framing subtly puts designers above the room. And people rarely accept lessons from someone they don’t already see as relevant to their goals.
In non-design orgs, stakeholders are not asking: “What is good UX?”
They are asking:
“Will this slow us down?”“Will this make my team look bad?”“Will this affect my targets?”
If your education doesn’t connect to those questions, it will stay theoretical.
Mistake #2: Forcing understanding instead of creating pull
Another common failure mode: mandatory learning without context.
Designers feel unheard, so they push harder.
- Required UX decks in meetings
- Workshops people didn’t ask for
- Long explanations when time is already tight
The intention is good. The effect is resistance.
Forced education triggers the same response as forced change: people comply outwardly and ignore it later.
Understanding sticks only when people need it. Which means advocacy often works better when it’s indirect.
Mistake #3: Explaining design instead of showing its utility
Designers love explaining how they work. Stakeholders care about what changes when designers are involved.
There’s a difference.
Saying:
“We do discovery, synthesis, ideation, and validation.”
Feels abstract.
Showing:
“This decision avoided three months of rework.”
Feels concrete.
In non-design orgs, design becomes credible when it is tied to outcomes people already care about: speed, clarity, risk, cost, confidence.
Not taste. Not craft. Not frameworks.
How to build UX advocacy that actually sticks
The most effective design advocates don’t try to convert people into designers. They translate design into the organization’s existing language.
This means:
- Framing research as risk reduction
- Framing usability as operational efficiency
- Framing clarity as decision speed
It’s less satisfying than talking about design ideals. But it’s also far more effective.
What actually worked for me
I learned this the slow way… by trying to educate, failing, then changing tactics.
Here are two things my team did that genuinely shifted how design was perceived in a non-design organization.
Not overnight. Not dramatically. But measurably.
1. Training without preaching: “What is UX”
Instead of pushing ad-hoc workshops, we partnered with HR and added a monthly session to the onboarding process.
Every new employee adjacent to product development; QA, developers, PMs, analysts, went through a session called: “What is UX?”
Not:
- “Why UX matters.”
- “How to do UX.”
- “Design thinking fundamentals.”
The goal was simple: Explain what we actually do, why it exists, and how other teams can work with us.
_2.jpg?table=block&id=2fe2a971-edb7-804e-81ad-c6a1887b96f4&cache=v2)
What we included:
- The kinds of problems UX works on
- What UX does and does not do
- How design decisions show up downstream
- Examples of real projects we worked on
- How non-design roles could involve us earlier
No evangelism. No superiority. No jargon Olympics.
The part everyone remembered
The session ended with Stanford d.school’s Gift-Giving (Wallet) Exercise, a hands-on introduction to design thinking that requires no prior knowledge.
People paired up, interviewed each other, synthesized insights, and designed a solution under time pressure.
They didn’t “learn UX.” They experienced what it feels like to design with intent. That difference mattered.
The result
By embedding this session into onboarding, we removed the need to convince people to attend. It wasn’t extra work; it was part of joining the company.
Within three months, we trained over 300 people.
Not to become designers but to understand when and how design could help them.
That understanding showed up later in better questions, earlier conversations, and fewer defensive reactions when design pushed back.
2. A monthly newsletter that did one thing well
The second shift was quieter. We started a monthly design newsletter sent company-wide.
It did not 1) teach theory, 2) argue for importance or 3) explain frameworks.
Instead, it highlighted:
- Small wins
- Projects in progress
- Decisions that changed direction
- What the design team was focused on
The purpose was visibility, not persuasion.
Over time, this did something subtle: It made design feel present without being loud.
People started connecting outcomes to design involvement. Not because we said “UX did this,” but because they kept seeing design show up where progress happened.
Why these worked when “education” didn’t
Both initiatives shared the same traits:
- They weren’t framed as a correction.
- They respected existing roles.
- They reduced uncertainty instead of increasing it.
- They met people where they already were.
Most importantly, they didn’t ask stakeholders to care about design. They made the design team easier to work with.
Design advocacy is a political arena (whether we admit it or not)
If there’s one thing I wish designers were more honest about, it’s this:
Design advocacy is not about being right.
It’s about being effective inside systems that weren’t built for you.
That means:
- Understanding who holds decision-making power
- Noticing which arguments land and which don’t
- Choosing when to push and when to step back
Education that ignores power dynamics becomes noise. Education that respects them becomes influential.
What actually changed my approach to stakeholder buy-in
I stopped asking:
“How do we educate stakeholders about UX?”
And started asking:
“What makes good decisions easier for them to say yes to?”
That question led to fewer decks. More conversations. Better timing. And a lot more patience.
A few hard-earned reminders:
- You don’t need people to agree with design. You need them to trust its role.
- You don’t need to teach theory. You need to reduce friction.
- You don’t need buy-in everywhere. You need alignment in the right places.
- You don’t need to win arguments. You need to survive the system long enough to shape it.
Design doesn’t lose because people don’t understand it.
It loses when designers misunderstand how organizations actually work. And once you see that, advocacy stops being loud and starts being durable.
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. Job Sprint Course: Stand out in an unpredictable job market by building a memorable personal brand and a killer job search strategy.
