My point was that "magnifying issues" is desirable. Fixing issues can't happen unless they are raised. All the teams I work on have weekly retros specifically to magnify issues, and especially to identify issues that might seem too minor to be worth the effort of raising. That is how you can address problems that affect many people a little bit, or that would grow into major problems eventually. Additionally the process of being heard and having people care about your experience builds team camaraderie and cultivates the atmosphere of respect and collaboration I find most productive.
Improvement of culture and process only comes when we're willing to listen to people and take their concerns seriously. Being dismissive of things that bother people is a great way to lose engineers, and also design really shitty products.
Magnifying issues beyond the potential cost of the issue isn't a good idea. Do it too much and you become a disturbance.
Disturbance isn't good. It's a big part of the reason why (aside from legal issues and employee retention) we don't want racism or sexual harassment in a workplace. It causes disturbances. Not because Moses came down from the mountain and said these things are evil.
Improvement of culture and process only comes when we're willing to listen to people and take their concerns seriously. Being dismissive of things that bother people is a great way to lose engineers, and also design really shitty products.