There are 2 important ways to manage online conference calls and effective handling of virtual meetings
1. Organizing the call
2. Leadership during the meetings
Important steps to note during the Organizing the calls:
- Time management - Rehearse all important calls
- Duration of the call based on the agenda and number of participants
- Tasks split as micro activities for tasks and smaller audience
- Issue resolution calls to identify dependencies and vendor involvements
- Extend invitees to dependent resources on technical aspects
- Subject: Summarize on the call to address queries, clarifications and approval requests
- Keep agenda crisp and state the urgency s needed
- Outlook Repeats/ recurring invites not adding as issues
- Bullet points on agenda for clarity to discuss and give background
- Repeats should not be more than 7 weeks or 2 months
- Invites can be extended and knowledge shared
- You should know your participants and customers management
- Action items log appended in the minutes with ETAs (Expected time for action completion)
- Keep watch on the silent spectators for their feedback
- Know the features of the bridge line
- Go on mute during noise behind you
- Record the meetings with the permission of the participants
- Disconnect single line of disturbance
- Audible and clarity is important
- Speak slowly, with right modulation, pause and listening to others
- Controlling of the call is important
- Identify line ups of key stakeholders
- Information to get from resources participating
- In Project calls, round table to capture risks and constraints from all concerned
- Repeat calls with continuous trackers, action items log for continuity and process
- Time zones availability to be embedded in the invite itself
- Conflict management is vital for leadership
- Severing of the tasks, changes and need for managers to provide resources during on and out of business hours
- Maintain harmony on calls with no blame game
- Provide correct information in calls and get info on the root cause analysis if needed
- Identify management calls is in operations management and not project management
- Buy in on due dates and expected time for delivery during the calls itself
- Decision and discussion groups to be clearly identified
- Trackers with percentage completion on the tasks needed for calls
- Voice modulation to command authority
- Handle the ice breaking filling the gaps
- Give an opportunity for all people on the call to talk
- Make sure bridge is not silent
- Provide clarity and audibility to all is important
- Set priorities, goals and action owners for tasks as a leader
- Prepare a project plan with the technical teams
- Schedule the call with scope and tasks
- Pre-preparation for the call is important
- Confirmation with all technical teams and call in control during ownership conflict
- Technical resource non-responsiveness should be clearly handled
- Tracking project status with slippages handled effectively by leaders
- Change window management - change not going as per plan
- PM to facilitate to conclude on issues and PM decision watch on roll backs
- Checking point calls during changes is important
- Meeting invite should have proper audience, call details, agenda, key stakeholders and action items defined
- Customer requirements gathering calls should have organizers and bridge participants clearly defined
- Identify the issue or the problem that the customer is not happy about the project or progress of the program
- Scope creep - with additions or deletions of the CR Process
- Deliverables not in quality- technical fixes to be identified
- Missed milestones and deliverables - how to bring them back to the track
- Red and Amber calls presentation to the customer diplomatically with offered solutions and back to green plans
- Customer non-responsiveness situation, leaders should try to have one on one discussion to get their inputs
- Escalations on team members - all criticisms to be handled privately
- Change outage windows extended or roll back needed- should be thoroughly communicated to the customer
- End customer or application owners approvals for Go/ No Go - plan B preparedness to handle the same