| ??? 12/01/10 13:28 Read: times |
#179798 - Don't (necessarily) blame the customers! Responding to: ???'s previous message |
Erik Malund said:
I have no doubt most of us have been through making a very good program description based on the customers requirement, having it accepted, and then when showing the proto hearing "that is not what I wanted". Did you not read Per's excellent note on this? Per Westermark said:
Designing initially for "optimum" can only be done when you can be 100% sure that you know everything. That is easy for a lamp timer. But for a large number of niches, you can't get the required customer feedback until the customers have been allowed to play with prototype units. The customers just can't visualize the product, so they can't describe what they consider important features to make your product stand out. And the developer often have completely different views of the product, so the developers can't switch hat and pretend to be a potential customer. Especially if the product is intended for users who are not too interested in technology, where there are a very big gap between developers and customers in expectations and way to use the product.
http://www.8052.com/forumchat/read/179792 http://www.8052.com/forumchat/read/179790 Very often it is simply not possible for someone to visualise exactly what they really need without being able to actually experience something in the real context/environment of the application. |
