Early in my career, I thought great designers were the ones who said yes. Yes to features, yes to timelines, yes to being helpful, flexible, and easy to work with.

It took years … and some hard lessons … to realize that great design isn’t just about solving problems. It’s also about defining them clearly. That means saying no more often than we’re taught to.

Not in a dramatic, table-flipping way (although sometimes that would have been therapeutic). But in the quiet, steady way that protects the user, the craft, and the outcome.

Let’s talk about the situations where “no” is not only appropriate … it’s essential.

Say No to Feature Creep

Feature creep is seductive. Just one more toggle, one more filter … one more “nice to have.”

But often, each additional feature adds complexity without delivering proportionate value. It can dilute your core product, overwhelm users, and slow development velocity.

Designers should be asking:

• What’s the job the user is trying to get done?
• Does this feature help them do that more efficiently or does it distract them?

Push for focus, simplicity isn’t about doing less for the sake of minimalism. It’s about doing the right things well.

Say No to Rushed Timelines

There will always be deadlines, and there should be. That’s part of working in tech. But when you’re asked to “just mock something up real quick” without the time to research, test, or iterate … you’re not designing. You’re decorating guesses.

You don’t have to flat-out reject the ask. Instead, reframe it:

• “Here’s what we can do in that time.”
• “Can we consider launching this in phases?”
• “Let’s document the risks if we skip user validation.”

Time is a design constraint. But so is too little time.

Say No to Poor UX Patterns

You know them when you see them: dark patterns, deceptive CTAs, pop-ups you can’t escape, etc. Sometimes they come from well-meaning stakeholders trying to hit a number, your job is to provide the guidance through “no”.

Here’s the thing, if you’re in the room and you stay silent … well, you’re complicit.

Saying no here isn’t just about design. It’s about ethics, accessibility, and trust.

Push back when something feels manipulative or exclusionary. You’re not being “difficult.” You’re being a user advocate, and that’s your job!

Say No to Being Treated Like a Pixel Pusher

If you’re getting handed fully baked solutions instead of real problems to solve, it’s time to push back.

You weren’t hired just to make things look pretty. You were hired to help things work better.

Try asking:

• “What’s the underlying goal here?”
• “What’s the problem this screen or flow is trying to solve?”
• “Have we considered the user journey leading up to this?”

When you push for context, you elevate the conversation. That’s how you earn trust as a strategic partner, not just a service provider.

Say No Without Burning Bridges

Here’s the nuance: saying no doesn’t mean slamming doors. It’s about inviting better conversations.

Instead of “That’s a bad idea,” try:

• “Help me understand why this is important.”
• “Can we test this with users first?”
• “Here’s what I’m concerned about … does that make sense from your side?”

The goal isn’t to win every battle. It’s to make sure the right trade-offs are being made consciously, not accidentally.

Saying No Is a Form of Leadership

You don’t need “Manager” in your title to lead. Every time you advocate for clarity, challenge assumptions, or protect the user … you’re stepping into leadership.

Yes, saying no can feel uncomfortable. Especially if you’re early in your career, or working in a culture that values compliance over critique.

But the designers who make the biggest impact over time? They’re the ones who learned how to say no with confidence, respect, and with purpose.

I'd love to hear about your thoughts, connect with me on LinkedIn and let's chat.

Until the next volume, thanks for joining me. 
Andrew Preble