© Ron Chapple Studios | Dreamstime.com
Web Conferencing Week
So, if this were really a weekly feature, we’d be on number 052 or something, and this is only number 14. Thus, why not two in a row?
The poor sap fallen asleep over his laptop in front of his desktop PC in the illustration doesn’t resemble yr (justifiably) humble svt in the slightest, but it’s what I’ll look like in a few hours.
No, I won’t suddenly get 35 years younger, grow back a lot of very dark hair and become vaguely Asian.
But, I’m working very late tonight, and very early in the morning. Sigh.
As I’ve often noted in this space, I support the enterprise web conferencing application from an end-user perspective. A vendor once described me most flatteringly as the manager of the end user experience for my technology.
So, in addition to working with the other, more technical, members of the team (server administrators and system architects); developing curriculum and reference materials; teaching nearly 4,000 fellow employees in the past six years to use web conferences by attending my training web conferences; besides all that, I’m the guy who gets the call when users have critical conferences that require my professional expertise.
Got the call a few weeks ago: we’re doing an important meeting three times, because the sun never sets on our global enterprise: once for the Asia-Pacific region, once for Europe and once for the Western Hemisphere. 8amCEST, 1pmCEST, 6pmCEST. We’ve had trouble with the web conferencing tool in the past, please help.
I endeavor to honor requests like this. But, of course, I’m sitting in the U.S. Central time zone.
8amCEST (Central European Summer Time) in, yes, central Europe, the origin of the meetings, translates to 1amCDT (U.S. Central Daylight Time).