I feel like most of these arguments can be made about in person meetings, too. Decision making needs to be documented somewhere regardless of the medium the conversation took place in.
Live chat could maybe be a good place for that to happen but then someone needs to transfer that information into a tool designed for it. Just like you would if you had a meeting in a physical office.
Now if the argument you want to make is that live chat is a bad place for those discussions to be had then that is different. Having worked at multiple fully-remote orgs with team members across many timezones and working different schedules I can agree live chat is not a great place for decision making to happen either.
We use RFCs for async decision making when live chat, zooms, or in-person meetings aren't possible. It is slower since you are often waiting for a response until the next day, but I also find that the waiting time can be quite productive for other tasks and gives everyone more time to think about an issue.
Live chat could maybe be a good place for that to happen but then someone needs to transfer that information into a tool designed for it. Just like you would if you had a meeting in a physical office.
Now if the argument you want to make is that live chat is a bad place for those discussions to be had then that is different. Having worked at multiple fully-remote orgs with team members across many timezones and working different schedules I can agree live chat is not a great place for decision making to happen either.
We use RFCs for async decision making when live chat, zooms, or in-person meetings aren't possible. It is slower since you are often waiting for a response until the next day, but I also find that the waiting time can be quite productive for other tasks and gives everyone more time to think about an issue.