Comment by zahlman

> listening to the use case, looking for the pain, and finding a way to solve the pain points. As opposed to trying to understand what feature the user wants to request.

... What is the distinction you're drawing here? How is "the feature the user wants to request" (note: not necessarily the feature the user actually requests) different from "the solution to the pain point"? Why would the user want a feature that doesn't alleviate the pain?