Having spend some good time in the Interaction design domain, I have started to think that the term "Requirement Gathering" is somewhat a misnomer and conveys a incorrect image of the process. Is there some agreement? Hear me out -
1) Term "Gathering" suggests that the requirements are already existing, and one just needs to collect them through some means. In most cases, this does not hold true. Product requirements are not gathered, but are formulated based on various sources of information - which could be user interviews, stakeholder views, business goals, market/user/domain research etc.
2) A good product is not built on a document of collected requirements but is rather a hypothesis that one builds and tests. This hypothesis is much more comprehensive and could aim to plant an "USP" which no requirement may define or want explicitly.
So given this line of thought - does it make sense to think that "Requirement Gathering" does not convey the picture the process is about - or am I just the one here?