Friday, September 10, 2010

Conference Calls Gone Wrong



Sometimes people struggle because they don't understand the technology they're using. I often feel that's the case with some of the equipment we use at my office. We're a satellite location of corporate headquarters, which is located in New York (surprise, surprise). So we often have meetings in which we video conference into New York. I'm always entertained at how long it takes them to troubleshoot what's wrong with the video conference - why we can hear them but not see them, etc.

Sometimes people are just idiots, and are oblivious to the impact that their use of technology affects those around them. I experienced one of these moments yesterday. The CEO in New York was speaking to the company. Big deal. Our office wasn't the only office video conferencing, and many others were calling in to listen from various parts of the country. About halfway through the meeting we heard a phone ring from one of the many lines connected to the mothersource. For the next few minutes, I was treated to one half of a personal phone call. Following that, we heard a baby crying, and somebody moving things. This went on for a good 30 minutes while the CEO (whose receiver was silent, and was therefore unable to hear the background noise) went on with his presentation, unaware of the problem. Multiple times, someone from another line voiced in to request that the person put their phone on mute. But the efforts were futile. The guilty party was obviously not paying any attention to the meeting.

On the other hand, it did break up the monotony. So thank you, anonymous stranger.

1 comment:

Chism said...

LOL

I was talking to a friend who shares a small enclosed office with another employee. Friend was forced to listen to an hour and a half phone conference call.

I think it would be better if they flew all the employees and a guest to NYC for a week!