Designers get a bad reputation for saying “no.” And let’s be honest…we’ve earned it. We’re often the ones pumping the brakes on bad ideas, pushing back on impractical requests, or rejecting solutions that don’t meet user needs.
And then, there’s that designer. You know the one.
They sit in their tastefully minimalist office, surrounded by Bauhaus prints and an expensive but extremely uncomfortable chair (for aesthetic reasons). They wear all black—maybe a turtleneck, maybe a designer brand you’ve never heard of. When someone dares to bring them an idea, they slowly remove their handcrafted acetate glasses, sigh dramatically, and deliver the verdict:
"No. That’s not best practice."
No explanation. No discussion. Just pure, unfiltered design snobbery.
The problem? When designers act like this, people stop coming to us for input early, which is exactly when bad ideas take root. If we’re known for saying “no,” we’re seen as blockers, not go-to problem-solvers.
But design isn’t about rejection. It’s about creation. Our job isn’t just to prevent bad outcomes; it’s to generate great ones.
So, instead of shutting ideas down, what if we made space for better ones? What if we said “yes” by providing multiple options?
Designers as Creators, Not Blockers
There’s a common perception that designers continually squash “bad” ideas. If you've ever had to explain why a dropdown isn’t the best UI element (again), you know the struggle. The problem is, when designers are seen as obstacles, people stop bringing us into the conversation early, and that’s when truly suboptimal ideas take root.
But here’s the irony: Design is inherently about creating. We explore, experiment, and shape possibilities. We’re not supposed to be roadblocks; we’re supposed to be pathfinders.
Instead of rejecting an idea outright, we should be reframing the conversation.
Example: A product manager wants to add a feature that disrupts the user flow. Instead of saying, “That won’t work,” try:
“Would you be open to exploring a few other options to achieve your goal while minimizing user disruption? Here are a few ideas we’ve explored…”
Now, instead of being the person who said "no," you're the team who came to the table ready to empower product leaders with an even better solution. Now you’re shifting the conversation away from “no”, to “yes, let’s do this together”.
Why Saying “Yes, with Options” Changes Everything
People shut down when they hear “no.” It’s human nature. Rejection feels personal, even when it’s just a dropdown.
Offering options keeps collaboration open. It shifts the conversation from “Can we do this?” (a yes/no question) to “What are some different ways to do this?” (a discussion).
It also avoids the dreaded (toxic) power struggle. If someone brings you an idea and you shoot it down, it’s likely to create defensiveness. But, if you acknowledge the goal behind the idea and build on their idea or offer multiple alternatives, they’re more likely to engage. And, they see you going out of your way to help them improve their ability to meet their goals.
Example: A stakeholder suggests a UI treatment grabs attention but is distracting to a critical user task. Instead of saying, “No, we can’t do that,” say:
“I see why that’s appealing. It seems like you’re really trying to capture the user’s attention and drive action. Would you be open to considering some alternative ways to achieve a similar effect while keeping performance on this other critical task high?”
See? You’re not saying no. You’re redirecting the conversation toward holistically better solutions.
The Pitfalls of Only One Option
Yes, I’ve already written on this topic. But, it’s worth repeating. One option is a trap. If you only have one option, it’s the best one…because it’s the only option.
There are real risks in considering just one idea, or landing on the first option to pop up:
- It Creates a False Sense of Certainty: When there’s only one solution, it’s easy to assume it’s the best. But without alternatives, you’re just guessing. Multiple options allow you to weigh trade-offs and make informed decisions.
- It Ties Your Idea to Your Identity: When you present only one solution, it’s easy to take criticism personally. It becomes your idea rather than just another idea. Multiple options create distance, making feedback about the work…not about you.
- It Encourages a Fixed Mindset: A single solution feels like the right answer rather than a hypothesis. More options encourage iterative thinking, allowing teams to refine rather than defend.
- It Increases the Risk of Blind Spots: If you don’t explore multiple angles, you might miss key constraints, biases, or better alternatives.
The fix? Always explore multiple options. Always. Yes, even if you’re confident in your first idea.
How to Rethink Your Responses as a Designer
So, how do you handle when the black-turtleneck designer with you begins to emerge, ready to roll eyes and snub with a “no”? The next time you feel that coming on, pause. Reframe the conversation.
1. Avoid immediate rejection: Instead of “That won’t work,” try: “That’s an interesting challenge. Let’s explore some options.”
2. Offer multiple possibilities: Even if you have a preferred solution, give at least one alternative. “We could do it this way, or we could try this approach. Let’s discuss the trade-offs.” Better yet, try to anticipate and come ready to the discussion with some additional options.
3. Frame constraints as design challenges: Instead of “We can’t do that,” try: “Here’s what we’d need to adjust to make that work.”
When Options Aren’t Possible
Ok, but sometimes, a hard “no” is necessary like when ethical, technical, or business constraints make an idea completely unworkable. But even here, there’s helpful ways to say “no”.
Example: A request introduces dark patterns that manipulate users. Instead of “We don’t do dark patterns,” say: “That approach could undermine user trust in our product by pushing the user into a costly unintentional action. That will potentially lead to increased cancellation rate. If you’re open to other options, we might find a way to achieve the same business goal while avoiding the side effects of this option.”
Notice, you didn’t even say the word “no”, but it becomes clear that there are serious consequences to this option. It keeps the conversation open. And, you just spoke to more than one goal, helping them to balance their thinking.
Designing Better Conversations, Not Just Products
Saying “yes with options” isn’t just a design tactic. It’s how you become the person people want to work with. It’s how you win friends and gain influence.
Because here’s the thing: nobody wants to collaborate with the snooty designer in the turtleneck of judgment. They want the inventor in the back room, the one surrounded by sketches, a backlog of promising prototypes, and a whiteboard filled with ideas that look like madness but are really pure genius.
This is the person you go to when you’ve got a gnarly problem. They don’t just tell you why something won’t work. They show you five better ways it could. They don’t shut down ideas. They build on them. They create unexpected solutions. They turn constraints into advantages.
This is what great designers do.
When we stop being the people who say “no” and start being the ones who find better ways forward, we change how we’re perceived. We’re no longer gatekeepers to get around. We’re core collaborators that help them through their challenges.
