# Judd Antin's Perspective on Saying No

Judd Antin's article is useful because it reframes "no" as a leadership move rather than a withdrawal. The goal is not to shut people down. The goal is to turn a request into a better conversation about need, tradeoffs, capacity, and priorities.

The strongest part of the article is the structure. Instead of treating every refusal the same way, Antin outlines three forms of no:

- A **Yes No** says yes to the need but no to the exact ask.
- A **Material No** says yes if the necessary time, people, or inputs are available.
- A **Priority No** says yes only if everyone agrees on what this new request should replace.

That matters because many people either over-accommodate or become abruptly dismissive. This framework helps you stay collaborative while still protecting focus and making tradeoffs visible. It is especially valuable in managing up, cross-functional work, and any environment where saying yes to everything quietly creates worse outcomes.

Antin makes an important point about why flat refusals fail. When you say no without context, the other person has no way to distinguish between "I disagree with the idea," "I do not have capacity," and "I think there is a better approach." All three are different situations that call for different responses, but a bare no collapses them into one signal: rejection. By naming which type of no you are giving, you keep the conversation productive and give the requester something to work with.

The Yes No is particularly useful for managers who receive requests that are directionally right but wrong in scope or approach. Instead of either accepting a poorly scoped project or appearing uncooperative, you can redirect: acknowledge the underlying need, then propose a version that actually makes sense. This moves you from gatekeeper to collaborator. The Material No works well when resources or information are genuinely the bottleneck. It makes the constraint visible without making the refusal personal. And the Priority No is the most powerful tool for managing up, because it forces the conversation every overloaded team needs: if this is now the priority, what are we deprioritizing?

One of the underappreciated aspects of the article is its treatment of the emotional dynamics at play. Saying no triggers discomfort on both sides. The person asking may feel dismissed. The person declining may feel guilty or worry about damaging the relationship. Antin's framework reduces that friction because each form of no includes an implicit offer of collaboration. You are not closing a door. You are opening a different, more realistic one.

## Key ideas to carry into practice

- A good no often sounds like a conversation about the real need, not a flat rejection.
- "Yes, if..." is often more productive than "No, because..." when the issue is capacity or missing inputs.
- Priority conversations get better when you force explicit tradeoffs instead of silently adding work.
- Saying no well can increase trust because it makes your reasoning legible.
- Name which type of no you are giving so the requester can respond to the real constraint, not just the refusal.
- The better you are at naming constraints and alternatives, the less defensive a no tends to feel.

## Common questions

**Q: How do I say no to a new request from my manager without sounding unhelpful?**  
**A:** Use a Priority No. Try: "Yes, I can take that on. To do it well, I would need to move one of the current priorities. Should this replace the roadmap recap or the customer analysis?" That keeps you collaborative while making the tradeoff visible.

**Q: What if the request itself is not quite the right solution?**  
**A:** Use a Yes No. For example: "Yes, I see why this feels urgent. I do not think a full new project is the right answer, but I can do a quick analysis of the last two customer calls and give you a recommendation by tomorrow." You are saying yes to the underlying need while redirecting the ask.

**Q: What is the difference between a Yes No, a Material No, and a Priority No?**  
**A:** A **Yes No** says yes to the underlying need but no to the specific ask, offering a better alternative. A **Material No** says yes if you get the resources, time, or inputs required to do it well. A **Priority No** says yes only if the requester agrees on what it should replace. All three keep the conversation collaborative instead of shutting it down.