Prioritizing everything is prioritizing nothing
blog.drgriffin.com.au
blog.drgriffin.com.au
I started to explain that it's about risk management - the things we pick up first have higher chance to be completed on time, so I asked which ones would cause more trouble if they were delayed.
Sometimes that helped, sometimes it didn't. So these days what I say when I can't get clear priorities is this: if everything is equally important, then I'll choose what my team works on first, and I'll do it according to my criteria, which is what tasks do we find most interesting. Almost always the response then is "ok, wait, let me think and by tomorrow I'll send you the list ordered by priority".
There was a project I was on that lacked a PM; I was assigned 3 different tasks by different stakeholders. There was zero way these tasks could all get done by the deadline. I told them that and asked for the engineering manager to sort out priorities, but he lacked the clout to do so. I sent out an e-mail with the items listed in a random order and said "unless someone tells me differently, this is the order I'm doing them in." I got 2/3 done by the deadline, and when I was asked why the 3rd one wasn't done, showed the e-mail chain (which of course nobody replied to). Less than a week later we got a PM and the project was basically sunshine and rainbows after that.
Everything is important and for tomorrow just shows that management/product are not doing their job. I have seen that in one owner companies, it maybe the top that does not allow for the company too work properly, it does not needs to be necessarily any product owner fault.
I totally agree! I think they're often in difficult situation, I've seen product managers with different priorities coming from various stakeholders. It's often a complicated situation.
This is usually how I get enough focus time to do research, planning, and prioritization for future releases.
This is just one perspective, but getting back to your question about “isn’t this still their job?”, the answer is “yes”, but at least in my case, I’m now doing that job for release N+2 if the whole company is currently focusing on mandates for N and N+1.
Your insight is interesting. While I mostly considered it leadership’s failure to provide focus, you could definitely observe the difference between areas of the company that had strong product leaders who could stand up to frivolous executives, and those that just parroted the next initiative without any real ability to prioritize and develop product.
To be fair, some of the mandates make sense. As a product grows and expands into new markets, and let’s just say that new market is a heavily regulated industry, and let’s say those regulations have major implications to the product, it takes a C-level mandate to get all groups on the same page.
While I understand it, it also puts product managers like myself in a difficult position. For now, I use it to structure my work between releases. But eventually it’s gonna raise my frustration at not meeting my existing customer’s needs to a level that I’ll need to work elsewhere.
Instead, I'll firmly agree with everything the author said about prioritization. I think he gave great examples and he is right. When you have 16 different "priorities" and "objectives" that are shared by each employee, you actually have zero priorities. I've seen leaders list many objectives, then say "these go to manager 1, these others go to manager 2, etc".
Very easy to fall into the trap of "doing more" though.
Prod is down becomes a sanctuary, compared to the politics and stalemates.
You can call it "50 shades of red" too, where it starts with green/yellow/red color coding then everything becomes red and you have to differentiate between reds. So in the end you have to choose between "deep red" and "crimson red of the darkest night". It was a joke in France during the pandemic where the entire map was colored red, with the shade of red indicating the level of restriction.
But even then, say you had 14 LPs each in tension with another LP. That's a 7-dimensional tension equation to figure out. Say you had 6 LPs in 3 pairs in tension with each other, that seems way more manageable.