How do you force a fucking client to not prioritize all fucking tasks with highest priority?!

"When everything is important, nothing really is."

If you can find some examples, show them to him directly. When he'll see that, "fixing a typo" is as equally important (according to the tag) than "fixing potential SQL injection", he might realise the issue.

These kind of tickets land on the bottom of the stack. Also 1 day delay per extra exclamation mark included for free!

This does depend on your client and your work.

If the client has business running of your work, then you can simple give an example:

If your task is preventing you from making money or causing a bug that might lose your customers - then it's a priority.

If your task involve changing a label from "Red" to "Redder Red" - this is not a priority. Another example: Task requires a new functionality to be added - is not a priority over those who prevent you from making money.

If it's just a website he owns, that helps him but isn't his income source, you can try:

If something that you always use is broken - it's a priority.

If it's a feature you think would be nice to have - it's not a priority (or same example with labels).

I'd say it's pretty simple and most do get after real-life examples, especially if we are talking about clients income/profit :)

@Fenix we had internal clients who had prioritized that way. we asked then with whatever we should start and asked them for an order. that way we received an ordered list instead of prioritized list and we knew then what is really important 😉

I am currently in this really "opposite world" where the client doesn't seem to care. Doesn't bother coming to planning meetings, doesn't do the things they are asked to do when they do show up. They're still paying the bills. Wat??

@2erXre5 actually this is quite a good and simple idea, I will try this next time. Thanks!