Managing Up
Asking for something that is not money
Requests for time, scope, training or a change in how you work are decided by a different mechanism from pay, and the difference is mostly about who can say yes.
By Yash Agarwal3 min read
Not everything you want costs salary
Pay conversations get all the attention, and they are also the hardest ones to win, because salary is bounded by structures set well above your manager. A great deal of what people actually want from a job is not salary at all: a different mix of work, a course, a change of hours, permission to spend a day a week on something, or a title that matches what they already do.
These requests behave differently, and the difference is worth understanding before you make one. Some cost real money from a budget somebody owns. Some cost nothing but require a decision. And some cost only your manager’s attention, which is scarcer than either but easier to get.
Work out who can actually say yes
The single most common reason a reasonable request fails is that it was made to somebody without the authority to grant it, who then had to carry it upwards without being invested in the outcome. A manager who cannot approve a thing and does not much care about it will pass it on in a weakened form, and the answer will come back as no with no explanation attached.
So ask, early and without drama, who decides. That question is easy to answer and it is almost never resented. If the answer is that your manager decides, the conversation is short. If it goes to a budget holder two levels up, your task shifts from persuading your manager to giving them something they can carry, which is a different piece of work with a different shape.
Give them the argument they will have to repeat
Whoever takes your request onwards has to restate it to somebody else, usually briefly and from memory, in a meeting about eleven other things. That is the moment your request either survives or does not, and you are not there. What survives is the version that is short and that connects to something the organisation already wants.
A course you would find interesting is a weak version. The same course, described as the thing that stops one particular piece of work depending entirely on a colleague who is stretched, is a version somebody can repeat. Neither framing is dishonest. One of them simply carries the information that the decision actually turns on, and the other requires the listener to supply it themselves.
Timing follows the budget year and the team’s year
Anything with a cost attached is governed by a cycle. Budgets are set at a fixed point, spent unevenly, and often surrendered if unused, which means the same request can be impossible in one month and easy in another. Asking about training just after a budget is set, or just before an underspent one expires, are the two good moments, and they are not secret.
Requests that cost no money have their own timing, which is about attention rather than funds. A month when your team is behind on something visible is a poor moment to propose a change to how you work, however sensible. This is not fairness, it is bandwidth, and treating it as bandwidth stops you reading an ordinary no as a verdict.
Ask for something specific, and say what happens next
Vague requests are easy to agree with and impossible to action, which is why so many end in warm agreement and nothing else. “More responsibility” is a wish. “I would like to run the monthly review from next quarter, with you sitting in for the first two” is a proposal, and it can be accepted, refused or modified.
Include the boring parts yourself. What it costs, what happens to your existing work, and how it could be reversed if it does not work. Handing over an answer to the objections is what separates a request that gets a decision from one that gets deferred, and deferral is the usual fate of anything that requires the person hearing it to do the thinking.
Reading the answer honestly
A refusal comes in two useful shapes. One says the thing is not possible now and explains what would change that, which is a real answer and worth returning to on the schedule it implies. The other says nothing at all, or agrees warmly and then produces no movement across two or three months, and that is also an answer even though it never uses the word.
Some organisations simply do not fund development, will not adjust how anybody works, and treat every request as a complaint. That is not something a better-phrased proposal fixes. If two or three modest, well-timed requests have all dissolved without explanation, the reasonable conclusion is about the place rather than about your technique.
Common questions
Is it worth asking for training when budgets are tight?
Often yes, provided you name the cheapest adequate option rather than the best one. A modest request that solves a stated problem survives a tight budget far better than an expensive one framed as development, since the first has an owner and the second only has a beneficiary.
Should I ask for a title change without a pay rise?
It can be worth it, since titles travel outside the company in a way internal grades do not. Expect it to be treated as a real decision rather than a formality, because in many places titles map to bands, and changing one has consequences the person you ask may not control.
What if my manager keeps saying they will look into it?
Put a date on it yourself, politely — asking whether it makes sense to revisit it at a specific point turns an open loop into a scheduled one. If two of those dates pass without anything happening, treat the absence of an answer as the answer and decide accordingly.
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.
