Deadly qualities of a Project Manager

A project manager is responsible to lead a project efficiently and successfully. He needs to lead his team in such a manner that they work in sync at all times and deliver the desired results at a stretch. Since he is the project planner and the project heavily relies on him, he or she has to ensure that they do not make any mistake or make one and overlook it.  However, there are some sins that a project manager should never ever commit. Read on to know what they are.
Identifying the Sins:
There are some habits that are nothing less than sins that no project manager should ever possess. 
Bad Attitude:
Arrogance and complacence are two qualities that should not be a part of any project manager’s system. Sure, they may lead the project management through its entire course, but that does not mean the project managers develop a bad attitude that could be interpreted as being superior to others or knowing more than the team members. A leader is supposed to stay humble to earn the trust and respect of his team. A bad attitude earns disrespect and revulsion from the team-members.    
Being Disorganized:
A project manager has to streamline the processes of any project. This offers clarity and structure to the project, thus maintaining a smooth flow and timelines. However, if the manager himself is disorganized, it may build up stress within the team and affect the overall progress of work badly.  If the manager repeatedly asks for the same details every day, forgets important information by trying to remember instead of noting them down and is constantly looking for the information or things he ‘misplaced’ or ‘doesn’t remember keeping’, the team suffers and gets frustrated, resulting in a dip in the performance
Poor Communication Skills and Indecisiveness:
A project manager needs to communicate properly and clearly with his team and people concerned with the project. The lack of communication leads to wide gaps in the structure of the project. Being indecisive reflects poorly on him and the team. He needs to be able to make sound decisions, no matter how tough the situation is instead of letting others make a call, nodding in agreement and then blaming others in case something goes awry. 
Overlooking Professional Ethic:
Ethics are important for everything one does. There will be a stark difference between the teams who are led by a leader who prioritizes ethical behaviour and strong character over who doesn’t. The team will follow the same, thus reflecting in how the project is being directed. Overlooking ethics will corrupt the project, create an unpleasant environment and even lead to unfortunate instances in the near future. 
Leading a project implementation based on a set of assumptions will guarantee a downfall. Assuming that the team-members know their role, that the project will run smoothly no matter what, that some important information will reach the team, that the team is working properly, that the project will be meet the deadline irrespective of the numerous glitches are some of the common assumptions that have brought down various projects. Assumption leads to many unpleasant results, which is why it is a sin that has to be eliminated from the core.
If a project manager shows distrust at every stage of the project, it will eventually create rifts within the team. The managers need to display trust, wisdom and demonstrate integrity to expect the same from the team. Questioning the judgement of the team-members, not believing in them, doubting if they can efficiently follow the plans and use the skills and resources like agile tools to their true potential and mainly not standing by them will eventually result in the team going against him or being replaced by a better manager who trusts his team to do well. 
Being a Better Leader:
A good leader is not just about delivering great results on time. He needs to be able to hold a team together, lead them well and maintain harmony at work while setting a great example. If he falls prey any of the above mentioned sins, it won’t be long when the team and the project are compromised. 


Author : Uma Daga

About Author
Uma Daga