[emadabdulrahim]

I also don't understand how async communication is bad for knowledge sharing. I find that well written documents of what the team learned, tech specs, user research, etc, to be far more effective ways to knowledge share, while keeping records of the information for anyone to pick up later.

I was recently interviewing at a really compelling startup backed by YC and I asked them how they communicate and knowledge share. The cofounder showed me pages and pages of well structures bits and pieces of things and findings the team come across and document. It's easily searchable and it's well categorize. It's their internal wiki, and I believe it is one of the most valuable assets a company can have. The startup relies on writing as the main method of sharing knowledge, getting async feedback, and gathering valuable information on important problems.

It is one of the main reasons I was intrigued and decided to join them. Their product is also awesome.