The message arrives at 4:40pm. Someone needs a deck by Monday morning, and it will take most of your weekend. You type “Yes, no problem — I’ll get it over to you.” You send it. And then you sit there doing the arithmetic: the two things that now slip, the evening you had planned, the fact that this is the third time this month.
Why does “just be more assertive” never work?
Because assertiveness was never the missing ingredient. The advice assumes you don’t know how to form the word “no”, when in fact you know exactly how, and you also know what happens next.
Refusing work at work carries real costs, and it is worth naming them honestly rather than waving them off as anxiety:
- Reputation. Availability gets read as commitment. The person who always absorbs the extra thing is described as reliable, and reliability is currency at review time — unfairly, but reliably.
- Relationships. The colleague you refuse is often someone you need next month. Workplaces run on accumulated goodwill, and goodwill is not evenly replaceable.
- Position. If your contract is short, your visa is tied to the job, or your manager keeps score, a refusal is not a neutral act. It goes on a mental ledger you cannot see.
Advice that pretends these risks are imaginary does not survive contact with an actual Tuesday. So here is the honest version of the goal. It is not to say no more often. It is to stop producing an automatic yes you will resent, and to make each no cost you as little as possible. Most of the time, that turns out not to require refusing at all.
What is the one technique that does most of the work?
Make the trade-off visible and hand the decision back.
Almost every unreasonable request is unreasonable because the person asking cannot see your queue. They are not being cruel; they are being uninformed, and you are the only one holding the information. When you say a flat yes, you keep that information to yourself and quietly eat the cost. When you say a flat no, you look like an obstacle. When you show the trade-off, you do neither — you turn a refusal into a question and move the choice to the person who actually owns the priorities.
“I can do that. It would mean the client report slips to Friday. Which would you rather have first?”
What it does is transfer the decision. If your manager says “do the new thing, let the report slip”, you now have a documented reprioritisation rather than a private failure. If they say “no, the report matters more”, you have just been protected from a request that was never worth its cost. Either way you stop being the person who silently absorbs the difference.
The shape adapts to most situations:
When you need a decision: “Happy to pick this up. Right now I’ve got the migration and the vendor review in flight — which of those should I pause?”
When the deadline is the problem, not the task: “I can do this properly by Thursday, or I can get you something rough by tomorrow lunchtime. Which is more useful?”
When you want to shrink the request rather than refuse it: “The full version is about three days. There’s a cut-down version — just the top-line numbers, no commentary — I could do this afternoon. Would that cover it?”
When you have capacity later but not now: “Not this week — I’d be doing it badly. From Monday I’ve got proper time for it. Does Monday work, or does it need someone else?”
Why is saying no upwards different from saying no sideways?
Most articles treat “saying no” as a single skill. It isn’t. The direction of the request changes the power in the room, and therefore changes the words.
To your own manager
This is the easiest one, and people find it the hardest. Your manager is usually the one person with both the authority and the incentive to reprioritise — they are on the hook for your output, so a task you drop badly is their problem too. Almost never refuse. Almost always reprioritise.
“Yes — where does this sit against the onboarding work? I can’t do both by Thursday.”
To a peer
Here nobody can compel anybody, which sounds easier and is often harder, because the currency is goodwill and you spend it directly. With peers, be warm and be specific about what you can do.
“I can’t take the whole thing this week. I can look over your draft on Wednesday and flag anything broken — would that help?”
To another department
Cross-team requests are where invisible work accumulates, because nobody in the other team sees your workload and nobody in your team sees their request. Route it, don’t refuse it.
“This one needs to come through Dan — he’s holding our priorities for the quarter. If he greenlights it I’ll pick it up.”
To someone senior in another team
The hardest case: real status, no formal authority over you, and a request you cannot afford to look unhelpful about. Do not refuse. Make it visible and let your own chain arbitrate.
“Yes, I’d like to help with this. I’m fully committed to the launch until the 20th, so let me check with Sam whether we can move something — I’ll come back to you today either way.”
To someone who reports to you
Different problem entirely: you have the power, so your no lands harder than you intend, and the risk is discouraging someone from bringing you things. Say no to the request, explicitly not to the person, and say why.
“Not this quarter, and it’s not the idea — it’s that we’ve already got two things half-finished. Bring it back in the planning session in January and I’ll back it.”
What if you need time before you answer?
Most bad yeses happen inside ten seconds. The single highest-value habit in this whole article is buying those seconds back:
“Let me check what’s on and come back to you this afternoon.”
That sentence is available to almost everyone, at almost every level, including a first week and a precarious contract. It is not a refusal, so it triggers none of the risks above. It is diligent — you are checking before committing, which is what a careful person does. And it converts a reflex into a decision.
What are the actual sentences to use?
Below are scripts for the situations that come up most. Take them and change the names. They work because they are short, they concede something real, and none of them contain an apology for having a workload.
An unreasonable deadline
“Thursday isn’t realistic for the full thing — it’s about a week of work. Two options: I can get you the section you need for the board by Thursday and the rest the following week, or we pull someone else in. What’s your preference?”
A task that is not yours
“That one sits with the ops team — Maya owns it. I’d send it straight to her, otherwise it’ll bounce back through me and lose a day.”
“I’ve picked this up a few times as a favour, but it isn’t in my patch and I’m not the right person to keep doing it. Can we get it assigned properly so it doesn’t depend on me being free?”
A meeting with no clear purpose
“What do you need from me in this one? If it’s just the numbers, I’ll send them over beforehand and skip it — shout if you’d rather I was there.”
“I’ll drop off after the first item if that’s alright — the rest isn’t my area, and I’ve got the deadline on Friday.”
Work that lands at 5pm on Friday
“I’m finishing up for the week — I’ll pick this up first thing Monday. If it genuinely can’t wait until then, let me know and I’ll see what I can do tonight.”
That second sentence is doing deliberate work. It is not weakness. Most Friday-evening requests are not truly urgent, and being asked to confirm the urgency out loud is enough to make about half of them wait. For the half that really can’t, you have kept the door open, so you don’t look like someone who checks out.
A favour from a colleague you like
“I want to help but I’d be doing it at 11pm and doing it badly. Is there a smaller piece — an hour, say — that would actually move it forward?”
“Not this one, I’m sorry — I’m underwater. Ask me again in two weeks, I mean that.”
Only say the second half if it’s true. A specific, honest no is better for a friendship than a resentful yes, and both of you will feel the resentful yes eventually.
A request from someone senior you cannot simply refuse
“Of course. To do it properly I’d need to park the Q3 forecast for a few days — is that the right call, or should I find another route?”
You have not refused anything. You have made the cost visible and put the risk on record before it materialises, which is what protects you if it does.
Being volunteered in a meeting with no warning
The one that catches everyone, because there are eight people watching and refusing in public feels enormous. Don’t refuse in public. Don’t accept in public either.
“Happy to look at it — let me check it against the launch work and confirm after this.”
“I can take it if we move the reporting deadline. Can we sort that out after the call?”
Both of these read as cooperative in the room, and both leave the decision genuinely open. Then you follow up within the hour, in writing, with the trade-off. Nine times out of ten the enthusiasm has cooled by then anyway.
Why does explaining yourself make it worse?
The instinct when refusing is to justify — to lay out the whole week, the three deadlines, the doctor’s appointment — because a long explanation feels like it earns the right to say no.
It does the opposite. Every reason you offer is a surface someone can push against. Mention the Thursday deadline and you’ll be told Thursday can move. Mention the appointment and you’ll be asked what time. You end up defending a case rather than communicating a decision, and the more you say, the more it sounds like you’re building an argument you don’t quite believe.
One reason is plenty. Sometimes none.
“I can’t take this on this week.” (Then stop. Let the silence sit.)
How do you stop a one-off becoming permanent?
The requests that do the real damage rarely arrive as a big ask. They arrive as “could you just do it this once”, you do it, and then it is yours forever, unassigned and unrecorded, because you did it before and it worked out fine.
The fix is to name the boundary at the moment you agree, not six months later when you are trying to give it back. It costs one clause:
“I’ll cover it this month. It shouldn’t sit with me long-term though — can we work out where it lands properly before next cycle?”
“I’ll do this one because it’s urgent. Going forward, can these come through the normal request queue? Otherwise I’ve got no way to plan around them.”
None of that is confrontational. You’re saying yes. You’re just refusing to let a favour silently convert into a job description. Say it in writing where you reasonably can — a message thread remembers what a corridor conversation doesn’t, and in six months you will want the record.
What if you genuinely cannot say no?
Some people can use everything above tomorrow. Some people cannot use any of it, and it is dishonest to write an article that pretends otherwise.
If you are three months into your first job, on a contract that renews at someone’s discretion, on a visa tied to the employer, supporting people on one income, or working for a manager who treats any pushback as disloyalty — the risk calculation is different, and it is different for good reasons. In those situations, the advice has to bend. Refusing may genuinely be the wrong move, and choosing not to refuse is not a failure of nerve. It is a correct reading of your position.
What remains available is narrower, quieter, and still worth doing:
- Make the workload visible in writing. Not as a complaint — as an update. “Here’s what I’m holding this week, in order” sent to your manager on a Monday is a normal professional act. It creates a shared picture without requiring you to object to anything.
- Ask for prioritisation instead of refusing. “Which of these should I do first?” is a question almost nobody can punish you for. It is the visible-trade-off technique with all of the edges filed off, and it produces most of the same protection.
- Keep a record. Dates, requests, what you delivered, what you flagged. Not as ammunition — as memory. It matters at review time, it matters if things go wrong, and it matters if you later need to demonstrate what you were actually carrying.
- Treat it as information about the job. If nothing can be declined, prioritised, or renegotiated, that is a fact about the workplace, not about you. Store it. It is relevant to decisions you will make later.
Anyone who tells you that you simply haven’t tried hard enough to push back has not been in your position.
What about the work nobody notices?
There is a category of task — taking the notes, organising the leaving card, booking the room, chasing people for their sections, onboarding the new starter, tidying the shared drive — that is genuinely necessary, takes real hours, and appears nowhere in any performance review.
This work is not distributed evenly. It falls disproportionately on women, on junior staff, and on whoever in the room is most obliging, and it accumulates: the person who took the notes once becomes the person who takes the notes, and the hours come out of the work that does get evaluated.
Worth saying plainly, because people who end up carrying it often experience it as a personal failing — as being bad at saying no. It is a pattern, not a character flaw. Two practical things follow. First, notice when you are being asked because you are the reliable one rather than the right one; that is the moment to use the precedent language above. Second, where these tasks are genuinely necessary, rotation is a reasonable thing to propose out loud:
“I’ve done the notes for the last few. Can we rotate it? Otherwise it just becomes my job.”
One more thing to protect while you are at it: your uninterrupted time. Every “quick question” costs more than the question, because the cost of an interruption is mostly the reassembly afterwards — which is why focus is worth defending as deliberately as your calendar.
Can you go back after you have already said yes?
Far more often than people believe. The assumption is that yes is a sealed contract and reopening it is worse than the original mistake. In practice, most people would strongly prefer to hear on Tuesday that something is at risk than to discover it on Friday when it was due.
“I said yes to this on Monday and I’ve now looked at it properly — it’s bigger than I thought. It’s about four days, not one. Do you want me to keep going and push the other work, or should we hand it to someone with more room?”
Say it once, cleanly, without an extended apology. Renegotiating a commitment three days in is normal professional behaviour. Missing it silently three weeks later is the thing that actually damages you.
What if the answer is that the workload is simply impossible?
Sometimes none of this applies, because there is no arrangement of your week in which the work fits. Two people left and were not replaced. The plan assumes forty-five hours and the work is sixty. No amount of skilful reprioritising resolves a structural gap — it just changes which thing fails.
The first move is still to make it explicit and in writing: this is what I’m holding, this is what will not get done, tell me which. If that produces a real decision, you had a workload problem and it is now shared. If it produces “manage it” for the third time, you have learned that the impossibility is deliberate — and at that point the question shifts from how to say no in this job to whether the job is worth what it costs. That is not a failure of technique, and knowing how to handle leaving well is part of the same skill set.
How do you decide what to say yes to?
The point of all this was never to do less. Someone who has become skilled at declining and put nothing in the space they cleared has traded one problem for a duller one.
The useful question is not “can I get out of this?” but “is this the thing I want to be known for?” Some work is genuinely worth the weekend — the project that puts you in front of people who make decisions, the awkward problem nobody else will touch, the thing that is visibly hard and visibly yours. Say yes to those loudly and on purpose. Saying no to the rest is only worth doing because it protects your ability to say yes to these, which is also most of what actually drives how to get promoted in any organisation that isn’t purely time-served.
Is it different when you are new?
Yes, and it is worth being clear about it. In your first weeks you have no track record, so people cannot yet tell the difference between “has good judgement about capacity” and “doesn’t want to do things”. You also don’t yet know which requests are load-bearing and which are noise.
So in the early period, lean towards yes, use the delayed yes rather than the refusal, and ask about priority rather than declining outright — “I’ve got these three, which order?” works from day one and costs you nothing. Once you have delivered a few things well, your no starts being read as judgement instead of reluctance. That shift is a real part of the first ninety days, and it is worth waiting for rather than forcing.
If declining something has already gone badly, the repair is its own skill — and an apology with an excuse attached is not one.
Acas covers what you can formally ask for when the problem is the shape of the job rather than any single request.
The American Psychological Association has material on healthy workplaces and what makes workloads sustainable rather than merely survivable.
Common questions
What if my manager just says “do both”?
Confirm it in writing and name the consequence without drama: “Understood — doing both. Flagging that the report will be a first draft rather than final.” You have complied, and you have put the outcome on record before it happens. If this is the answer every time, the constraint is your manager rather than your phrasing, and no script fixes that.
Will I get a reputation as difficult?
Not from the trade-off framing, because you never refused anything — you asked for a decision. Reputations for difficulty come from flat refusals with no alternative, from complaining about workload without proposing anything, and from inconsistency. Someone who reliably delivers what they agreed to and is clear about what they can’t take on is generally described as organised.
How do I say no to a request from my manager’s manager?
You mostly don’t — you route it. “Yes, glad to. Let me check with Sam how it fits against the current priorities and I’ll come back to you today.” Senior people generally do not want you to quietly drop something important to serve them; they want the conflict surfaced. Going around your own manager is the thing that causes damage, not the delay.
Should I say no by message or in person?
In person or on a call when the relationship matters and the no might sting — tone carries, and you can hear the response. In writing when the record matters: anything about deadlines, scope, precedent, or reprioritisation. A useful combination is to have the conversation live and then send a short summary afterwards, so you get both the warmth and the paper trail.
What if I say no and they do it themselves, badly, and it becomes a problem?
That is their decision and its consequence, provided you flagged the risk clearly at the time. This is exactly why the trade-off framing is worth the effort — “I can’t take this on this week, and it’ll need someone with access to the billing system” leaves a record of a warning given. Absorbing work permanently to prevent other people from making their own mistakes is not a sustainable arrangement, and it usually ends with you owning something nobody remembers giving you.