Master the art of synchronous & asynchronous communication

28/3/2024
Collaboration
Replay
Collaboration
Replay
Link to form

Master the art of synchronous & asynchronous communication

Choosing the right channel for the right message

Fastening the frame

Create clear communication rules based on the urgency and complexity of your messages.

Use the Urgency - Complexity matrix to select the appropriate channel:

Favoring asynchronous technology 

Asynchronous: any communication that does not require a simultaneous connection between sender and receiver.

1. The advantages of asynchronous technology

To improve your use of asynchronous communication, capitalize on alternatives to e-mail:

  • The shared document: for collaborative work or to list points for discussion at a future meeting
  • The event description on Outlook: use it to share the agenda in advance
  • The Teams message you can come back to later
  • Voice memo or video recording

2. Coaching to anchor the rules

To bring these rules to life within your organization, question and reframe your employees on : 

  • The channel: "Why don't you find a moment when we can talk about it in person?
  • The need: "Do you need me or is this for info?"
  • Urgency: "I don't see any urgency, we'll talk about that at our next item."

Improve your team's written communication

1. Transmitters: put yourself in the receiver's shoes

An e-mail must answer 3 questions from the receiver to be read: 

  1. Why do I have to open it?
  2. Should I do it now or later (5, 10 or 20 minutes)?
  3. Do I have the essential elements (and only those) to decide what to do (reply, plan a reply, archive)

2. On written messages: coach without demotivating

Give a tip

  • "You're more likely to be read if..."
  • "If you want us to get back to you by a specific date, make it clear.

Don't punish

  • "Your message is impossible to read"
  • "You wrote me a paving stone"
  • "Can you make it shorter?"

Creating quality synchronous moments

Our feedback after 250 workshops, 500 hours of remote training and 2,000 registrations for the Remote Academy:

Tops

  • The moderator has a true leadership posture: introduces, involves, explains the reason for the meeting and concludes.
  • Energy isn't just a matter of form: you have to redouble it to make it go the distance.
  • We can be directive and engaging : distributing the floor works better than asking "any questions?"
  • Creativity does not mean improvisation: the more you want to collaborate, the more you have to come prepared.

Flops

  • Energy-free, almost subdued launch: "OK, let's go".
  • No demands on preparation: "Haven't you read the doc? We'll go through it together".
  • No consideration of participants and their desire to express themselves: microphones, non-verbal language... 
  • Over-interpretation of silence: "no questions asked, okay what I meant..."
  • Poorly prepared participatory sequence: "we've got 10 minutes left, any ideas on...?"
  • Conclusion without energy or message

‍Finally, here are some inspiring blogs from FROG (Full Remote Organisations):

Choosing the right channel for the right message

Fastening the frame

Create clear communication rules based on the urgency and complexity of your messages.

Use the Urgency - Complexity matrix to select the appropriate channel:

Favoring asynchronous technology 

Asynchronous: any communication that does not require a simultaneous connection between sender and receiver.

1. The advantages of asynchronous technology

To improve your use of asynchronous communication, capitalize on alternatives to e-mail:

  • The shared document: for collaborative work or to list points for discussion at a future meeting
  • The event description on Outlook: use it to share the agenda in advance
  • The Teams message you can come back to later
  • Voice memo or video recording

2. Coaching to anchor the rules

To bring these rules to life within your organization, question and reframe your employees on : 

  • The channel: "Why don't you find a moment when we can talk about it in person?
  • The need: "Do you need me or is this for info?"
  • Urgency: "I don't see any urgency, we'll talk about that at our next item."

Improve your team's written communication

1. Transmitters: put yourself in the receiver's shoes

An e-mail must answer 3 questions from the receiver to be read: 

  1. Why do I have to open it?
  2. Should I do it now or later (5, 10 or 20 minutes)?
  3. Do I have the essential elements (and only those) to decide what to do (reply, plan a reply, archive)

2. On written messages: coach without demotivating

Give a tip

  • "You're more likely to be read if..."
  • "If you want us to get back to you by a specific date, make it clear.

Don't punish

  • "Your message is impossible to read"
  • "You wrote me a paving stone"
  • "Can you make it shorter?"

Creating quality synchronous moments

Our feedback after 250 workshops, 500 hours of remote training and 2,000 registrations for the Remote Academy:

Tops

  • The moderator has a true leadership posture: introduces, involves, explains the reason for the meeting and concludes.
  • Energy isn't just a matter of form: you have to redouble it to make it go the distance.
  • We can be directive and engaging : distributing the floor works better than asking "any questions?"
  • Creativity does not mean improvisation: the more you want to collaborate, the more you have to come prepared.

Flops

  • Energy-free, almost subdued launch: "OK, let's go".
  • No demands on preparation: "Haven't you read the doc? We'll go through it together".
  • No consideration of participants and their desire to express themselves: microphones, non-verbal language... 
  • Over-interpretation of silence: "no questions asked, okay what I meant..."
  • Poorly prepared participatory sequence: "we've got 10 minutes left, any ideas on...?"
  • Conclusion without energy or message

‍Finally, here are some inspiring blogs from FROG (Full Remote Organisations):

FAQ

No items found.
Newsletter

don't miss a thing, join our newsletter

Thank you! Your request has been received.
Oops! Something went wrong while submitting the form.