Summary: Most designers believe they are being dismissed when their work gets challenged. The reality is usually more uncomfortable: the problem starts from within. This article breaks down the three patterns that keep designers from advocating effectively for their own work — weak domain foundations, a fragile sense of professional standing, and a tendency to experience challenge as confrontation. Through a real story about a project manager who pushed back on everything, he explores why challenge is not the enemy of good design work — and why waiting for a better environment to fix these patterns is not a strategy.
There is a kind of meeting that most designers have experienced at some point in their career. The kind where you walk in with solid work, a clear rationale, and a good understanding of the problem — and you still walk out feeling like nothing landed. The work gets challenged, the decisions get questioned, and by the end of it you feel more like a vendor defending a quote than a professional sharing a considered point of view.
Many designers mistake a credibility problem for a communication problem. I have had that experience more times than I care to admit. And for a long time, I thought the problem was communication — that I needed to get better at presenting, at reading the room, at speaking the right language to the right people. That is partly true. But it is not the whole story.
The real pattern I kept seeing — in my own work and in conversations with other designers — goes deeper than communication skill. It comes from three things that tend to show up together, and that feed into each other in ways that are easy to miss from the inside.
The first one is domain knowledge. Or the lack of it.
This one is uncomfortable to talk about because it feels like an accusation. But it is the most important of the three, and it is worth being direct about.
When a designer does not have deep enough foundations in the discipline, they cannot reliably defend design decisions — not because they lack confidence, but because they do not have enough solid ground to stand on. I have seen this happen often: a design decision gets challenged, and instead of responding with reasoning grounded in research, usability principles, or information architecture, the designer retreats into preference. “This feels cleaner.” “I think users would prefer this.” Which, to everyone else in the room, sounds like opinion. Because it is.
The uncomfortable truth is that a lot of what gets called a design decision is not actually a design decision. It is a subjective call dressed up in design language. And the moment someone pushes back on it with any rigour, it collapses. This is not a communication problem. It is a knowledge problem. And no amount of better presentation will fix it.
The second pattern is harder to see because it lives inside the designer’s head.
I call it the “you’re just a designer” syndrome — not because that is what other people say, but because it is what many designers have quietly internalised. When I ask designers what they do, a surprising number say some version of “I’m a UX designer” — as if that were a complete answer. But that is a title, not a role description. And if you cannot articulate what you are actually responsible for, you cannot expect anyone else to treat that responsibility seriously.
The way other people see your role in an organisation tends to track closely with how you see it yourself. If you act like someone who makes screens, you will be treated like someone who makes screens. If you act like someone who is responsible for whether the product actually works for the people using it — and what that means for the business — you will eventually be treated that way. Not immediately. But eventually.
The third pattern is where the first two land.
When a designer is not sure of their foundations, and not sure of their own standing, any situation that involves defending or challenging a decision starts to feel like a confrontation. Not a discussion. Not a part of the work. A confrontation — something to manage, survive, or avoid.
A few years ago I worked with a project manager who was genuinely exceptional at what he did. From the very first meeting, every session with him felt like a fight. He challenged everything. Not because he was difficult — I understood that later — but because that was how he thought through problems. He pushed until something held. After two or three weeks of this, at the end of one of our meetings, he told me he loved working with me. That he looked forward to our sessions.
I was stunned. I had been thinking about how to reduce how often I had to talk to him.
What I eventually realised is that he was not trying to win anything. He was trying to find out what was actually solid. The moments where I held my ground and came back with clear reasoning — not louder, not more defensive, just more grounded — those were the moments he trusted me most. Not the ones where I accommodated him. Not the ones where I said “good point, I’ll reconsider.” The ones where I said “no, and here is why.”
That experience changed how I understood challenge in design work. Challenge is not confrontation. Challenge is the work. It is how good decisions get separated from comfortable ones. And if every challenging question feels like a personal attack, the problem is not the question — it is the relationship the designer has with their own expertise.
Weak foundations make it harder to hold a position. Harder to hold a position makes the designer’s sense of their own standing fragile. Fragile standing makes challenge feel threatening. And once challenge feels threatening, the designer stops engaging with it — which means the work never gets pressure-tested, which means the foundations never get stronger.
It is a closed loop. And waiting for a better environment to break it is not a strategy. Better environments help, and I have written about the organisational side of this before. But no environment is perfect. The question is whether you can hold your ground — and keep improving — even in the ones that are not.
That is where the responsibility actually sits.
More articles: https://medium.com/@attila.ando.aa
Website: https://attilaando.com/
