Requirements Gathering by Committee

One of the thing that people talked about when iOS 7 was released, was the ugly icons. Some people thought it was a product of design by comittee.

If you don’t know what that is, it is where the final design of a product was a result of a mix and match of everyone’s idea and execution.

The good thing about it is that you get everyone to contribute to the final product.

The bad thing about it is that you get everyone to contribute to the final product.

When everyone has a say, you will definitely lack consistency.

We think every segment of the business need a clear authority. A leader. Or in this case some sort of Design Director.

Same thing goes with requirements gathering. As much as we believe that a software or a solution needs to solve the customer’s problem, there is still no point in implementing every single feature in a piece of software, hoping that it would solve all the customer’s pain points.

A product manager is clearly needed to make sure that scope creep doesn’t happen.

Don’t get us wrong. We need customer’s feedback. But we also need someone to extract all the core problems out of the pile of complaints from all the customers.

At DK we value our client’s feedback. But we also value the outcome of the project. We want to make sure that the final deliverables solve the real pain points of our clients.

If you are interested in hiring us, give us a call.

Leave a Reply

Your email address will not be published. Required fields are marked *