Tamara Adlin from Fell Swoop ( a UX consulting firm in Seattle, WA) wrote a revelatory article about how important it is to know what problem you are trying to solve . Her client(Client X) was having all sorts of problems with their UI, including an inordinate number of users asking “why can’t I do X with your product”.
Client X asked how they should avoid creating such confusion. Instead of just jumping in to solve the (rather obvious & severe) problems with Client X’s UI, she realized the answer was much more basic: she needed to establish exactly what question their product was trying to answer. What problem was the product/website trying to solve?
Ms. Adlin explained that to properly answer that seemingly simple question you have to figure out: