How to Push Back on Stakeholders and Win (Real Examples)

Do not index

Read time: under 5 minutes

Staying silent can ruin your UX career

The spine you never grew might just be the reason you’re failing.

Let me be brutally honest for a second: not having a spine in your career is a fast track to failure.

This isn't just about design; it's about life. The moment you fold under pressure or allow stakeholders to bulldoze your ideas without a fight, you're setting yourself—and the project—up for disaster.

You’re the expert. You know what’s best, yet the fear of confrontation or simply not being “liked” holds you back.

But here’s the kicker: silence equals agreement. If you don’t speak up, the mistakes pile up, and before you know it, you’re knee-deep in avoidable issues.

You need to be prepared to fight for your ideas. And no, I’m not saying pick a fight with every stakeholder or turn every meeting into a battlefield. I’m talking about confidently pushing back when the situation calls for it, backing up your expertise, and guiding the ship in the right direction.

In my career, I’ve had successes when I pushed back and failures when I didn’t. Let me walk you through both.

Story #1: Building a culture of confidence

At Wizeline, I transitioned from a UX Lead to a UX Manager, and we were taught one key principle: we are consultants.

This wasn’t some corporate lip service. We were trained to believe that as designers, our job was to give expert advice, not just take orders.

Our culture was built on pushing back—always. If a client had an idea that wasn’t aligned with the product’s goals or user experience, it was our job to voice that.

The key to success? We never blindly followed what the client wanted. Sure, we listened extensively. But we were paid for our expertise, so we acted like it.

Every designer on the team was encouraged to speak up. We ran kickoff meetings, led strategy workshops, and took control. Not project managers. Not engineers. Designers.

I remember one particular client who came in with a strong preconceived idea of what they wanted. They were dead set on certain features.

But after several workshops, we confidently pushed back, presenting the data, explaining the user needs, and ultimately turning their heads around.

Not only did they thank us for it, but the product was a massive success because we stuck to our guns.

📌 Lessons learned:

Be the expert: Clients (or stakeholders) are looking to you for guidance. Don’t just agree; provide insight, backed by research.

Build a culture of speaking up: Your team should know it’s okay to challenge the status quo. Empower them to voice their opinions.

Lead from the front: Don’t hide behind other departments. You know the users and the product better than anyone. Take charge in meetings and workshops.

Don’t let clients dictate design: They don’t always know what’s best. Your job is to present them with the right direction, even if it’s uncomfortable.

Story #2: The price of staying quiet

Now, let’s talk about what happens when you don’t push back. In my first official design role at TINYpulse, I found myself in an intimidating situation. I was the sole designer, reporting directly to the CEO and the co-founder, who also happened to be the head of product. It was a lot of pressure.

I didn’t know how to advocate for myself or my designs. Everything was new, and I felt like I didn’t have the experience to say “no” or suggest alternatives. Instead, I just took orders.

We redesigned our platform several times based on feedback from leadership, never really questioning whether it was the right move.

The result? We ended up redesigning the second product five times before it even launched. And guess what? The product flopped.

Why? Because I didn’t push back. I wasn’t confident in saying, “This approach isn’t working.” I didn’t advocate for user-centered design. I just followed instructions, thinking it was safer to stay quiet.

📌 Lessons learned:

Push back, even when you’re unsure: You don’t need all the answers to question decisions. Trust your gut and your expertise.

Self-advocacy is non-negotiable: Learn to advocate for your designs and yourself. If you don’t, no one else will.

Don’t be afraid of leadership: Just because someone holds a higher title doesn’t mean they always know better. Your insights are valuable.

Silence isn’t safety: Staying quiet might feel like the safer option, but in reality, it leads to failure. Speak up, even if it’s uncomfortable.

Key takeaways

Conclusion: You’re the expert. Start acting like it.

Look, at the end of the day, pushing back is about more than just defending your designs. It’s about owning your expertise and not allowing anyone; whether it’s a client, a stakeholder, or a CEO to push you into decisions that you know are wrong.

The consequences of staying silent aren’t just failed products—they’re lost opportunities for growth, both for you and your team.

If you want to succeed, you need to get comfortable with the uncomfortable. Have those tough conversations. Push back when necessary. And always remember: silence won’t protect you, but confidence will.

👉

Whenever you're ready, there are 4 ways I can help you:

1. Junior Designer Bundle: Transition into UX with my playbooks: breaking down portfolios, applications, and UX frameworks, to build a solid career foundation. Craft an unforgettable portfolio & get hired.

2. Senior Designer Bundle: Become a design leader with systems to build healthier, happier teams and grow you and others meaningfully. Join 500+ aspiring leaders.

3. UX Portfolio Critique: Get a 20-minute video of brutally honest feedback, a checklist of things to fix, in less than 48 hours. Get a personalised portfolio critique here.

4. Job Sprint Course: Stand out in an unpredictable job market by building a memorable personal brand and a killer job search strategy. Get hired in UX with Job Sprint.