I often work with the same PM on large application tasks. I am the main point of contact for all things technical. The PM is a bit of a disaster in that this person cannot keep anything straight, we don't have any sort of documented timelines, we get no actions after meetings and so on. Our projects are just several fragmented email chains.
This was not meant as a rant, just background. It is what it is and we are used to it. The common problem that everyone on my team is that this PM will assign their own path to do things. And they may require us to do something on the the technical side that has no use or purpose for the next 6 months but assigns it to be done in two weeks.
I am using an exaggerated example (but real) but most examples are pretty far off. So this PM emails us and says is XYZ done?
We email back and say no. We are not going to meet that date because of this. Does that hinder any other timelines or the project in any way? If it does we can help with an alternative to make sure that everyone is on task.
No answer. Couple days later. Can I have an update on XYZ?
No update. Again does this hinder the project in any way? Can you please let us know why this needs to be done right now?
No answer. Couple days later. Can I have an update on XYZ?
This goes on until one of my team members blows up (rightly) at the PM or the task is complete.
90% of the time these things can't be done in the time frame the PM allots because of vendor issues. The other 10% I am just making a choice that my team meets real deadlines and gets things done in the proper order rather than the fake important things induced by the PM team
So what can be done to stop this sort of communication back and forth? Really we just need to force the PM to tell us why something has to be done. What are some strategies when dealing with this?
(When I do have an employee blow up at the PM. The answer is always the same. The task has no need to be done anytime soon. It is just a nice to have. The task is always pushed to a realistic part of the project. In essence the PM doesn't want to tell their boss that they are changing timelines because they have no clue about the project or task and still don't. I don't like these after blow-up calls because the PM's management focuses on our group's professionalism over their PM costing of hundreds of hours of time. You know things that would never happen at a mid/small shop. Obviously I am in huge corporate America.)
Some sidenotes: The PM's boss doesn't care or even invested time to understand. Also getting on phone calls and hashing it out like you would do normally makes things worse. As the PM misconstrues everything from the call, doesn't follow up from anything on the call, and sends no actions.