Avoid Design by Committee : Generate Apart, Evaluate Together

Avoid Design by Committee : Generate Apart, Evaluate Together
▻https://dev.to/lpasqualis/avoid-design-by-committee-generate-apart-evaluate-together-2l00

https://res.cloudinary.com/practicaldev/image/fetch/s--DDuVaDYy--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/xdlu2dgyz0muduuqkpu8.jpg

This post was first published in its entirety on CoderHood as Avoid Design by Committee: Generate Apart, Evaluate Together. CoderHood is a blog dedicated to the human dimension of software engineering.

The tech industry thrives on innovation. Building innovative software products requires constant design and architecture of creative solutions. In that context, I am not a fan of design by committee; in fact, I believe that it is more of a disease than a strategy. It afflicts teams with no leadership or unclear leadership; the process is painful, and the results are abysmal.

Usability issues plague software products designed by committee. Such products look like collections of features stuck together without a unifying vision or a unique feeling; they are like onions, built as a series (...)