@x4nw @nat Kind of relatedly: when I develop something for clients, I always repeatedly emphasize throughout the process that "it can always be changed later, if needed" (and write my code so that that is actually possible).

This seems quite effective at *preventing* bikeshedding, because they don't have the sense that it's "now or never" to get their points made.