This is the official discussion thread for the webinar:Leadership Webinar Dec-2016 - All Channels Open - Facilitating Clear and Open Communication Presenter: Jane Farley When: DECEMBER 8, 2016 4:00 PM EST (UTC-5) Link to recording: https://www.projectmanagement.com/webinars...n-Communication Synopsys: Genuine feedback and open vertical communication are fundamental to effectively leading comprehensive and successful projects and programmes. Honesty, observation and evaluation from all tiers enable a leader to understand the dynamics of their team and project, providing the flexibility to make adjustments accordingly. In this session, Jane will explore the vital importance of clear two-way communication between leaders and team members.
Questions from the webinar: Diana E. A. García Sánchez: Question: By globalizing you mean lack of cultural/gender awareness? Murray Leslie 2: QUESTION: engaging 'wallflowers' or shy workers for feedback Ahmed Dabaja Gebara: question: how can prevente problems when the industry or bussines has no copertative database Diana E. A. García Sánchez: Question: What would you do in a culture socil/country where being direct is considered highly rude? Suzanne Siccone: Question: ANy suggestions to PREVENT multi-tasking during a virtual meeting. Saving Changes...
Murray LeslieSoftware Quality Assurance| Ocean Networks CanadaVictoria, British Columbia, Canada
"Who's to blame?" vs "What went wrong?" my org is constantly putting out bush fires, no time for reflection or continuous improvement. How can I convince all team members to take time to document the problem, the root-cause, and suggestions how to prevent or mitigate similar incidents in the future. Is anybody else in this situation? What are you doing?
...
1 reply by Jane Farley
Dec 08, 2016 5:28 PM
Jane Farley
...
Murray you raise a good point. One of the ways you can deal with this is from the outset of the project build the lessons learned register. Capture the "mistakes" or "problem" as you go (if you are not already capturing them as issues. Then at key phases/ stage gates/points in the project factor in time to add to the lessons learned register and for their review/analysis and what can be done differently.
You could also have an agenda item at the project meeting to consider what might need to be changed for improvement..
Saving Changes...
Penny WickmanPM III| Xerox CorporationPleasant Shade, Tn, United States
Thank you for an informative webinar! Some really great tips! Saving Changes...
Diana E. A. García SánchezDoctorate in Direction of Organizations, Master in Computer Systems and IT| CFECiudad De Mexico, Mexico
Question: What would you do in a culture social/country where being direct is considered highly rude?
...
1 reply by Jane Farley
Dec 08, 2016 5:22 PM
Jane Farley
...
Great question. In my country we tend to call that being tactful. However, it depends on the circumstance. If you are meaning in the situation where you are trying to give feedback, then building a relationship is key, before you try to impact the feedback (especially if it is negative feedback on their performance). Whereas good news or compliments are generally well received without needing to put too much effort in to the relationship.
Question: What would you do in a culture social/country where being direct is considered highly rude?
Great question. In my country we tend to call that being tactful. However, it depends on the circumstance. If you are meaning in the situation where you are trying to give feedback, then building a relationship is key, before you try to impact the feedback (especially if it is negative feedback on their performance). Whereas good news or compliments are generally well received without needing to put too much effort in to the relationship. Saving Changes...
"Who's to blame?" vs "What went wrong?" my org is constantly putting out bush fires, no time for reflection or continuous improvement. How can I convince all team members to take time to document the problem, the root-cause, and suggestions how to prevent or mitigate similar incidents in the future. Is anybody else in this situation? What are you doing?
Murray you raise a good point. One of the ways you can deal with this is from the outset of the project build the lessons learned register. Capture the "mistakes" or "problem" as you go (if you are not already capturing them as issues. Then at key phases/ stage gates/points in the project factor in time to add to the lessons learned register and for their review/analysis and what can be done differently.
You could also have an agenda item at the project meeting to consider what might need to be changed for improvement.. Saving Changes...
Community Champion
