"No" is not a four-letter word.
Read time: 3 minutes / Subscribe to this newsletter
Hello Friend!
Last week, I told you about a serial people-pleaser, Anna.
She received a last-minute request on a Friday afternoon with a tight Tuesday deadline. Like she was usually prone to do, she gave a reflexive yes.
The problem? She was out on Monday. And because she never clarified the request, she quickly learned it would be a coordination nightmare with an external third party.
The yes paradox is that in our eagerness to win the affection and respect of our co-workers, we agree to things that aren’t realistic to deliver. We end up in a scramble. Rework ensues. Instead of earning credibility, we hurt ourselves.
You can remind yourself of her full story here, and a simple process for turning a reflexive yes into a real yes.
This week, I’m covering how to deliver a thoughtful “no,” “not yet,” or revised timeline without damaging trust.
The Hardest Room to Say No In
Here’s what makes a moment like Anna’s so difficult.
It’s not the ask itself. It’s the audience.
When someone with positional authority or a valued peer assigns you work in front of a group, your nervous system reads it as high-stakes. Your brain floods with adrenaline. Blood goes to your hands and feet.
Literally, the prehistoric wiring to get out of danger. And in that state, you cannot do your best thinking. You just want it to be over.
So you say yes. Not because it’s the right answer. Because the room is watching and yes is the fastest exit.
But here’s something I want you to know: you don’t have to resolve it in the room.
You can simply respond, “I can help with that.” It’s not the same as yes. It’s a landing pad. It buys you the time and space to actually figure out whether you can deliver the request. Without creating a scene. Without undermining anyone’s authority. Without burning the relationship.
The meeting ends. You go back to your desk. And then you do the real work.
Your Next Move
After the meeting, send a short note to the requester:
“I want to make sure I do this well. Can I get a little more context on the desired outcome and timeline? Based on what I have going on this week, I want to give you a realistic date rather than the fastest one.”
That’s it. No apology. No over-explanation. No performance of helpfulness.
Then exhale.
Remember, to give a real yes the context you are looking for must answer three questions well:
What exactly is being asked? Know the format and depth of detail required for the request.
So what — why does this matter? Be clear on the desired impact or outcome of this work.
What’s next — how will they use it? Understand how your work will be leveraged and what the likely next steps are.
The Thoughtful "No" (or Not Yet)
After answering these questions and realizing the request isn’t realistic or that this isn’t the right thing to be working on right now, you will need to navigate what I call a thoughtful no. Not a hard no. Not a blunt refusal. A considered response that protects the relationship and protects your ability to actually deliver.
There are three situations where this comes up most:
When the timeline is unrealistic. Don’t just absorb it. Propose an alternative. “Based on what I have going on this week, I could have this to you by [date]. Would that work?” If you’re a serial people-pleaser, this will feel awkward the first few times.
But remember, you’re not saying no to the work. You’re saying no to a deadline that was never realistic to begin with. And by offering a specific date instead of just pushing back, you keep the power in their hands.
They can tell you if it truly can’t wait. If they say it can’t, that’s when you get honest about what would have to move: “I can make that work, but I’d need to deprioritize [X]. Can you help me figure out where this lands relative to what I already have on my plate?”
Now it’s a ranking decision, not a yes/no.
When relational pressure is making it hard to think. Someone you like. Someone who trusts you. They’re not trying to overwhelm you. They’re counting on you, and that’s exactly what makes it hard.
The instinct is to protect the relationship by saying yes. But the relationship is better protected by being honest. When you feel that pull, slow it down: “I’d really like to help with this. Can you tell me a little more about what support you actually need?”
That question does two things. It signals that you care. And it creates the space to find out whether the full ask is actually necessary. Sometimes what they need is a fraction of what they asked for.
If after getting context you still can’t deliver, be direct but warm: “I want to be upfront with you… Given what’s on my plate right now, I can’t do this justice by [date]. I’d rather tell you that now than let you down later. Can we talk about timing?”
That’s not a no. That’s the most dependable thing you can say.
When a leader assigns work in a group setting. The room is watching. Your nervous system wants out. Affirm it publicly, “I can help with that,” and then follow up privately after the meeting, once the pressure of the audience is gone: “I want to make sure I do this well. Before I commit to a timeline, can I get a little more context on what you’re looking for and when you actually need it?”
Nine times out of ten, the deadline was a reflex. They’ll give you more room than the meeting implied. If the timeline is still genuinely tight after that conversation, that’s when you bring your list: “Given what I'm currently working on, which of these would you want me to deprioritize to make space for this?”
Let them order the priorities.
The bottom line: a thoughtful “not yet” builds more trust than an unrealistic “yes.”
I’ve turned all three scenarios into a one-page cheat sheet.
[ Download The Thoughtful "No" Cheat Sheet here]
Same format as last week’s Real Yes Framework. Print it. Keep it close. You’ll need it sooner than you think.
Your Unignorable Move
Think about the last time someone asked you for something and yes was out of your mouth before you’d thought it through.
What happened next? Did you deliver exactly what was needed, on time, without stress? Or did you spend the next few days scrambling?
That’s the cost of the reflexive yes.
Here’s the harder question: who told you that saying yes was the same thing as being dependable? Because somewhere along the way, you learned that.
And it’s worth finding out if it’s actually true or if it’s just the story you tell yourself to avoid an uncomfortable conversation.
A thoughtful no is not the opposite of being easy to work with. It might be the clearest proof of it.
What’s one ask you’re carrying right now that deserves a more honest answer?
Your coach,
Chris
P.S. If you’re working on the reflexive yes habit and want someone in your corner, I’d love to connect. That’s what coaching is for.
