Yeah, "ask a question via email, wait for a response" while using a nominally async channel isn't really adopting async processes (neither is your manager email

Yeah, "ask a question via email, wait for a response" while using a nominally async channel isn't really adopting async processes (neither is your manager emailing you at 7pm your time and expecting a reply in less than 14h). At the minimum, that email should be going to an internal mailing list where some other knowledgeable employee can answer, and in any situation where that one Q is actually blocking and there is no other work that can be done in the interim, there ought to be a root cause analysis done, at least informally, to prevent that from happening in the future (probably resulting in some docs being updated or expanded). Other async tools and channels: bug and issue trackers, kanban boards, wikis, forums, pull/merge requests, version control commit messages, annotation/commenting systems like hypothes.is, even NNTP.