Design By Committee
Products and software designed by committee tend to be characterized by needless complexity, internal inconsistency, logical flaws, banality, and the lack of a unifying vision.
"Who needs vision when you have meetings?"
The problem with Design By Committee (DBC) is that typically the result is a compromise arrived at by trying to achieve some consensus and please everybody in the room. It's a classic case of "Too many cooks spoil the soup." Most products that are well-designed have a singularity of purpose and do an excellent job of avoiding Feature Creep. Frequently, maintaining this focus on doing one thing well is accomplished by fending off attempts to co-opt the product's design in various meetings, thus avoiding DBC. This only works when those who have the vision for the product also have the political clout and communication skills to hold their ground against well-meaning peers and supervisors eager to get their input included in the final product.