User Testing - My takeaway
Iterative testing. Getting the customer involved early and often. These key ideas are not only frequently mentioned but thoroughly explained in books about a...
We discussed the research that our group has been working on. Two students are looking through the App Store and Google Play Store for apps and gathering up their desriptions, pricing, app purpose, and reviews. We also have been creating a presentation of screenshots of the apps so we can easily compare their UIs. I’ve been looking at apps that specifically target ADHD (for task management and not symptamatology) and specifically use AI (AI is in the title or description). Another student was scraping Reddit posts to gather information about users with ADHD and write up a collection of user personas.
I was getting the feeling that some of the information was becoming repetitive. I said “I could keep looking at apps and reading more in the book (How to ADHD) but the same themes are coming up. Perhaps I could have stopped sooner, and have all the information I have now”. Just how many apps do you need to analyze before you feel like you have a comprehensive analysis of them?
The professor’s response was that we are “reaching saturation.” I didn’t consider it that way, but when she said that, I was immediately reminded of my Research Methods class. I expressed concern about having enough testers for the app. “Should I start asking now for volunteers to test the app next year?” The professor explained how you don’t actually need that many testers. You get diminishing returns at a certain point.
I asked ChatGPT to give me a picture of the graph I was thinking of so I can visualize this concept. This was the best I could get before I ran out of image creation calls.
It sounds like we are reaching saturation. On Tuesday we should synthesize this information so we can move forward. A student expressed that they would be willing to keep going on with the web scraping but was concerned if we should keep doing that. We don’t want to waste time doing something unnecessary!
I expressed that I like what we’ve got here and I’m looking forward to testing as soon as possible. I was sold on the whole testing early idea in lean and agile methodologies.
Iterative testing. Getting the customer involved early and often. These key ideas are not only frequently mentioned but thoroughly explained in books about a...
It all started with a need. I attend weekly tech meetups and often share event details on Discord with my group. But as the list grew, keeping things organiz...
Eric Ries 2011
Jake Knapp, John Zeratsky, Braden Kowitz 2016
Andrew Stellman & Jennifer Greene 2014
What is this ‘Maker Faire?’
Getting the thoughts out there - using Lucidchart
What’s the least amount of (and most important) features we need to make for the design so that we can start testing?
How do you know when to stop? We discussed the research that our group has been working on. Two students are looking through the App Store and Google Play St...
AI/Tech Coffee Social ☕
Friday Team Meeting #1 - Online edition
Tuesday Team Meeting #2: Getting the hang of it
Monday Meeting #2: Reconvening after our First Full Week of Work
Maja Dakic 2023
Jeff Gothelf & Josh Seiden 2021
John Whalen, PhD. 2019