Gathering User Requirements involves a process that uses several different methods and sources to find and collect data. This can be comprised of information from interviews, questionnaires , html"}]' tabindex='0' role='link'>A/B testing and focus groups that will then, in turn, be analyzed along with KPI)" href="http://jumpstartcto.com/defining-your-startup-key-performance-indicator-kpi/">your Key Performance Indicators (KPI’s).
html"}]' tabindex='0' role='link'>Minimum Viable Product" width="600" height="100" class="lazy lazy-hidden alignnone size-full wp-image-833" srcset="" data-srcset="https://d2haskyseezqzi.cloudfront.net/wp-content/uploads/2013/02/gather_requirements600x100.jpg 600w, https://d2haskyseezqzi.cloudfront.net/wp-content/uploads/2013/02/gather_requirements600x100-300x50.jpg 300w" sizes="(max-width: 600px) 100vw, 600px"/>
A common mistake people make is that they tend to treat themselves as one of the users. Like a horses with blinders, we often myopically base what we think the requirements list is, solely on one’s own selfish needs and not on the real and objective needs of the users. The correct way is to first adhere to the process of gathering User Requirements before deciding on what you think those requirements ought to be.
