Proposing uncoordinated action makes no sense unless you basically deny the nature of the problem, which means you can't solve it. Workable solutions will be sidelined for as long as possible in favor of appealing fantasies.
The effect of uncoordinated action on the problem may be fine, but treating it as part of the solution space on par with actual solutions is not.
e.g.:
Alice and Bob are on a team of 10 developers. Code quality is terrible. It's obvious to Meg, the manager, that something must be done before the product totally collapses.
The other 8 developers don't care. Not only that: they actively refuse to even contemplate why quality might matter, and also each of them has different, mutually exclusive, horrifyingly destructive preferences.
Carol only uses `switch`, not `if`. Dave removes "unnecessary" object allocations (all of them) because GC pressure. Eve's editor replaces every single space with tab on save.
So Bob takes Meg aside and says the team needs training. If everyone who militantly does not care and actively refuses to cooperate could just be shown the error of their ways, he says, we surely could accept a style guide everyone would follow. Training will cure obstinance and apathy with minimal investment.
Later, Alice goes to Meg and says we need a git hook that enforces linting and, actually, a CI pipeline wouldn't hurt.
I don't know, says Meg. That sounds like it would slow us down. And setting all that up could be a lot of work. Bob says we can solve it with a couple trainings and a lot less effort.
So they go with Bob's solution, with predictable results, because Meg likes it better. If everyone who cannot possibly agree would just agree, she reasons, there would be no need for major changes.
Why can't they just agree?