Most people say yes when they want to say no — then resent the person they said yes to. The cost isn’t just the time you lose. It’s the trust erosion that comes from overpromising and underdelivering.
The solution isn’t becoming more assertive. It’s building a routine that makes saying no automatic and low-friction.
The Real Reason Saying No Is Hard
Saying no feels risky because you’re afraid of what the other person will think. But the bigger risk is saying yes and then not delivering — or delivering late and rushed. One “no” is fine. A broken promise is remembered.
Your colleagues are not actually expecting you to say yes to everything. They’re expecting you to deliver what you commit to.
The Two-Part No
Step 1: Name the conflict briefly. You don’t need a long explanation.
“I’m at capacity on [project] right now.”
Step 2: Offer an alternative.
“Can you ask Jordan? Or if it’s not urgent, I can take it Thursday.”
That’s it. You acknowledged the request, stated your constraint, and offered a next step. The alternative is what separates a cold no from a helpful one.
The Three Types of No
1. The Busy No
“I’d like to help, but I’m fully committed to [X] through [date]. Can you check with [someone else]?”
This is the most common situation. You’re not declining the work — you’re declining the timeline. Be specific about your constraint so it doesn’t sound like a soft maybe.
2. The Boundary No
“That’s not something I can take on — [specific reason]. [Alternative resource] might be helpful.”
Boundary violations are when someone consistently asks you to do work that isn’t your responsibility. Be direct. “That’s not in my role” is not rude. It’s clarifying expectations.
3. The Strategic No
“I’m not the right person for this — [reason]. [Person] has handled this before and can do it faster.”
Sometimes the best thing you can do is point someone to the right person. This is doing your job, not being unhelpful.
How to Handle the Pressure Response
Some people push back when you say no. Here is how to handle the three most common pressure tactics:
“It’ll only take 5 minutes.”
It won’t. And if it did, they wouldn’t be asking. “I understand, but I’m not available for even short tasks right now — can we schedule for next week?”
“I really need this from you specifically.”
Often not true. If it is, they’ll wait. “What specifically requires me? If it’s something only I know, let’s schedule 15 minutes and I’ll document it so it doesn’t block you again.”
“Just this once.”
It never is. “I want to be helpful, but this would mean deprioritizing [current project]. What’s the priority between these two?”
What Not to Say
– Don’t apologize excessively (“I’m so sorry, I feel terrible, but…”)
– Don’t give a detailed justification that invites debate
– Don’t say “let me check and get back to you” if the answer is no
– Don’t make your no conditional on something you know won’t happen
A Real Example in Practice
A colleague asks you to take over a slide deck due tomorrow. You already have two deadlines.
The wrong response: “Uh… let me see if I can fit it in…” (you can’t, but now you said yes)
The right response: “I have [Project X] and [Project Y] due by end of week — I won’t be able to give the deck the attention it deserves. Sam on your team has done this before and could knock it out quickly. Want me to make the intro?”
You said no clearly. You offered a specific alternative. You explained why (quality, not availability). And you made the alternative easy by offering a small contribution.
The Templates That Help
Every one of these conversations is easier with prepared wording. The Office Email Templates Bundle has scripts for saying no to peers, declining manager requests, and escalating when boundary-setting isn’t working.