Jump to content

Design by committee

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Hayden747 (talk | contribs) at 13:21, 7 July 2009. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Design by committee is a term referring to a style of design and its resultant output when a group of entities comes together to produce something (often the design of technological systems or standards), particularly in the presence of poor and incompetent leadership. The defining characteristics of "design by committee" are needless complexity, internal inconsistency, logical flaws, banality, and the lack of a unifying vision.

The term is especially common in technical parlance, and legitimates the need and general acceptance of a unique systems architect. Often, when software is designed by a committee, the original motivation, specifications and technical criteria take a backseat and poor choices may be made merely to appease the egos of several individual committee members. Such products and standards end up doing too many things or having parts that fit together poorly (because the entities who produced those parts were unaware of each other's requirements for a good fit).

The term is also common in automotive parlance for poorly designed or unpopular cars.[1]

Airbus is gradually becoming more well known for its issues regarding design by committee. It began as a consortium of aerospace manufacturers and it's primary concern is now more about politics than actually producing a product which puts fundamental safety before short term economics.

One maxim is that a camel is a horse designed by committee; this has been attributed to Vogue magazine, July 1958, to Sir Alec Issigonis and also to University of Wisconsin philosophy professor Lester Hunt.[2][3]

Notes

See also