Getting to what customers really want
Literal voice of the customer does not translate into meaningful inputs. Customer-driven movement has failed to produce the desired results because asking the customer what he wants solicits wrong inputs.
Companies gather requirements however they do this without ever really understanding what types of inputs they need to obtain from customers. Neither does the customer. Customers offer their requirements in a language that is convenient to them but unfortunately not convenient for the creation of breakthrough products.
The web was built around the idea that a client’s job is to request data from a server, and a server’s job is to fulfill those requests. This paradigm went unchallenged for a number of years but with the introduction of AJAX around 2005 many people started to explore the possibilities of making connections between a client and server bidirectional.
As part of any software development effort the age old challenge is to ensure a team working together to create software will meet the expectations of customers or users that will use it. A lot of attention is focused on working software – but what does that really mean. Continue reading