Design by committee is a disparaging term for a project that has many designers involved but no unifying plan or vision.
The term is used to refer to suboptimal traits that such a process may produce as a result of having to compromise between the requirements and viewpoints of the participants, particularly in the presence of poor leadership or poor technical knowledge, such as needless complexity, internal inconsistency, logical flaws, banality, and the lack of a unifying vision. This democratic design process is in contrast to autocratic design, or design by dictator, where the project leader decides on the design. The difference is that in an autocratic style, members of the organizations are not included and the final outcome is the responsibility of the leader.
The term is especially common in technical parlance; it legitimizes the need and general acceptance of a unique systems architect and stresses the need for technical quality over political feasibility.
An example of a technical decision said to be a typical result of design by committee is the Asynchronous Transfer Mode (ATM) cell size of 53 bytes. The choice of 53 bytes was political rather than technical. When the CCITT was standardizing ATM, parties from the United States wanted a 64-byte payload. Parties from Europe wanted 32-byte payloads. Most of the European parties eventually came around to the arguments made by the Americans, but France and a few others held out for a shorter cell length of 32 bytes. A 53-byte size (48 bytes plus 5 byte header) was the compromise chosen.
The term is also common in other fields of design such as graphic design, architecture or industrial design. In automotive design, this process is often blamed for unpopular or poorly designed cars.
One maxim is that a camel is a horse designed by committee; this phrase has appeared in use in the United States as early as the 1950s.