I did user research on an Agile team for a few years. I tagged ALL observations, not just those about any sprint's key questions.
As the product team evolved its focus, I was able to slice and dice my data to answer questions we hadn't yet formally asked.
Each time, I could leapfrog the first study into informed follow-up studies.
In the long run, extra Time Tagging = Time Saved when starting a new product direction.
#UR #UserResearch #tagging #observations #ResearchOps #IxD #Design #agile
I tagged research data over multiple years.
There was an unintended outcome of tagging ALL observations from every Agile sprint—rather than only tagging observations that related to the current sprint's research focus…
As time passed, some of the qualitative data became quantitative as the sample size grew.
#UR #UserResearch #tagging #observations #ResearchOps #IxD #Design #agile #qualitative #QualitativeData #quantitative #QuantitativeData #data #analysis #longitudinal #LongitudinalData #CUA
@Chris There are specialty tools for this.
I used Reframer, by Optimal Workshop. Aurelius is nice, too. There are others. Schedule some free demos.
If you use a tool that has a speech-to-text transcription function, it makes data entry from recordings faster. Tagging takes time, of course. You need a robust set of keywords that cover: your domain and its features, user emotions and attitudes, user-performance tags, and specific UI parts.
Also, ensure any cloud data storage is GDPR compliant.
I loved using #Reframer by Optimal Workshop¹ to reveal trends after tagging. I recently had a demo of Aurelius¹, which transcribes recordings and helps a bit with tagging. There are other tools.
For group use, agree a taxonomy: tags that cover your domain's terminology, current & missing² features, version, specific UI parts², click paths², task performance score², observed user emotions² and attitudes².
¹ Check GDPR if EU data is moved to NZ or US servers.
² Helps reveal insights. ☺️
Jerome
Chris Coleman
skry