Kepler
Cornell Big Red
If I were asked to be a PM, I would politely decline. Thankfully, in my career, I've never been asked- but then again, probably 20 years ago, they became an official position.
I'm not sure how to describe them, but we spend too much time worrying about the message to management vs. actually talking about the project. And because of that mindset in management, our section meetings have transition to us talking about our projects to mostly wasting time updating the one pagers for our managers.
Which means we have both PM's and managers to deal with instead of focusing on the actual project.
All of the PM's I've encountered are amazing at being passive aggressive to people- for every error state, they manage to blame everyone- thinking that if everyone worked on the issue at the same time, it would solve the problem. But that hardly ever does anything other than make people mad.
PM's tend to think they know about the technical details they are "managing" which makes them pretty dangerous when they hardly ever know enough.
So what I'm hearing is:
1. Not respecting the team's time
2. Not recognizing the PM's personal technical ignorance
3. Fostering a fault-finding, distrustful environment
And what would help would be:
1. Ensuring time taken on management results in a commensurate decrease in task time and/or some magically equivalent increase in quality
2. Being humble, asking questions, having a technical peer to evaluate whether management objectives and guidance make practical sense
3. Being open, suspending judgment, focusing on the task and not on supposed deficiencies in performance
Is that fair?
I really want to be "one of the good ones."