Agile UX Research Sprint

Incorporating Agile into a user research sprint is a powerful method to be a team player within a product setting (and often in agencies). As mentioned above though, this is not a one-size-fits-all approach, there are dependencies. The combined table and flowchart below gets into the details of my approach in a user research sprint, detailing each stage's goals, key points, and relevant tools. It showcases a systematic approach to planning, conducting, analyzing, and sharing research findings with the product team while emphasizing collaboration and adapting to project needs. The sections that follow this table explain the methodologies behind the following methods:

The diagram I employ above is a cohesive, temporal orchestration of different methodologies, akin to a user journey map. However, there are important caveats to the above diagram and assumptions that were knowingly made when it was created. Specifically, card sorts, tree tests, concept research, UX Research Strategy creation and creating a User Research Playbook are activities that do not fall neatly into one sprint. These would be more like epics in an agile model and consist of multiple sprints (and would each require their own diagram as above). Also, the above sprint would be done at two weeks (or more). While it can be done faster, its not recommended.

During the UX research exercise phase, I employ a combination of qualitative and quantitative methods to ensure a comprehensive understanding of the user:

All findings and insights are stored in an insight repository or cloud storage like Google Drive or a SQL Relational Database for easy access and sharing.