Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"What should I deprioritize?" I've known a couple supervisors who hate this response, effectively responding in turn "nothing!" (Fortunately I did not work for them myself, just heard them complain about it.)


I worked for a boss who marked nearly every task in Jira as "Blocker" which was the highest priority.

Of course this is ridiculous. When everything has the highest priority, there's no priority between the tasks.

The solution? Use my judgment and ignore the marked priority. The boss was going to be an ass either way.


A useful variation is: "Where does this fit in the order of priorities? Would you put it above <most important pending task> or <most urgent pending task>?". If neither, you have some time to figure it out later, after you complete your ongoing task(s).


Many times, to me it just works to say "yes" and just not do it. Managers ask for so many things, and change priorities so often (cancelling the previous things they asked), that they don't really make a difference.

So if I agree, I say "yes" and I do it. If I disagree, I say "yes" and I don't do it. Usually, when I disagree, that's because it is not as important as they think, and therefore they don't have to come ask a second time: they just forget about it.


For that kind of manager, just employ their other brilliant strategy: a long awkward silence. And make sure to keep eye contact throughout. It will go much better!


> Saying no to a senior leader at work is almost unthinkable, even laughable, for many people. However, when saying yes is going to compromise your ability to make the highest level of contribution to your work, it is also your obligation.

What kind of world do the people who write this stuff live in?


Agreed. Not the world I live in. My default answer to almost every request from anyone for my extremely limited time is no. Maybe this is cultural or something.


Or worse..

the response is: list out your priorities and the impact of not doing them long with a recommendation of moving forward

... isn't that YOUR job? This especially sucks when it happens regularly and it means you're not spending any time on the prioritized work, just working on setting priorities.


I feel for you. A manager should probably be better on-top of those things. But this response means you're probably working with an earnest, but perhaps not fully up to level manager, instead of someone who just doesn't give a shit about how you're getting screwed.


that was my immediate reaction to reading that also. It's easy for the person to say nothing and then what? You haven't got much out of that exchange at all. Now you still have to say no, which was the original problem that you tried to side-step.


Well, this depends. If you were saying no because you honestly believe that you cannot accommodate your manager's (or whatever) request into your current schedule/plan/loading, then you probably want to take the time to get in writing a new plan that exactly articulates what your manager believes your old plan and priorities were, and what your new plan and priorities are. You are now trying to solve a planning and communication problem.

If you were just saying no because you didn't -want- to do it. Well, then your manager is calling your bluff, and ya, you need to find another way to wiggle out of it. Tough luck.


> then what?

Then, at least you know that you are dealing with a jerk.


Absolutely. I've asked this in the past a little differently: "which one do you want me to prioritize first?", only to be left with "both", or "all of them are top priority", effectively wiping their hands clean of the situation, meaning I'd be the one at fault if I couldn't deliver.


"If everything is a priority, then nothing is." I've had some success with that line in response to such supervisors.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: