Good stuff. This advice can actually be applied to any generic software development area and not just web. Let me explain. I work with clients who can be technically savvy and when we start a project, instead of discussing "what is the need", they would go into "I need an excel macro that can pull this xyz data from abc source and do blah". I tell them "Sure that could be a way to address your need BUT what is your need again ? I need to understand what it is that you are looking for rather than getting into the how. Once we have clarity on the what, I am more than happy to discuss some of the hows or the implementation details".
Comments
Good stuff. This advice can actually be applied to any generic software development area and not just web. Let me explain. I work with clients who can be technically savvy and when we start a project, instead of discussing "what is the need", they would go into "I need an excel macro that can pull this xyz data from abc source and do blah". I tell them "Sure that could be a way to address your need BUT what is your need again ? I need to understand what it is that you are looking for rather than getting into the how. Once we have clarity on the what, I am more than happy to discuss some of the hows or the implementation details".