Loading Profile...
Prompting
It'd be nice to be able to show the user instructions to run though, like a list of tasks to complete with the software.
2
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has not planned to implement this.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?While I agree this would be useful for remote testing, it's something the moderator/facilitator would normally do in a regular test situation. As such, I'm not sure it would be of enough benefit to justify complicating the interface and set-up process. What do you think?
-
Inappropriate?Hi Max, Andy,
I think Max's idea would be a great addition to the product. It wouldn't complexify the interface, it would actually be very very helpful for the test user.
When the users clicks the Stop control, he or she would be presented with the list of tasks, where each task would have a Start button.
Say the tasks are set at the project level. The test organizer runs a dozen tests, where each user reads and clicks the active task before groing trough it. In the end, the organizer could choose to view or export all the recordings of Task 1, from all the test users. It would be awesome.
I hope this makes sense.
I’m excited
-
Inappropriate?Yeah, when I'm using Silverback, I like to leave the room, and see if the user can figure out the UI all on their own. I've been prompting them with a TextMate document, but I think you guys could come up with a much more elegant method of doing so. I'm not saying to watch for them to complete an action, just provide them with a list of tasks to complete.
-
-
Inappropriate?It is not a good idea to show the user a list of tasks to complete, because that way the user might feel stress if he/she can't complete the tasks in time. They will also read through all the tasks before starting, which will lead them in a certain way and compromises the test results.
Showing the time it took them to complete a task isn't good either. Because it looks like you are testing the user instead of your application, which is completely the opposite of usability testing.
It is better to show them task by task (or scenario by scenario) and have a facilitator in the room to help in case of issues.
http://www.uie.com/articles/usability...
I’m undecided
1 Comment
Add a comment
This is one of the best points
-
I completely agree. While showing tasks is a necessity for a remote usability tool or an unmoderated session, it's much better to have the moderator in the room with the user to gain the insight directly. As such we prefer to get the moderator to set the tasks. You could of course give the user the tasks on scraps of paper. However you wouldn't want to give them all the tasks up front as this could overload and stress them.
Time to task is a good metric if you're doing quantitate research, but less useful in a guerilla test, which is more qualitative. Time to task is also difficult to interpret unless you know the optimal time to complete the task, and have a baseline to compare the current test subject to. For instance, you need to know if the user is being slow just on this task, or if they are slow in general.
All very interesting ideas though, so keep em coming.
EMPLOYEE
