Skip to main content

Checklist for virtual meetings

The following checklist is constructed from the following paper on Project Connections, Best
Practices from Experiences in Facilitating Virtual Meetings (Mittleman, Briggs, Nunamaker).
  1. It is harder to follow a meeting process from a distance.
    • Be explicit in the planning of the meeting.
    • Poll the participants for their vested interests.
    • Whiteboard/flipchart the agenda and refer back during the course of the meeting.
    • Do not ignore process transitions.
    • Do things in an incremental fashion.
  2. People don't get feedback when working over a distance.
    • Facilitate feedback.
    • Encourage frequent milestones and checkpoints.
    • Use of alternative methods for feedback.
  3. People forget who is at a distributed meeting.
  4. It is harder to build a team over a distance.
    • Create clear, unambiguous goals for the team.
    • Have kickoff meeting face to face.
    • Have mutual breaks.
  5. Network connections are unpredictable.
    • Assume that there will be a technology learning curve.
    • Have a fallback plan.
    • Have a techie on-call.
    • Establish a mechanism for meeting reboots.
    • Provide a process map to participants.
  6. It is tough to sort out multiple communication channels.
    • Don't chase new technology.
    • Separate tasks and processes.
    • Use video where it is beneficial.
    • Video is not only about talking heads.
    • Use collaboration tools.
  7. There is an art to using audio and video channels in a distributed meeting.
    • Encourage dialogue rather adopt a briefing format.
    • Leverage relationships.
    • Be aware of the microphone location.
    • Change the focus to different sites.
  8. It is harder to converge over a distance.
    • Use ad-hoc teams to negotiate compromise solutions.
    • Creat a team document repositary.
  9. Different time virtual meetings are different than same time virtual meetings.
    • Make certain there arn't easier methods to complete tasks.
    • Value output.
    • Make instructions explicit.
And don't forget the Donuts!

Another checklist for virtual meetings is here.


Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi