A clean no

It is 4:55 on a Friday and your own manager has just dropped something on you that will eat the weekend. You type “no problem”, because no felt like it needed a case, and you did not have one ready, and the silence while you built one would have been worse.

The problem is rarely that managers cannot say no. It is that they say it with six reasons attached, and every reason is a handle for the other person to pull.

Why your no goes soft

Watch what happens when you pile up justifications.

“I would love to, it is just that the migration is running late and Priya is off next week and I have got the board pack on Tuesday and honestly the team is already stretched.”

You have now offered four problems, and a reasonable person will start solving them. Priya comes back Thursday. The board pack can slip. And so on, until you are arguing about your own staffing rota instead of the answer, which was no.

A clean no has four parts and the last one is the difficult one.

1. The decision, first. “I cannot take this on.” Not at the end, after the run-up. First.
2. One reason. The real one. One reason is a position; four reasons is an opening bid.
3. What you can do, if anything is honestly available. “I can look at it after the 14th” or “Sam could take the first pass”.
4. Then stop talking. The silence after a no belongs to them. Filling it is how you end up saying yes in instalments.

Saying no upward

Most of the anxiety here is about your boss, and the usual advice, be assertive, is useless because assertiveness is not the missing ingredient. Information is.

HBR’s three ways to say no to your boss all come down to the same move: make the trade-off visible and hand the decision back.

I can do this, or I can have the migration finished by the 14th. I cannot do both. Which would you rather have?

That is not a refusal, it is a choice, and it is a choice they are better placed to make than you. It also quietly does something else: it puts on the record that the capacity question was raised, and who decided what.

Lara Hogan’s delegate or decline is the thing to read before that conversation, not during it. Work out what actually comes off your plate first, so that when you are asked what would slip, you have an answer instead of a feeling.

When they keep pushing

The reflex when a no does not take is to find a better reason. Do not. New reasons signal that the last ones were negotiable.

The broken record is exactly what it sounds like. Acknowledge what they said, then repeat your sentence, calmly, in roughly the same words, as many times as it takes.

“I understand it is urgent. I cannot take it on this week.” “I know the client is asking. I cannot take it on this week.” It feels rude for the first two rounds and completely normal by the third. What makes it work is that it gives the other person nothing new to argue with.

The peer who wants your best engineer for “just two weeks”

This one gets people because it is framed as a favour between colleagues, and the cost is invisible to the person asking.

Make it visible, without making it a fight. “If Anya goes for two weeks, the payments work does not happen this month, and it is already committed. I cannot do that. What I can do is give you half a day of her time to unblock your design.”

No, then an offer. The offer is what keeps the relationship, and it has to be something you can actually afford, or you have made a promise instead of a boundary.

The boundary that has already been crossed forty times

The 11pm Slack is not a single event, so do not raise it as one. Raise the pattern.

Crucial Learning’s note on broken boundaries is right that the conversation has to name the repetition rather than the incident, otherwise you are having a small argument about one message.

There is one part of this that is entirely within your control, and it is not their behaviour. It is your reply times. You taught them that messages at 11pm get answered at 11pm, because for two years you were their peer and you answered. So say what you are changing: “I am not going to reply after seven any more. If something is genuinely on fire, ring me. Otherwise I will pick it up in the morning.”

Then do not reply after seven. That part is the whole policy.

The no that is not yours to give

Some noes come with a process attached, and improvising is how organisations end up at a tribunal.

A flexible working request in the UK is the clearest example. Since April 2024 it is a day-one right, you have two months to decide including any appeal, you have to consult the employee before refusing, and a refusal has to rest on one of eight statutory business reasons. Acas has both the guidance and the statutory code of practice. Read them before the meeting, not after.

The conversation still has to be had by a human being, and “the policy says no” is not a reason, it is a hiding place. Say which reason, say what you considered, and say what would change your answer if anything would.

Carrying a no you did not choose

The hardest version: you are delivering a decision you argued against. There are two ways to get this wrong and most people pick one of them.

You can pretend you agree, which your team will detect in about four seconds and never quite trust again. Or you can distance yourself, “this came down from above, I think it is mad too”, which buys you one comfortable afternoon and costs you your authority for the rest of the year.

Ron Carucci’s middle path is to be honest that it was not your call, clear that you are carrying it out anyway, and specific about what you did raise and what you will keep raising. You can say “I pushed on this and lost” without saying “and they were idiots”.

The thing nobody tells you is that a clear no is better for the other person too. A soft maybe leaves them planning around something that was never going to happen. The uncomfortable ten seconds buys them a week.