Author here, happy to see some discussion around this. I see two major classes of comments. 1. “Why not accomplish this with X?” We arrived at this solution or

Author here, happy to see some discussion around this. I see two major classes of comments. 1. “Why not accomplish this with X?” We arrived at this solution organically, which was important for adoption: a Discord server meant for gaming hour turned into hangout rooms turned into offices. It may not be the best option, but best means nil if you can’t convince people to use it. For us and our existing culture, Discord was an easy and incremental jump to take. Take whatever path makes sense for your culture. 2. “Why not make this asynchronous?” Asynchrony should indeed be the default mode of communication, but synchrony has its uses; between nonverbal communication and round-trip-time it is simply obnoxiously higher bandwidth. It trades away efficiency (person-hours) for speed (hours). The fewer people involved the better the exchange rate, which is why this article focuses on 1:1 interactions. I wrote about this later in my article “Why Be Synchronous?” [1] but tldr; synchrony should be deployed similarly to tech debt. [1]: https://twos.dev/async.html https://twos.dev/async.html