How is this for controversial? Diversity of ideas and experience could also be interpreted as lack of direction. In truth, "ideas and experience" could cover anything from cultural issues to technical issues. However, I'll point out some ways that "diversity in ideas an experience" could be interpreted, just so you get a feeling for why someone might object to a non-specific label like that.

Elsewhere in the thread, people are talking about excessive drinking on the job contributing to harassment. In the culture where I currently live (Japan), drinking is virtually mandatory. In fact, I once got an official reprimand for not drinking at a company event. Within the Japanese culture, drinking allows you to relax the way your present yourself. If you are drunk, it is acceptable to clearly say what you think, even if it might be embarrassing for others. This may be the only time to provide feedback up the ladder. Additionally, people higher up in the organisation are allowed to be more familiar with those lower down, which is impossible in normal every day work. This develops an honest camaraderie up and down the organisation and without the social lubricant (or excuse is probably a better word) that is alcohol, the work culture suffers.

Now, perhaps we have several Japanese people who have experienced significant success with this corporate culture. Do we want to grant it a kind of equivalent status within our organisation? Or do we want to have a kind of veto that says, "Despite your previous experience and your cultural background, this is a no-go area for our organisation"?

Even when talking about technical rather than cultural issues, there may be times when we need to limit discussion. I may have hired someone with extensive C++ experience into my Ruby on Rails team. Having that experience is really valuable. The C++ programmer can see things from different perspectives and provide solutions that are different that what the average Rails developer has seen before. However, if the C++ programmer suddenly starts demanding that all string processing should be handled in C++, we might want to limit this discussion. The C++ programmer may have lots of wonderful tools and experience to help them with this task, but the bulk of the developers on the team are not going to be able to cope. Potentially every developer on the team has some niche thing that they would like to introduce. Do we really want to provide a stage for all of these ideas, or do we want to filter them first and work on the ideas that seem most compatible with the team?

It is entirely possible that you disagree with my standpoint. I certainly have met a few people who feel that giving every person in the company an equal opportunity to pursue all of their ideas is a good idea. I have not experienced a successful company that embraced that philosophy, however. Leadership is often about focusing on a few ideas and limiting discussion that appear to be going in incompatible directions. As much as I am frustrated when my ideas get shot down without much air time, I recognise the reality of this necessity.

It's also possible that you have a completely different point that you are hoping to make and it was lost on me due to the brevity of your comment. In that case, perhaps it would be better to try to explain your position in more detail.