- Having asynchronous communication channels and making heavy use of them can have great effects on productivity.
- Every question asked in an internal Slack is a policy failure.
- Asynchronous environments allows for self discovery without interruptions:
- You can keep on your flow without waiting for someone to give you details.
- You can get into “Deep [[Focus]]” session without context switching that allows for better [[productivity]].
- You can work whenever, since you are not dependent on anyone immediately.
- You’ll have written records of everything.
- Async communication takes more time but it enable better thinking. Learn to[[Asking Questions|ask better questions]] and [[Writing|write requests]].
- The 4 components of a great asynchronous message:
- Enough information to cover all follow-up questions.
- A deadline. When do you need a response by? How urgent is it? Which task is being blocked right now?
- Links, images, and as much supporting material as possible that will help illustrate your thoughts.
- A concrete need. What do you want to get out of the communication? Approval on a task? An asset of some kind? Be clear.
- Beware of the (cultural) Power Distance Index. The lower the PDI, the more direct communications are preferred; the higher, the more diplomatic the communications are preferred.
- Asynchronous communication is efficient and inclusive, ensuring that discussions are well thought through, self-documented, and accessible to all team members, regardless of their work hours.