I agree that some conflicts are much better handled via synchronous voice conversation. And I think that's acceptable, if not desirable. However, I make sure that after the call we write down some notes what decision we made, and why we decided the way we did. This makes sure that parties not present at the meeting (i.e. other developers, and our future selves) can pick up the context quickly and save us the pain of working through the decision process again.
And then there is always the issue of dysfunctional team communications where the channel doesn't matter. In asynch conversations poor/obstinate communicators don't need everybody in the room to keep adding to a controversial conversation. So you just can't stop them..
And I just learned a new word: 'in·tran·si·gent': unwilling or refusing to change one's views or to agree about something. Thanks.
> more awkward for decision-makers to assert themselves
That has probably more to do with team culture than the communication channel used. I'd think that a capable and respected decision maker can assert themselves easily via written word.