There is a not so fine line between designing a product people need and one that you need them to need.

Title: Usable yet Useless: Why Every Business Needs Product Discovery
Context: He who would choose to succeed must first understand what success looks like.
Synopsis: There are many different types of complexity that designers face when working on a solution to a brand new problem. We try and manage this complexity of complexities as best we can while simultaneously attempting to crystallize a vision in our heads for where we need to wind up at the end of our process. This is our first mistake. As hard as we try, and as much as we might know better, carts and horses are awful hard to put in chronological order as ideas crash over us soaking us to the bone with brilliant potential. Complexity is rarely addressed in the first 5 minutes, and if you are convinced that it has been, know that you are within wide margins of error 100% wrong. Process is there for a reason. Discovery is the front end of process for an even better reason. You cannot design a solution without first understanding the problem no matter how guru-like and Jedi-ish your skills may be.
Best Bit: “The Lean Startup concept of ‘Minimum Viable Product’ is certainly useful, but shouldn’t we rather focus on Minimum Desirable Products?”

via alistapart.com