No-one likes Project Managers
And maybe they’re right.
Project managers have a bad name. Let’s face it, we’ve all come across people and whole companies that think project managers just cause problems. In their eyes, we insist on the production of arcane documents, we get in their way while they are trying to just get on and do the work, and we hold far too many meetings. And don’t get them started on the metrics. Or the milestones. Or the project plans. Or the requests for progress reports.
Now, you and I know that project managers actually add value. We help to keep the project moving forward. We help to keep the team focused. We help to spot problems early, and deal with them. We help to bring it all together.
But… sometimes, those people who complain about us? Sometimes, they have a point.
When team members are complaining about project managers, one of the main reasons behind it could be our fault.
If project team members are complaining about project management getting in the way, it means they aren’t seeing value from it. And that usually means one of two things: either a methodology is being applied blindly, or the project manager isn’t explaining what the value is.
Luckily, the way to solve either of these problems is simple: take the time to talk to your team. And I mean really talk, and really listen, not hold yet more meetings. If there is someone who is complaining a lot, sit down with them, and have them explain why they aren’t happy. Sometimes, you’ll find that they hadn’t realised the benefits to the rest of the project of what you are doing – or asking them to do.
Sometimes, though, you’ll find they have a valid point. Perhaps you have been insisting on a particular piece of information being gathered, or a particular measurement being made, because it worked on the last project similar to this. But maybe it isn’t appropriate here. Don’t be afraid to learn from your team members that you are being too heavy handed in applying a particular methodology.
Remember, no methodology is ever going to be a perfect fit for your project. You need to flex it, lighten it up here and there, toughen it up in other places. You need to borrow some pieces from one system, and other pieces from another, to fit them together to make the right way for managing your project, right now.
So the next time you hear someone complaining about project management, take the time to talk, and to listen. You never know, they might be right.
What about you? Have you come across people who just didn’t get project management? How did you handle it? Let me know!
[…] Go to the author’s original blog: No-one likes Project Managers | Project Management Guide […]
I think every seasoned PM met this kind of people. And to be honest I agree that most of the time it’s PM’s fault to have a team which doesn’t get it.
One of reasons of the situation looks like that is that PM has some kind of superpower: he can always tell the team “the customer wants it that way” and that’s something one can’t really deny.
My advice is to avoid this techniqe. Your solution, to talk with team members, to listen to them, is a way better. And if you don’t find reasonable people who are willing to discuss why something is important you can still use the superpower as a fallback plan.
We love our project manager, but he can be tough. The team has to be willing to default to his better judgement because, afterall, he is the man with the master plan. Doing this has never failed us. And though we may have grumbled our way through a few projects, our PM always pulls it off in the end. Open communication certainly helps the best, especially in a neutral environment.
I appreciate your efforts on this site. And am responding because, there is a lot of truth in your title – although “no one” is a bit of an overstatement.
I think hit at one of the core issues when you mention issues of how methodology is being applied and the need for explanation/understanding.
In my experience, especially in interactive agencies, PM-explanations won’t always drive change. Executive support is an important component too.
Keep fighting the good fight.
For laughs, take a look at what I and Dustin Hoffman have to say: http://pm2pm.blogspot.com/2008/12/project-management-there-is-no-evidence.html
It is absolutely true that Project Management is mostly seen as a Villain both by the team members as they feel project management is stretching them too much also by the Customer as the Customer thinks the Project Management is holding the information / deliverables.Thus it is the resposibilty of the Project Management to strike the balance.
If PMs are seen as villians, its because they aren’t doing all of their jobs. They may be wearing their a police caps and accountants’ visors, but some of the other hats they should be wearing have been forgotten.
Ultimately every successful project requires the willing cooperation of people, their understanding of what needs to be done, their acquiescence and their effort.
Managing people and communication (which includes listening and actually _addressing_ their concerns) is equally important as managing any other other aspect of a project.
If these are done properly, a PM won’t be seen as any worse than the executives and manager to whom everyone reports, and might be more trusted and better respected.
Ignore these at your peril, because very few project managers work in a project structure, most are in a matrix management environment. The people with whom you have to work can be forced to take the blue pill, but if they gag on it, it will come back and soil you.
I agree with most of the reasons mentioned in the previous comments.
In my experience, one very important reason for the push back from team members is because they simply cannot see what this guy is there for anyway. In a classic software team scenario, every developer and architect feels he/she knows more about the project and should not need to listen to someone with zero technical knowledge.
The only solution is for the PM to educate such team members as to the need for a project manager. We need to correct the expectations. Once they realize that project manager needs to be good in other things to make sure the project succeeds rather than be a technical guru, some of the resistance will disappear.
lethargicintellect.blogspot.com
The project manager is often the project messenger for communicating budget, schedule, and scope. Resources sometimes perceive the “messenger” as the bearer of bad news for communicating change requests and out of scope items. The “don’t shoot the messenger” phrase applies in this case and can also contribute to the perception of project managers.
May I just say what a comfort to divcoser somebody who genuinely knows what they’re discussing over the internet. You definitely understand how to bring a problem to light and make it important. A lot more people ought to read this and understand this side of the story. I can’t believe you aren’t more popular since you surely possess the gift.