Get Lynne's new brochure

 

 

 

 

 

Read the Whitepaper on "10 Challenges of Leading Today's Workforce and what to do about them"

 

 

 

 

 

 

 

 

 

 

 

Listen to Lynne Cazaly's interviews on Spotify

 

 

 

 

 

 

 

 

 

 

 

 

New Book coming soon

Clever Skills

How to use your greatest human capabilities for the unfolding future 

 

 

 

AS PUBLISHED IN

 

 

 

 

 

 

 

Award winning & Best selling

10 x author

 

 

 

 

 

 

 

 

 

What people say...

 

 

I acknowledge the traditional owners of the land on which I live - the Yalukit-Willam - and pay my respects to their elders past, present and emerging. 

 

 

 

 

 

 

 

« Lean Leadership Lessons - the Visual Notes Story | Main | A Blueprint for Meetings, Workshops, Conversations »
Wednesday
Dec112013

The ultimate in remote and distributed collaboration

When I'm running facilitation training programs and I gather a bunch of 'concerns, questions, challenges' at the start of the day, many people raise the remote hookups and telconference topic.

Whether it's a video hookup or audio only, there are plenty of tricky challenges:

- how do you keep people engaged

- how do you KNOW if they're engaged

- how do you achieve what you need to do in the time available

- how do .... <insert your challenge and question here!>

I am an occasional listener (wierd as it may be but thanks to my father's careers and keen interest in all things mechanical) to the Air Traffic Control feed of my local airport in Melbourne. 

Think about it - hundreds of people flying through the air at speed in the airspace above you, in big metal tubes, with a couple of people 'up front' in control of the metal tube. 

On the ground, air traffic controllers observing, managing and directing traffic through and around the airspace. 

I think this is the ultimate in remote and distributed collaboration and communication. 

Heights, speed restrictions, approaches, departures, angles, gate allocations, weather advice, wheelchair requirements for passengers (yes, they arrange this in the air) and many other key pieces of information are communicated, resolved, discussed and arranged with some, but not full visuals. 

Shorthand, codes and abbreviations are used as part of their operational jargon. It's efficient.

Questions are asked by pilots - 'can we cancel our speed restrictions'? And they are answered by air traffic controllers.

Controllers ask questions of pilots - 'can you use runway 27 or do you need 35'? 

And problems are solved - 'our headset for arrivals transmission is not operational. Can you relay please?'

If day in and out these critical pieces of information are able to be encoded, communicated and decoded in what can be perilous environments, a phone or video hookup with the team in another city shouldn't be so hard!

  • You must allow more time than you think you'll need for the topic.
  • Allow for time to introduce, engage, map out the agenda, take questions.
  • Allow time for problem solving, information sharing and collaborating.
  • Allow time for general discussions and 'wonderings' by participants too. 

In your haste to get 'stuff done', you might be communicating some messages you had no intention of conveying! The consequences could be far reaching and the rework may be costly and time consuming. Check understanding - check again for questions. 

Play air traffic controller at your next remote meeting and focus on clear communication and great collaboration. 

And now... tuning in to the feed, the massive A380 is coming in to Melbourne from LA. QF94. Now that's a BIG project to get on the ground safely!

A view from the tail camera on board the A380, coming in to land in Melbourne from LA. 

 

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>