metaUsable is a site dedicated to learning and sharing about designing for experiences.
Many organizations consider quantitative data to be clear and conclusive. Making decisions based on quant data is considered a best practice that organizations either follow or aspire to follow. While in many cases it is better than guesses and hunches, it simply does not tell you the whole story. Despite how much quantitative data you are capturing, you will still not have a full enough picture to make better product decisions. Relying only on quantitative data can ruin the experience as quickly as not using any data at all.
This is a high level diagram I created for use in communicating to stakeholders, project managers, and development teams how Product Experience Design and Research activities fit into an overall product / development process
Any User-Centered process is going to have
Discovery, Design, and Development phases as part of the cycle
There are many diagrams around the digital product design process that have been created over the last decade or more. There is the double diamond of the Design Thinking and the recent UX & Agile diagram by Jeff Gothelf. However, none of them really captured the entire cycle that ties previous development which is often the source or a starting point for new development.
Below is a pdf with details on design and research activities that might be used in each phase.
Download the Detailed Product Experience Design & Research Cycle PDF