A Project Manager must possess “multiple personality” especially when coming to the requirements. He should jump into the shoes of all the stakeholders and domain to get the correct picture of “what customer want”. Sometimes customer may not be knowing the exact requirements so project manager or a BA (business analyst)’s help is required to build the initial requirements.
The workers, say Developer of an IT company may be too technical and miss many points of the business cases. But to find out what all things he might have missed, PM should be able to think from his side too.
When thinking about issues outside the job, PM must understand the feelings of the team. If the requirement is not clear, employees will not be able to execute the job correctly and at the end it will be just guess work. Don’t assume everybody understand the requirements even if it is a very simple one. Sit with them and discuss all the issues including their out-of-work stuff. Discussing out-of-work matters will give them confidence that you are supporting them in all the aspects. Communication with stakeholders is very important even if it is a Yes or No subject.
Project Manager is the glue to co-ordinate all the stakeholders in single virtual place. Business communications must be transparent to avoid end-of-day surprises. PM should turn to a BA, Solution Architect, Client Tester, Worker and all the available forms of stakeholder throughout the life of a project for the accuracy of the product or service result.
- Your experience might tell you not to go with a challenge but listen to new ideas. Others also got experience
- Sometimes brain weights more than experience. Give them a chance
- Don’t say ‘NO’ straight away. People are different. Some people might explain why it is a ‘YES’ but some people will go silent, thinking ‘don’t argue with a fool’
- Nothing is impossible. Brainstorm! you will get plenty of solutions in paper
- Look and smile to opponents after any idea-fight. You need them till you resign. Don’t expect them to give you back a smile
- Know to whom you are talking to
- Silence can bring miracles, but know when to be silent and when to make sound
- Defend with positive statements against negative ones but not vice versa
- Analyze, analyze, analyze and analyze before projecting a solution. Even your third analysis can be wrong.
- Always produce proof/evidence to support. Quantifying will reduce 60% of talks
- Pictures and prototypes can talk
- Let mirror and a recorder be your draft audience for complex problems. If yourself do not understand the solution, nobody will