Saying no
Updated 24 September 2026
She has not asked yet. You know it is coming, because the compliance workstream needs an owner and the last three times something needed an owner it was you. You have run the meeting in your head for days: the moment she asks, the sentence you will say, and the pause after it, which is the part you cannot get right. Either you hear yourself saying yes, or you hear yourself saying no and then adding "but if it's really urgent" before she has finished nodding.
This page is about that conversation: the one where you say no to your boss and it stays said. Not how to hint at it. How to say it, out loud, to her.
The hard part is not saying no. Most people can get the word out. The hard part is the two seconds after it, when she pauses, and you fill the pause by taking it back.
Two versions of this conversation are in the FirstSpar library, and they fail in different ways.
In one, Helen, your director, asks you to take one more project. You are carrying two, one is late, and you have said yes to the last three things she asked for. The trap is her silence. She does not argue. She waits, and you hear yourself soften: "unless there's really nobody else", "I could probably look at it next month". Now you have not said no. You have said negotiate.
In the other, Elena, your manager, has been handing you other people's work for a month because you're the reliable one. The trap is the praise. When she says she knew you would get it done, agreeing with her feels like being a team player. It is how you end up carrying a fourth thing.
Both traps close from the same direction. They make you want to be the person she thinks you are.
Settle three things.
Whether it is really too much. Overwhelmed and overloaded are not the same. Write down everything you are carrying, with its date, and look at it cold. If it fits, this is a different conversation. If it does not, you now hold the list that answers the question you are afraid of.
The facts. Not "I'm swamped". The two projects, the one that is late and why, the three assignments in the last month that started as someone else's, and what has slipped on your own list while you did them. The vague version sounds like complaining. The exact version sounds like someone who runs their own workload.
What you need to leave with. With Helen, it is one clear no that survives the pause. With Elena, it is a real prioritisation decision: which thing comes off, or which date moves. Not sympathy, and not "we'll see".
You do not defend your work ethic. The list does that. The person who says "I can't take this on, and here is what I'm doing instead" is not the one who looks lazy. The one who says yes and misses the date is.
Lead with the no, then the reason. Not the other way round. A long explanation before the answer sounds like asking permission for it.
Helen, I can't take the compliance workstream. I'm carrying two projects, one of them is already late, and adding a third means all three slip.
One sentence for the decision, one for the reason. Then stop, because the next thing that happens is she pauses, and the pause is where this conversation is actually decided.
Knowing the opening line is the easy part. You can type it into a chat window and get a tidier version back. What you cannot get back is what you say in the ninety seconds after she answers, when she is quiet, or generous, or busy, and that is the part worth rehearsing out loud.
Helen says nothing. It lasts three seconds and feels like thirty. Everything in you wants to fill it, and what you fill it with will be a smaller no: "unless it's just a few hours", "I could pick it up once the delivery is out". Do not. Let the pause be hers. If she wants to push back she will, and you will answer that. If she is only thinking, you have handed her a retreat she never asked for.
This is the pushback that sounds like a fact, and it is one. Everyone is busy, and it probably is a priority. Neither changes what you said. Acknowledge it plainly: yes, the team is stretched, and yes, it matters. Then return to your list. If it is a priority, it needs an owner with the capacity for it, and that is a decision about her team, not about your evenings.
This is Elena's move, and it is the hardest one to hold, because it is true and it is kind. The mistake is to agree with it: "I know, and I'm happy to help." Agree with the compliment and you have agreed with the conclusion. Instead, name what it has cost. Reliable has meant three assignments in a month that were someone else's, and your own priorities slipping while you did them. Then ask for the thing you came for: which of these comes off.
Good. The conversation has turned into the one you wanted. Do not answer for her, and do not say "all of it is important". Put the list on the table and ask her to choose. If she says she cannot, say that then you cannot either, and the date on whichever she does not pick moves. That is not a threat. It is arithmetic.
Say no once, and then do not say it again with a smaller word. Every restatement, every "but if you're stuck", is a version of yes. The debrief in FirstSpar calls this holding your ground under pushback, and here the pushback is not anger. It is a pause, a compliment, and a reminder that everyone is busy. Each one is an opening to walk it back. Hold the sentence you came in with, and let the silence be uncomfortable for both of you.
Clarity. The no arrived in the first sentence, not after a paragraph about how much you love the team. Helen could repeat back what you said and what you are asking her to decide.
Holding the line. The pause did not shrink it. The compliment did not turn it into a yes. When Elena said she knew you would get it done, you said what that had cost, and you did not apologise for saying it.
Specificity. You brought the two projects, the one that is late, and the three assignments from the last month. You were not "overwhelmed". You were carrying named things with named dates, and you asked for a named decision about them.
You will replay it. Most people do: the sentence you softened, the compliment you should have let pass. Write down, the same day, what you said and what she decided, because the decision is the thing that matters, and a week from now it will have become "I think she said she'd look at it".
If she did not decide, that is your answer too. Go back in a week with the same list and the same sentence. The second time is shorter.
You face Helen, your director.
Your director is about to ask you to take the compliance workstream. You are already carrying two projects and one of them is late. You have said yes to the last three things she asked for.
Objective: Say no once, clearly, and not walk it back when she pauses.
Written at Pressure Test · Managing up · Priorities · Holding your ground
You face Elena, your manager.
You have become the person your manager, Elena, gives extra work to whenever something is urgent. Over the last month you have taken on three assignments that originally belonged to other people, because Elena said she knew you would get them done. You are proud she trusts you, but your own priorities are slipping and you are starting to resent that reliability earns you more work rather than more support.
Objective: Tell Elena the workload is not sustainable and force a real prioritisation decision, without it sounding like you will not help the team.
Written at Pressure Test · Managing up · Priorities · Holding your ground
Three spars a week on your own conversation, no account needed. The written scenarios and the harder pushback are Pro.
FirstSpar