Managing Up
Being handed work that does not fit in the time available
The moment you are given something you cannot finish is a decision point, and the way most people handle it guarantees the worst of the possible outcomes.
By Tara Mukherjee4 min read

Where the failure actually happens
The situation is familiar. You are given a piece of work with a date attached, you do a rough calculation, and you can see that it doesn’t fit alongside what you already have. What almost everyone does next is accept it, hope to find the time, and say nothing until the deadline is close enough to be a problem. The intention is good. The result is that your manager loses the only thing they could have done something with, which is early warning.
It helps to see this from their side. A manager with a fixed set of commitments and not enough people is running an allocation problem. They can move a deadline, remove something else from your list, add a person, reduce the scope, or accept a lower standard. Every one of those options exists at the moment the work is assigned. By the time the deadline is a week away, most of them have expired, and the only remaining option is the bad one.
Why saying nothing feels safer than it is
The silence is not laziness; it is a reasonable-seeming fear. Saying you can’t fit something in feels like an admission that you are slower than expected, and early in a career there is no internal benchmark to reassure you that the estimate is fair rather than a personal shortfall. So people gamble on the optimistic case, work extra hours, and often get away with it, which teaches exactly the wrong lesson.
The tell that this is a bad strategy is what happens on the occasion it fails. A missed deadline that was flagged three weeks early is an adjustment. A missed deadline that arrives as a surprise is an incident, because it has now propagated to everyone downstream who planned around your date. The asymmetry between those two outcomes is much larger than the small embarrassment of raising the question at the start.
Bring the trade, not the refusal
The conversation that works isn’t no. It is a specific statement of what is already committed, an estimate for the new work, and a question about priority. Something close to: I have these three things, this new piece looks like it takes about this long, which of the existing ones should move? That hands the decision to the person whose job it is to make it, which is the whole point.
Two details matter. Do the arithmetic before you speak, because a vague sense of being busy is easy to dismiss and a list is not. And be genuinely willing to hear that the new thing wins and something you care about gets dropped. If you present a trade and then resist every version of it, you were not offering a trade, and that is noticed.
It also helps to separate the date from the scope, since these are often confused. A great deal of work has a version that fits the time and a version that does not, and asking which one is wanted is usually more productive than negotiating the deadline. Managers frequently have less attachment to completeness than people assume, particularly when the alternative is being late.
Estimating badly is normal, and there is a fix
Objecting that you cannot estimate is fair, especially in the first year, when you have no basis for comparison and everything is unfamiliar. The workable substitute is a timeboxed investigation: agree to spend a fixed short period finding out what the work involves, and come back with a shape rather than a number. Almost nobody refuses that, and it converts an impossible question into a small deliverable.
Over a couple of years, keep rough records of what you thought things would take and what they did take. That habit is unglamorous and it produces the single most useful professional asset available early on, which is an estimate people can rely on. Being right about how long things take is quietly worth more than being fast.
When the answer is that everything is priority one
Sometimes you present the trade and are told that all of it must be done. That happens for two very different reasons. The manager may be under a commitment they cannot move and is genuinely stuck, in which case the honest response is to agree what will be sacrificed in practice, since something will be, and to make sure it is chosen rather than discovered.
Or the organisation may be chronically overcommitted and simply passing the shortfall down to whoever will absorb it. This is a common pattern and it is worth recognising, because it does not resolve. Individuals who quietly absorb it are rewarded in the short term and become the load-bearing element in a structure that nobody has to fix. If repeated attempts to have priorities set produce nothing but encouragement, take that as information about the organisation rather than about your own capacity.
Common questions
How early should I flag that something will be late?
As soon as your honest estimate crosses the date, not when the date arrives. The value of the warning decays quickly, because the options available to fix it disappear one by one as the deadline approaches.
Does pushing back make me look uncommitted?
It depends entirely on how it is framed. Refusing looks uncommitted; presenting a list of current commitments and asking which one moves looks organised. The second version puts the work first and the decision where it belongs, which is hard to read as reluctance.
What if my manager never sets priorities?
Set them provisionally yourself and send the list, stating what you intend to do first and what you intend to let slip. Silence in response is a form of agreement and gives you something to point at. It also frequently prompts a correction, because seeing a wrong order written down is easier than generating the right one from scratch.
Senior writer, After the First Job
Tara writes the explanatory pieces on first months, managing up, money at work and reads the small print so you do not have to.





