Skip to main content

Project Jeopardizer (PJ)

Who are Project Jeopardizers?

As the name implies, these are the people responsible for jeopardizing your projects and accelerating their failure! They gracefully and confidently push projects to drift from their track to the disaster track.

Project Jeopardizers (PJ) AKA Project Monsters are people who have authority and who, for some odd reasons, have a say in your work, and can destroy it completely by the directions they give and the decision they make. They usually help driving projects to their catastrophic ends or in the best cases they lead projects to disastrous situations only! These people run afterwards and disappear from the picture. They also exist in the background of every team project photo.PJ

In most of the cases, PJs think they are doing this for the benefit of the project. They are also the first people who panic in stressful situations and leave everything for others to save. They are also very professional in transferring the blame to others, and they are the ones who steal the credit from others in case of success.

People pertaining to this category can be clients, consultants, process improvement people, auditors, strategy people, top management, middle management and sometimes people from your own team or from other helper functions in the same company.

And above all, PJs are the people who get promoted while good people commit suicides or die early with heart attacks because of PJs!

PJ Job Requirements

PJs should have the following qualifications to best fit in their positions:

  • They should be able lose their e-mails and papers
  • They should have the power to destroy your work
  • They should have the ability to impose additional sudden unnecessary work at any time to overload the project
  • They should be able to convince others that they are working for a greater cause which they don’t understand
  • You have to explain everything to them because sometimes they don’t understand and then they forget
  • They forget a lot and others have to remind them with everything
  • They have to be chased to get things done

PJ Characteristics

They are also characterized by the following:

  • They are very bad listeners
  • They believe they understand everything
  • They believe they have a vision
  • They don’t respect plans
  • They always come up with unplanned activities, extra demos & releases
  • All their requests are important and urgent
  • They believe that assigning more people on the project means it will finish faster
  • They believe that project’s dependencies are deficiencies
  • They think Software is magic, and that they it’s a tool to con clients and get money
  • You have to cover their mistakes and bad decisions, and maybe sacrifice yourself for them

PJ Attitude

Their attitude is always driving you crazy while they try to convince you that it’s your fault!

  • They always “have something else in mind
  • When you agree on anything with, they do something else, most of the times, totally something different
  • They think that PMs are time wasters, and they deal with them on this basis
  • They enjoy watching you suffer!

How to Deal with PJs?

As a PM you have to absorb everything as it became kind of normal that others try to destroy your work. I tried many ways and tricks to deal with and handle PJs, and I still can’t find a silver bullet advice to end your troubles with them. Among the methods I tried were the following:

  • Escalate on them. This never worked with me as it always fired back on my team and myself
  • Ask to leave the project. Sometimes it works fine, and they are the ones who leave instead of you
  • Think about something else when talking to these people… I was once thinking about the bus and if I will be able to catch it or not, and this made time pass quickly… Unfortunately, I didn’t catch the bus this day!
  • Let them say what they want, then do exactly the opposite. This worked well many times
  • Let them face the problem or the situation and they will retreat or fail. This trick was successful somehow
  • Take some time off, and put them in charge instead of you. This also proved to be good somehow, although this trick has to be used very carefully
  • Quit your job. I did this once, I wasn’t very happy, but it was the only way to get rid of them as there were many of them

The end point is that you have to fight for your project to live… you have to fight for your project to succeed.

Comments

Popular posts from this blog

The Triangle of Tactics

Sometimes referred to as the Triangle of Horror… where the PM tries his best to maintain his balance while walking on the very thin project rope between this triangle and the Project Constraints Triangle (time, cost & scope). The triangle sides represent: The Team, The Client and The Management Every side of this triangle is obsessed by the sole idea that the other two sides want him dead, i.e. the team thinks that the client and the top management want him dead and vice versa. Usually a good PM gets lost while trying to maintain this triangle in good shape to keep all parties satisfied and happy while making them think they are his first and only priority to get out what is needed from them for the sake of the project. From my perspective, this is a much harder balance to keep rather than maintaining and managing the Project Constraints Triangle… It highly depends on people, their culture, maturity level, and on the PM’s ability to understand this and deal with it in a

I am a Project Manager

I am a Project Manager and I love my job… I am a project Manager and I love doing my work! I am nothing more but a Project Manager amongst many others. I got married to my work (not job) after a great love story which started from early childhood ( coming soon ). I started my career as a Software Developer in the late 90s, then held many positions in the field of Software Development, some were promotions and some were kind of additional assignments due to my performance. Among the positions I held are Developer, Team Leader, Project Manager, Project Leader, Senior Project Manager, Senior Project Leader, Program Manager, Business Analyst… though I was dreaming about becoming an Architect! But seriously the job I loved the most is Project Management. The things I hated the most in my early years were politics and economics/finance, which both became the core of my daily work for some years now! 94% of my experience was built by working in Software Houses as a vendor/provider and

5 Reasons not to listen to a PM (for Managers)

Usually a PM cares about his projects and is keen to develop them as per the planned budget, time and scope. However, managers should not listen to their PMs for the following reasons: 1. PMs are Time Wasters PMs plan… They study and mitigate risks and project issues in proper ways to guarantee the smooth execution of the project. Planning is a bad practice that PMs should stop using and referring to whenever they discuss a project related issue. Plans are not really needed and in most of the times they are useless because no one follows them (all gratitude and respect reserved for PJs). Also, it is preferable to face risks when they fire. Anyways, who really cares for risk mitigation and contingency stuff! Let’s face surprises when they arise and use panic mode to push on teams to solve their issues! 2. PMs Forecast PMs track their projects and use trends, issues, project and client historical data to forecast project status and use corrective actions properly to maintain thei