[Scoble] Everyone who rips us apart, though, does make the book better. In fact, we invited one blogger, Trevor Cook, who had some constructive criticism to write a part of a chapter. That wouldn’t have happened if we had just waited until the end to publish the book. This process is going to be used in products too. You just watch.
I’ll be honest, I haven’t been paying too much attention in keeping up with Scoble and Shel Israel write their book about weblogs, "Naked Conversations" (frankly, it feels like more blogging about blogging), Scoble made a comment that really scares me: "This process is going to be used in products too. You just watch."
Bzzz. Wrong. Sorry Scoble, I have to disagree with you here, big time.
Don’t get me wrong – I’m the first person to fight program managers left and right in order to (coining a term from Kathy Sierra) give users the "I Rule!" feeling, and to make sure that feedback from your users and usability is a part of the design process, but "design by committee" never works when it comes to building software. In fact, it leads to only one thing: feature creep.
Don Norman, author of The Design of Everyday Things has it right (from New Scientist): "You don‚Äôt do good software design by committee. You do it best by having a dictator. From the user‚Äôs point of view, you must have a coherent design philosophy, and I don‚Äôt see how that could come about from open source software. The person who‚Äôs done it best is Steve Jobs, and he‚Äôs well-known for being a tyrant."