Your boss just dropped something new on your plate. It does not matter if you are a frontline associate, a team lead, or a vice president. Somewhere up your reporting chain, this is a real priority, tied to something or someone you may not even be aware of. Meanwhile, you are looking at the ten other urgent, ASAP projects already on your list and wondering how this one is supposed to fit. You are not wondering whether to do it. You are wondering what to do with everything else.
This post is about the part of that moment most people get wrong. The fix is not what you say back. The fix is what you understand before you say anything.
Most Pushback Fails for the Same Reason
If you have ever pushed back on a request and watched it go sideways, the reason is almost never your words. People assume it is. They go home and replay the conversation, looking for the sentence that broke it. The sentence is rarely the problem.
The problem is that you walked into the conversation talking about your own pressure when you should have been thinking about your boss's. When you lead with "I have too much going on," even when it is true, your boss hears it as a complaint. When you lead with "help me understand where this fits with the other things you have asked me for," your boss hears something different. They hear a partner. The content of the request is the same. The frame is completely different.
This is what managing up actually is, and most of what gets written about it misses the point. Managing up is not flattery. It is not gaming the relationship. It is the simple practice of understanding what your boss is dealing with before you walk into a conversation about your workload. Once you do that, the right words tend to show up on their own.
I have written about a version of this in another setting, in my post on the 25 strategies for getting promoted after being passed over, where one of the strategies is to consider your boss's perspective. That post is about a different career moment, but the underlying skill is the same. The people who get promoted, get heard, and get trusted are the people who think about the conversation from both sides of the desk before they sit down.
What follows is the version of that skill you need for the workload conversation. Three things your boss is dealing with that you probably are not thinking about, and how to use each one to make your next priority conversation land.
Thing One: What Your Boss Is Being Measured On Right Now
Every boss has a small list of things they are being measured on this quarter. It is rarely the same list as the work they hand you. They give you tasks because tasks need to get done, but their own performance review is tied to a smaller, sharper set of outcomes. If you do not know what those outcomes are, you cannot tell the difference between a request that matters to them and a request they are passing along because someone else asked.
Here is the move. Find out, on purpose, what your boss is being measured on. You do not need to ask in a heavy way. You can ask in a regular one-on-one, in a planning conversation, or in passing. Something as simple as "what are the two or three things you most need to see done this quarter?" works in any industry, at any level. Most bosses are happy to answer because most bosses think about this constantly and almost no one asks them.
Once you know, the priority conversation gets simpler. When something new lands on your plate, you can ask yourself first whether it ties to one of those two or three things. If it does, you treat it as a real priority. If it does not, you have a useful question to bring back to your boss. Not "is this important," which sounds like you are pushing back, but "help me see how this connects to the bigger goals we talked about." That question tells your boss you are paying attention to the strategy, not just the task list. That changes how every conversation lands from there forward.
Thing Two: The Pressure They Cannot Openly Admit To
Your boss has a boss. So does their boss. Every level of the org chart has someone above it putting pressure on the level below. The thing your boss just dropped on your plate may have nothing to do with what they actually want. It may be something they were told to make happen, by someone they cannot say no to, on a timeline they did not get to set.
They will rarely tell you this. They cannot. Admitting it out loud would feel like complaining about their own boss, which most leaders are trained not to do. So they pass the pressure down the chain, often without context, and you receive it as if it came from them alone.
You do not need to ask whether this is happening. You just need to know that it sometimes is. When you assume it might be in play, the conversation changes. Instead of "why are you asking me to do this," your question becomes "is this coming from your priorities or from somewhere else, so I can make sure I handle it the right way?" That question gives your boss a graceful way to tell you the truth without violating any of their own loyalties. It also signals that you are someone who can handle the real answer, which is exactly the kind of employee bosses promote and protect.
Here is the part people miss. When you name this dynamic without making your boss defend it, you become one of the few people they can be honest with. That is rare. It is also where real trust gets built. Not by being agreeable, and not by being clever, but by being a person who understands that they are operating under pressure too.
Thing Three: What Pushback Sounds Like to the Person Receiving It
This is the one most people never think through. They picture pushback from their own side, as the brave act of saying what needs to be said. They never picture how it lands.
Most pushback sounds like one of three things to the person hearing it. It sounds like complaining ("I have so much going on"). It sounds like resistance ("I do not think we should do this"). Or it sounds like a request for permission to do less ("can I drop something to make room?"). All three put the boss in a defensive position, and once they are defensive, the conversation stops being about the work and starts being about the relationship.
There is a fourth kind of pushback that almost never triggers defensiveness. It sounds like commitment. "I want to make sure I do this well, so help me think through what comes off the list to make room for it." The difference is the verb. You are not asking to do less. You are asking for the help you need to do this right.
That single shift, from asking permission to drop work to asking for help making the new work succeed, changes everything about how it lands. Your boss is no longer adjudicating your workload. They are partnering on a real problem. They are also being asked to do exactly what they are paid to do, which is set priorities. Most bosses will rise to that ask. The ones who do not are giving you important information about who they are, which you can use later.
The Frame Underneath All Three
Notice what these three things have in common. They are all about understanding what your boss is experiencing, not about polishing your script. The reason this works is that pushback is a relational act, not a verbal one. The words are downstream of the relationship. When the relationship is built on the assumption that your boss is also under pressure, doing their best with what they know, the conversation almost takes care of itself. When the relationship is built on the assumption that your boss is the problem, no script in the world will fix it.
This is also true, by the way, of how your team experiences you. Read that sentence again, because it matters. Every reader of this post is somebody's employee. Most are also somebody's boss. The same dynamic you are learning to navigate up the chain is the one your team is navigating with you. The clarity you wish your boss would offer is the clarity your team is hoping for from you. The conversation you want to have with your manager is the conversation your direct reports want to have with you.
That is the quiet upside of getting this right. You do not just become better at being managed. You become a better manager, because you understand what good looks like from both sides.
What to Actually Do This Week
Three small moves, ordered easiest to hardest. None of them require a big sit-down with your boss.
Find out what your boss is being measured on. Next time you have any kind of meeting with them, ask the question. "What are the two or three outcomes you most need to see this quarter?" That is it. Listen to the answer. Write it down somewhere you will see it next week.
Assume there is pressure you cannot see. Just for the next two weeks, when a new task lands on your plate, ask yourself privately: what might be driving this that I do not know about? You do not need to confirm anything. You just need to stop assuming the request came out of nowhere.
Replace one piece of pushback with a partnering question. The next time you are about to say "I have too much going on" or "can I drop something," try instead: "help me think through what comes off the list so I can do this well." See what happens. The first time will feel awkward. The third time will feel like the way you talk.
That is all of it. You do not need a script. You need a frame.
Where to Go From Here
This post is one piece of a bigger pattern. Once you have figured out how to read your boss, the next two questions become urgent.
First, what do you actually do with everything on your plate? Sorting your work, deciding what to keep, and deciding what to hand off is a separate skill, and it is the one that comes right before this conversation. If you have not sorted your work yet, the post on prioritizing tasks at work when everything feels urgent is where to start.
Second, what about the team that reports to you? You are someone's employee, but you are also someone's boss, and the same clarity you are asking for from your manager is what your team is asking for from you. The Art of Delegation teaches the version of this skill that points downward. How to choose what to delegate, who to delegate it to, and how to communicate the handoff so your team is never wondering what you actually meant. And Getting Results with Positive Accountability teaches the follow-up skill. How to hold your team to what you agreed on without slipping into the kind of micromanagement that makes good people quit.
Both courses are inside the Leadership Pipeline Builder, a subscription built for working leaders who need real tools rather than theory.
The Conversation You Are Going to Have Anyway
Your boss is going to add to your plate again this week. You can have the same reactive, frustrated conversation you have had before. Or you can have a different one, built on the understanding that they are working under pressure too, that their request is connected to something bigger than the task itself, and that the best way to push back is to ask for help, not permission.
That different conversation is the one that earns trust. And trust, over time, is what gets you out of the everything-is-urgent loop in the first place.
