Agile was intended to address the problem of waterfall software development: delivering the wrong thing too late.
When "Agile" teams only want to code something once – no acceptance that usability testing might reveal a failing that necessitates another iteration – it's just more waterfall development with Agile-flavoured rituals and ceremonies.
I've recently seen a KPI used called "First Time Right" to measure the ratio of dev tickets needing re-work, as if that is inheritly a bad thing.
Born of good intentions, I'm sure, but given the trends of that KPI, it wasn't helping.
What DID help was to connect the users and devs so they could talk to one another and gain a shared understanding of what problem needed to be solved. It is disheartening to see how we STILL struggle with basic issues like this.
@FiveSketches How did you store it all? I’ve been piling up Google drive folders with a bunch of reports, but I really don’t know how I’d effectively find and reference anything in there to answer future questions.
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.
Qwerty keyboards are laid out to keep the arms of a mechanical typewriter from hitting each other as you type, because letters that are more commonly used side by side are farther apart on the "keyboard".
Thumb typing has different constraints. There's probably a case for a different keyboard layout, now, to reduce common typos.
Who would research new layouts and the demand? One of the O/S publishers?