Wednesday, 09 February 2011 10:35

The Bad and the Ugly

Written by 
Rate this item
(0 votes)

George_Feature_Feb9As in any profession, there are the great, the good, the bad and the ugly.  When we have PMs who in the bad and ugly category, we can often find the cause of their deficiencies in the “system of operations.”  The quality gurus tell us that 15% of defects are caused by personal error and 85% are caused by systemic deficiencies.  In the case of the deficient PM or BA the most prevalent causes seem to be unclear role and responsibility understandings and lack of training and support. This is exacerbated by ego issues – people not owning up to the fact that their skills are deficient or that they have a different understanding of their role than those around them.

Once there was a PM who was convinced that her job was to direct the players on the project team. She required that each of them run their daily plan by her and that she approve it. She regularly told them to do things her way, rather than the way they had planned to do it. In short she was a Theory X manager.  Unfortunately, she had a team of highly competent and motivated players. They hated her and were becoming increasingly de-motivated. 

The team members had been together on previous projects with another PM. They viewed the PM role as one that consisted of assigning and prioritizing the work, keeping track of progress, communicating with outside stakeholders, breaking down barriers to progress and keeping the team safe from interference and irrational expectations. They expected their PM to be a competent player and considered him to be a peer, not a boss.

What were the systemic and personal performance causes in this case? 

On the systemic side, the senior managers who assigned the PM did not take the time and effort to explore and define the role. They did not appreciate the relationship dynamics between members of the team. To them people were interchangeable pieces that were being paid to make things happen, no matter what.  In addition, the PM role definition was non-existent and there was no formal mechanism for performance review. Further, people were made PMs based on a formal credential (PMP or equivalent) and a history of being really good project team performers. 

On the personal side, the PM was without much in the way of emotional and social intelligence. Her ability to read the needs of the other team members was more than deficient; it was non-existent. She was so closed minded that she could not conceive of another way to do things than her own. The thought of letting the team figure things out for themselves was threatening.

The combination was deadly. After two projects, the team fell apart. Two members left the company and the other two asked to be transferred. There were no exit interviews (another systemic issue) so the firm never found out about the real reasons for the turn over. The PM surrounded herself with team members who liked or at least accepted taking orders and went on to be relatively successful in getting projects done on time and budget. After ten years or so, she began to burn out and ultimately was let go in a downsizing.

 Don't forget to leave your comments below.

Read 2051 times Last modified on Wednesday, 09 February 2011 11:40
George Pitagorsky

George Pitagorsky, PMP, integrates core disciplines and applies people centric systems and process thinking to achieve sustainable optimal performance. George authored The Zen Approach to Project Management and PM BasicsTM. He teaches meditation and is on the Board of Directors of the NY Insight Meditation Center.

Comments  

 
0 # Agile Scout 2011-02-09 04:27
So... are Project Managers killing the profession? http://agilescout.com/project-managers-are-killing-the-profession/
Reply | Reply with quote | Quote
 
 
0 # Don Solan 2011-02-09 04:43
This can be just ast true of Business Analysts who mis-handle Stakeholders depending on them to gather, communicate, and deliver business value from requirements.
Reply | Reply with quote | Quote
 
 
0 # George Baron, PMP 2011-02-09 05:59
A great project manager knows all methods to lead the team and project itself to get the success achievement. If needed, he/she should maintain his/her opinion (bought-in in the team) in front of any othher stakeholders, finally, the PM is accountable, responsible about the success or failure of the project, nobody else !!! If two members left the team? I guess there is a personal decision there while the human beings decision should be respected, no comment. I do not believe the two left the team due to PM. I had similar situation when two people left the team based on their decision, in that case they made that option, in my view, due to many hours working on the project without recompense. They found a better working place working less and get paid more :-)
Reply | Reply with quote | Quote
 
 
0 # Ed Kozak, PMP 2011-02-10 05:55
Not that people should take responsibility for their actions, I feel that many issues are caused, deliberately or unconsciously, by the top. You stated that " the senior managers who assigned the PM did not take the time and effort to explore and define the role. They did not appreciate the relationship dynamics between members of the team. To them people were interchangeable pieces that were being paid to make things happen, no matter what." So the PM that they put in place seemed to be the right fit for their perception. The fact that "the PM was without much in the way of emotional and social intelligence" seemed to fulfill Management's needs and, although not mentioned, I wonder if the reward system that was in place did nothing but enforce the micromanagement that the PM saw fit to perform. You also stated that "people were made PMs based on a formal credential (PMP or equivalent) and a history of being really good project team performers." This "halo effect" of feeling that a good, competent technical person makes a good, competent PM, is also a shortcoming of Mangement. While I do agree that this person was "an ugly PM" and that ugly PMs are out there, they're allowed to exist due to Management's shortcomings.
Reply | Reply with quote | Quote
 
 
0 # Ed Kozak, PMP 2011-02-10 05:56
...sorry, typo. I meant "shouldn't take responsibility for their own actions."
Reply | Reply with quote | Quote
 
 
0 # Tony Huynh, PMP 2011-02-10 08:14
This is definitely an ugly side of project management. Almost everytime people talk about PM, they talk about project delivery on time, on budget and on scope. How to get there is often forgotten. I this article, the PM was viewed as a hero, high performer to the company even with what she had done to her team members. Although she had to pay her price at the end, but only after 10 long years. Perhaps there is a need for more emphasis on team building and human touch in project managment.
Reply | Reply with quote | Quote
 
 
0 # George Pitagorsky 2011-02-11 11:26
Regarding George B's comment "the PM is accountable, responsible about the success or failure of the project, nobody else !!!" I must disagree. There is accountability throughout the stakeholder ranks. Senior management may be responsible for the failure of projects just as project performers may be. The responsible parties should all be accountable. While we don't really know why the people left the project team, there is great evidence to say that one of the primary motivators for individual motivation is the quality of supervision (see Herzberg).
Reply | Reply with quote | Quote
 
 
0 # George Pitagorsky 2011-02-11 11:33
The quality gurus tell us that the system of operations and the senior management responsible for them are responsible for 85% of the issues and in fact all of the chronic issues. While there may be some real ugly PMs, as Ed says their ability to hold on to their jobs is the responsibility of senior management. Le t's remember to have compassion for the PM in the story. She paid a personal price over the ten years. Her leaving was only the final payment.
Reply | Reply with quote | Quote
 
 
0 # H M Thakur 2011-02-14 15:41
Sometimes we do come across the detrimental effect of classic "Halo Effect", the article brings out one such case. Agreed that we come across PMs who are good, bad and ugly. Let us take time to ponder the root cause as to what makes them ugly, as rightly brought out in the article, lack of humality and treating the team members & PMs as mere interchangeable pieces leads to all this and more. PMs need to apply themselves and there is more to the defined processes, inputs and outputs. Certainly one needs to look at the team spirit, managing expectations of stakeholders which most of you would agree with me are equally important. More importantly, dealing with people who have feelings and emotions as our own, we need to be little more empathic and success would follow.
Reply | Reply with quote | Quote
 
 
0 # Paul Scioletti 2011-02-15 00:17
In many cases, PM's that are challenged in their role often have not worked as part of a project team, or specifically in roles similar to those which they are currently managing. Success in managing financial service administrators or sales staff does not easily translate into managing a technology project, whether the team is dedicated or shared resource. In addition, the PM must be adaptable to the demographics of team members and the culture of the organization or department in which the project resides. Direct, daily management may work well in organizations that constitute teams of recent graduates or having less than 1-2 years work experience, yet in organizations with more experienced personnel, such an approach will likely cause the team to be dysfunctional and result in diminished productivity.
Reply | Reply with quote | Quote
 

Add comment