Asynchronous Communication = There be Dragons!

Game teams are now commonly spread around the globe. With each of us working in our own time zone, it's easy to drop communication bombs onto platforms like Slack and Discord without first understanding how our words will be received.

We have lost the opportunity and the art of reading the room. We are missing out on the cues sent with body language.

In person we get early indicators telling us that our ideas are being well-received or absolutely inappropriate. Being in different time zones alone on our computers makes it compelling to go too far with big bold beautiful idea before we stomp right into a steaming pile-of-poop.

What can we do? Here are some suggestions. If you have more, let me know. cindi@cindiknapton.com

1. Assume that what you are writing could be misinterpreted. Read it back to yourself before you send it. Could this be taken the wrong way? Have I gone too far? What is my intuition telling me?

2. Go Slow. I know that's against one of the principals of start-up, but presenting your idea slowly will mimic an in person conversation. Start with something like "Hey Colleague! I know it's not my department, but I saw the super compelling work that you did on Gobbledegook. You've inspired me to share some thoughts, if your open to it?"

3. Write from a place of empathy. This is a challenging creative industry. Remember that the person you are writing to is a creative sensitive human being. They will better appreciate your communication when you convey respect for them and their work.

4. Address asynchronous colleagues with the same respect that you would show to a mentor. Think about how your mentor would like to be addressed. Consider your colleagues as peers and yes, even as mentors. There is something to learn from everyone.

5. Imagine yourself receiving what you have written. What else is the recipient managing right now? When will they be receiving the message? How invested are they in the item you want to discuss? How will they feel about what you’ve written? 

6. Articulate respect and appreciation before you get spicy. Start with a respectful acknowledgement of your recipient’s contribution to the team. This mirrors the old feedback sandwich -- smooth your path with a positive before you share your brilliant opinion of how to change what they have created.

7. Present your statements as “thoughts” not as absolute truths. Try something like: “Based on my work on other projects I have a suggestion that we might consider….” Avoid phrases that imply that your opinion is correct such as “Doesn’t work.” “Is wrong.”  “Doesn’t deliver.”

8. Get a feel for the tone of communications at your company. If you are new to a company, before you decide to “make yourself known,” watch and read. How does the CEO speak to the team? Do they make imperious take-it-or-leave-it statements? Or do they share their thoughts with an opening for feedback?

9. Accept the “No”. If you get a “No”, do not keep forging ahead. Understand that in professional communication, a “No” is unlikely to be delivered in a two-letter format. It is hopefully conveyed in a thoughtful response that carefully lays out why your idea doesn’t work. Read between the lines. Hear that polite explanation of why your idea isn’t appropriate and recognize it as a “No.” Then stop pushing your idea.

10. Emulate the responses that you receive from colleagues that you respect. Are they thoughtful, well organized, and considerate of the bigger picture? Can you emulate the professionalism? This is a learned professional skill. I am absolutely certain that they made some bold communication errors in their past and learned how to present their ideas in a thoughtful and respectful manner.

11. Ultimately: Just be nice!