How to say no.

Why no feels so risky

No is hard because it sets two things you care about against each other: protecting what matters to you, and staying on good terms with the person asking. In The Power of a Positive No, Ury describes the ways people usually handle that tension. Accommodating keeps the peace, but you pay for it. Attacking protects your interests and bruises the relationship. Avoiding manages to do both badly, just more slowly.

What he offers instead is a way of saying no that balances power and relationship while still serving your interests.

The Positive No

Ury's shorthand for it is Yes! No. Yes? The first yes is to your own interests, whatever it is you're protecting. The no is the limit, said clearly. The second yes is a proposal, an invitation to something that could work for both of you.

What we like about this is that it separates the request from the person. In Ury's framing, you're asserting your interests without rejecting them. You can turn down what someone wants and still treat them with respect.

Say a colleague asks you to cover their weekend on-call shift for the third month in a row. A Positive No might sound like this: "I'm keeping my weekends for my family, so I can't do this one. I'm happy to swap a weekday shift with you if that helps."

Say the no plainly

Soft wording invites another try. "I'm not sure I can" tells the other person the door is still ajar, so naturally they push on it. Saying clearly what you can't do, with one short reason, can feel harsh in the moment. It also saves you having the same conversation three more times.

Long explanations cause their own trouble. Every reason you offer becomes a problem for the other person to solve, and before long you're debating your reasons instead of your answer.

Let the other side say no too

Jim Camp comes at this from the opposite direction in Start with No. He wants you to invite the other side to say no. In one of his examples, a cold caller opens by telling the prospect that if the product isn't relevant, they can just say so and he'll leave them alone. Camp's argument is that giving people explicit permission to decline takes the pressure off and brings the real issues out sooner.

Chris Voss makes a similar case in Never Split the Difference, where he treats no as the point where a negotiation really gets going. When people feel free to refuse, they also tend to feel safe enough to tell you what they actually need.

When they push back

Expect your first no to be tested. Ury is clear that delivering it isn't the end of the job. You still have to deal with the reaction and help the other person get to yes on what you've proposed. Try not to build a brand-new argument every time. Acknowledge that they're frustrated, restate the no more briefly than before, and point back to the option that's still open.

One more thing: don't threaten consequences you won't follow through on. People pick up quickly on a boundary that isn't real, and they'll start testing to find where your actual limit is.