Stephen SalakaDirector of Application Development| Tsunami TsolutionsMelbourne, Fl, United States
In current regulated projects, there is a lot of documentation as well as documentation required for formal project appraisals. Some team members, while great producers for project velocity, have a tendency to shirk their responsibilities for proper communication and reporting. What are some suggestions to help them focus on the necessity of documentation without becoming a nagging influence? Saving Changes...
Product Operations Program ManagerBarcelona, Cataluña, Spain
Great answers.
The soft skills of the PM in terms of convincing the ptoject team of the necessity to adhere to certain processes is also relevant. He/she must be convincing and persuasive, this is key and often more effective that what may be written in a management plan. Saving Changes...
Manfred KressSenior Project Manager, PMP| Atos Information Technology GmbHTaunusstein, Germany
All of you are right with your experiences and advices. But all teambuilding sessions, kick off meetings, "personal" talks, nagging, implemented processes and rules do not help when someone is not doing his/her job anyway. At the end you as the PM are the responsible that the work is done.
Once I was in such a situation (not about propper documentation but similar) and as ultima ratio I removed him from the team. I've done all you and I have mentioned incl. a meeting with his manager and HR. Maybe it was a warning to others but it never happened again. It sounds harsh but sometimes you to make an unpopular decision for the benefit of the project. Saving Changes...
When I've worked "in the dark side" more than 10 years ago, documentation was a nightmare. I said "dark side" because of years ago, our managers aren't real leaders, and they don’t lead, they only said “I want this for yesterday”, without explanation. Then, I was on the dark side, without view or understanding the importance of documentation and working as IT consultant.
After that first nightmare, I’ve worked with PROJECT MANAGERS (Capital letters, because they have all the skills and knowledge for this profession) that explained to us the real importance of documentation, knowledge management was part of the project. Now, I can imagine how hard they have worked to move more than fifty people team from one side to the other.
As I remember
- Clear Communication
- Support from the organization, it means documentation time was included in the consultant time that they invoiced to the client.
- Team building sessions basically was some role plays to understand what happen when you’ll arrive at a new company and you don’t have documentation.
That happened more than 10 years ago, now as a project manager, at the moment, the teams that I've led have a clear understanding of the importance of documentation.
...
1 reply by Rami Kaibni
Dec 22, 2016 10:57 AM
Rami Kaibni
...
Excellent feedback Maria - That's exactly right. It is a combination if several efforts. I am with you 100%
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Dec 22, 2016 10:50 AM
Replying to Mayte Mata Sivera
...
Interesting answers, my 2cents.
When I've worked "in the dark side" more than 10 years ago, documentation was a nightmare. I said "dark side" because of years ago, our managers aren't real leaders, and they don’t lead, they only said “I want this for yesterday”, without explanation. Then, I was on the dark side, without view or understanding the importance of documentation and working as IT consultant.
After that first nightmare, I’ve worked with PROJECT MANAGERS (Capital letters, because they have all the skills and knowledge for this profession) that explained to us the real importance of documentation, knowledge management was part of the project. Now, I can imagine how hard they have worked to move more than fifty people team from one side to the other.
As I remember
- Clear Communication
- Support from the organization, it means documentation time was included in the consultant time that they invoiced to the client.
- Team building sessions basically was some role plays to understand what happen when you’ll arrive at a new company and you don’t have documentation.
That happened more than 10 years ago, now as a project manager, at the moment, the teams that I've led have a clear understanding of the importance of documentation.
Excellent feedback Maria - That's exactly right. It is a combination if several efforts. I am with you 100% Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Most people want to do well, including at work. If you tell them that not completing the documentation reflects poorly on their performance, you might help them get motivated to do the work. Obviously, you want to use this "stick" tactfully. Saving Changes...
Stephen:
Every project is different but I'd recommend three things:
1. Talk to the individual about the deliverable document and listen to their issues. Better understand their motivation to participate and meet deadlines.
2. Reaffirm their participation by updating your RACI chart, schedule with names assigned to tasks/deliverable, issues list with outstanding items due
3. Acknowledge their participation if they comply with your request or if the don't talk to their functional manager immediately.
There are plenty of resources that want to work on projects; if necessary work with your sponsor to escalate resource issues.
Emotional intelligence, conflict management, assertiveness, change management and leadership are skill-sets that you will need to continue to develop since it will help you to work with difficult people, complex projects, stakeholder expectations and more. Saving Changes...
Community Champion
