Overall the pilot went very, very well. It look just under 50 minutes and the participant was able to complete all tasks. I got some great feedback about changing some of the wording and breaking up one of the tasks into two tasks. I found some broken hotspots within the prototype as well. Most importantly, I discovered an entire interaction missing from the prototype, as demonstrated by the video. I went back and created a way for participants to be able to use either the folder tree or the folder grid when attempting to select a single content item. Since I proposed to allow users to navigate folders and channels using the folder grid, that needs to be functional from the beginning screen of this task—it will be valuable to see how many users choose to use the tree versus the grid upon first being presented with this picker layout. I can't believe I almost didn't include that! (Participants could hide the tree in order to use the grid as I explain in the video, but that will not give me the testing data I need in the most accurate way.)
My prototype is up to 116 screens :/ I just didn't realize the differences in doing true interaction design for a piece of software versus wireframing for a website—I'm learning that these are two unique tasks with their own separate needs so I am glad for the experience. I still might make another tweak to my overall design again based on the pilot. I haven't decided whether a single click to a folder in the tree should display the contents of that folder in the grid, or if that should remain a double-click.
I've scheduled most of my test participants over the coming weeks, starting with two iSchool students next week followed by two OpenText employees the week after. Following that initial round of testing, I will make adjustments to the test plan and prototype before conducting tests with real OpenText customers the last week of March.
Another great video, very helpful! One thing I don't understand from your post is why a delay due to streaming of remote testing translates into you not getting everything. Don't you get everything, but just delayed? Anyway, not that important, but just a stumble for me. Looks like you are still learning in leaps and bounds. Nice job!
ReplyDeleteIt's not just delayed but the video feed actually loses frames because the screen can't refresh fast enough when quick movements are made; for instance if you were trying to distinguish between a user single or double-clicking a link. I think I found a program that might overcome that issue. It also shouldn't be an issue if I can run the prototype locally and allow the participants to control my screen, but then they will experience frame loss which could be frustrating.
Delete