Managing Up
Saying no to a request from someone senior
Refusing work is rarely the actual skill required; what matters is making a capacity problem visible in a way that leaves the decision with the person who should be making it.
By Yash Agarwal3 min read

The word no is almost never the right instrument
People who struggle with this usually imagine the conversation as a binary — accept and drown, or refuse and be marked as difficult. Framed that way, most people accept, and the cost lands later as missed deadlines on work that was already committed. The refusal was avoided; the consequence was not.
The more accurate frame is that you are almost never being asked whether the work is possible in the abstract. You are being asked to do it in addition to a set of other commitments that the requester frequently cannot see. What you actually possess is not a veto but information, and the useful move is to supply it.
Make the trade explicit and hand it back
The reliable form of the answer is yes-and-what-moves. I can take that on; it would mean the migration testing slips to the following week, or the monthly pack goes out without the regional breakdown. Which do you prefer? That is not a refusal, and it is very hard to characterise as unhelpful.
The effect is to relocate the decision. Prioritising between two pieces of work when both are wanted is a management responsibility, and handing it to the person with the authority to make it is not passing the buck — it is the correct routing. Senior people who are any good recognise this immediately, and a surprising number will withdraw the request themselves once the cost is visible.
Be specific about the cost, though. Vague statements about being busy carry almost no weight, partly because everybody is busy and partly because they cannot be evaluated. Naming the exact thing that slips, and by roughly how long, is what makes the trade real.
Your manager is normally part of the answer
Where the request comes from somebody outside your reporting line, the sentence that keeps you out of trouble is that you will check on sequencing and come back with a time. It is not evasive, it takes a few minutes, and it prevents the common failure where a junior person quietly reorders their week for a senior stranger and their own manager discovers it a fortnight later.
Managers are generally happy to absorb this. Saying no to a peer is part of their job and costs them far less than it costs you, since they have standing and context you do not. The mistake is to treat asking them as an admission that you could not handle it yourself.
Sometimes the answer is simply yes
It is worth saying plainly that not every request should be negotiated. Short tasks, genuine emergencies, things that are obviously more important than what you were doing, and the occasional favour that buys goodwill — all of these are better absorbed than analysed. Somebody who produces a trade-off analysis for a ten-minute job becomes exhausting to work with, and that reputation is harder to shift than a busy week.
The judgement is about size and frequency. One unplanned request a week is ordinary working life. A pattern where your committed work is routinely displaced by whoever asked most recently is a structural problem, and it should be raised as a pattern rather than fought case by case.
What to do when the answer is not accepted
Occasionally you will lay out the trade honestly and be told to do all of it anyway, with nothing dropped. This happens, and it is not always unreasonable — there are weeks where everything genuinely is required. What matters then is the record. A short note confirming what you agreed to attempt, and what is at risk, is ordinary practice and it protects everyone including the person who asked.
If it happens repeatedly, you are looking at one of two situations. Either the organisation is under a temporary strain that is understood and time-limited, or it has quietly decided that the gap between the work and the people is a problem for individuals to absorb. The second is a real feature of some workplaces, it does not resolve through better communication, and the only reliable responses are to escalate it as a resourcing issue or to leave. If the load is affecting your health, treat that as its own question and speak to a qualified professional rather than waiting for the quarter to end.
Common questions
Will asking about priorities make me look incapable?
It generally has the opposite effect, provided the question is specific. Someone who knows exactly what is on their plate and what each new item would displace reads as organised. Someone who says yes to everything and then misses dates reads as unreliable, which is a worse label and a stickier one.
What if I genuinely cannot do the task at all?
Say so early and say why, in terms of capability rather than willingness, and offer what you can do instead — find who can, prepare the inputs, take a smaller piece. An early honest answer is nearly always cheaper for everyone than a late failed attempt.
Does this work with a manager who does not accept trade-offs?
Less well, and it is worth being realistic about that. What it still does is create a record and force the choice into the open, which sometimes changes behaviour over months. If it never does, the situation is about the manager rather than about your phrasing.
Contributing editor, After the First Job
Yash writes the explanatory pieces on first months, managing up, money at work and would rather show the working than assert the conclusion.





