I don't think I disagree, so this is perhaps a devil's advocate argument--to the extent a product is meant for somewhat general use, by integrating more perspectives during development, we might uncover blind spots and innovate in ways that resonate more deeply with their core audience, not less. Asking, “Whose needs might we be overlooking?” could be useful not because every minority requires a bespoke solution, but because overlooking them might mean missing opportunities to serve even the majority better.

From anecdotal experience with voice recognition software: early versions struggled with accents and also required training on your voice specifically, which limited their utility. Making models more flexible didn’t just help minority users with accents—I think it improved accuracy for everyone. Similarly, curb cuts on sidewalks, originally designed for accessibility users, now benefit parents with strollers and even those food delivery robots running around some cities.

Maybe one frame is to avoid unintentional exclusion? The pizza shop isn't obligated to, but could at least consider the fact that some people don't eat meat (or pork or whatever), and therefore keep the margherita on the menu to the benefit of everyone.

I agree that it's impossible to build a product that satisfies everyone, which is the issue with global tech companies. In my utopian world, we would educate people and develop tools so that communities can build their own tools to cater to their own needs (in the same spirit as unix). I think that's better than what we have today with technocrats in Silicon valley dictating how tech should look and function for the rest of the world.