I'll add that global/fully async remote work is even more merciless, especially on Agile figuring-it-out-as-we-go-along orgs. Communication has to be written and clear enough to avoid back-and-forth, changes are possible on the order of a day, not an hour so planning ahead and evaluating critical paths is more important, and everyone has to be able to pick up and put down work that's become blocked by someone on the other side of the planet. It's a tall order, but I'd like to think that the benefits are worth it for both individual and company.
I recognize past experiences in what you describe - but here's the punchline:
Working for a completely on-site company located in two buildings within 10 minutes' walking distance, it was still sometimes impossible to get hold of some people, or understand their attempts to communicate without going back-and-forth 3-4 times.
I think the company I'm thinking of is simply also a "winner of remote work" because it already managed to survive despite massive mismanagement and miscommunication before remote work.
Another comment pointed out that shared time zone "remote working mercilessly exposes some of the flaws in the organization." (https://news.ycombinator.com/item?id=28369657)
I'll add that global/fully async remote work is even more merciless, especially on Agile figuring-it-out-as-we-go-along orgs. Communication has to be written and clear enough to avoid back-and-forth, changes are possible on the order of a day, not an hour so planning ahead and evaluating critical paths is more important, and everyone has to be able to pick up and put down work that's become blocked by someone on the other side of the planet. It's a tall order, but I'd like to think that the benefits are worth it for both individual and company.