New answers tagged

1

Simple answer: No. Longer answer: The "Requirements Gathering" stage is not about formulating a solution. It is about gathering together the requirements that any proposed solution must satisfy in order to be considered successful. It's like finding out what kinds of food your friends prefer before you look for a restaurant to book. You can then use ...


1

Term "Gathering" suggests that the requirements are already existing, and one just needs to collect them through some means. I guess user/product requirements also already exist, in that there are several possible solutions to meet what the user's expectations are, and you just need to collect them through some means. A good product is not built ...


0

TL;DR: a UX process should include both needs discovery and requirements gathering Question is possibly a bit leading in that assumes some particular UX process and terminology. The following two questions are a razor that may help crystallise differences in activities: Q. UX is about discovering users needs and satisfying them. Is this the same as ...


1

It is quite accurate description of a process of collecting the things that are needed: requirement (n.): "things required, a need" gathering (n.): "an assembly of people, act of coming together," gather (v.) "unite, agree, assemble; gather, collect, store up" I don't think hypothesis formulation comes anywhere close to convey the true ...


3

At an abstract high level, Requirement Gathering still works, i.e. it doesn't specify how you will gather/discover the requirements nor the process. However, I agree with you that it does not exactly match what we do. I doubt we can come up with an alternative which will go on to become an UX industry terminology.



Top 50 recent answers are included