Some workflows require synchronous communications. Meetings, in person or virtual, are great for these.<p>Other workflows work asynchronously. E-mail, IM and the like are great for these.<p>Post-War America erred on the side of meetings, forcing asynchronous flows into artificial bottlenecks. Silicon Valley seems to have over-corrected, replacing ten-minute meetings with full-day Slack threads.<p>Trying to force asynchronous flows into synchronous constructs introduces unnecessary delays, as the slowest process sets the pace. It also increases overhead, since resource C is occupied while A and B sync. Trying to force synchronous flows into asynchronous constructs introduces mistakes through mis-communications. It also increases overhead, since an additional layer of verifying everyone got critical information is introduced.