Uploader User Testing Results & Redesign

Allison Bloodworth abloodworth at berkeley.edu
Wed Aug 13 23:05:17 UTC 2008


I'd suggest creating a dependent JIRA task to tackle the "what we  
didn't have time to discuss" section after we've gone through steps  
1-3 in "What to do next" section below (assuming we have tasks entered  
for them as well). I think it's quite possible that the personas and  
scenarios could inform those design decisions we didn't yet discuss.  
Unless there's a reason we need to make decisions sooner?

On Aug 13, 2008, at 3:32 PM, Daphne Ogle wrote:

> Thanks for sending this out Erin!
>
> I wonder if there's anything we can discuss and agree on a plan  
> forward in the "what we didn't have time to discuss" section?
>
> -Daphne
>
> On Aug 12, 2008, at 2:35 PM, Erin Yu wrote:
>
>> Hi everyone,
>>
>> Thanks for attending and sharing your thoughts. 	
>>
>>
>> Here's what we discussed in our meeting today:
>>
>> 	Issue #1: Pause
>>
>> 	Solution 1: 	Make Pause more prominent
>> Simpler to implement
>> grey tablecloth vs. greying out individual controls
>>
>> 	Solution 2: 	Remove Pause button
>> The user will feel like s/he is racing against the interface.
>> People didn't see pause button / no one bothered to use it.
>> Pause button wasn't intuitive
>>
>> 	
>> 	Reasoning for Pause
>> Provide a way for the users to stop the progress of upload
>> Help with technical challenge
>>
>> 	
>> 	Cancel
>> Use case:  Upload is taking too long (large files or many files).  
>> User has to go and just wants to stop the entire task, "I'll come  
>> back to it later."
>> Cancel can only be handled by a temporary file storage with no  
>> control over it from the front end.
>>
>>
>> 	Discussions around simple vs. more complicated uploader
>> A simple uploader would allow users to upload smaller files quickly  
>> with less options
>> A comprehensive uploader allows users to stop the upload, add/  
>> remove files during the upload, and cancel the upload
>> 	
>>
>> 	Scenarios for Uploader
>> Create the list of primary scenarios we want to support
>> Determine pain points from the simple old file upload
>> Review existing scenarios from image gallery (need to find)
>> Determine what the 80 is in the 80/20 rule
>>
>>
>> Here's what we didn't have time to discuss:
>>
>> Progress bar
>> Should there be one total progress bar only?
>> Should there be another progress indicator in case the progress bar  
>> is stuck?
>> Information on upload
>> How much information should be displayed during and after the  
>> upload? # of files uploaded, # of files successfully uploaded, # of  
>> files with errors, etc.
>> Error messages
>> If a file fails to upload, should the error message show up within  
>> the Uploader?
>> More on this page: http://wiki.fluidproject.org/display/fluid/Uploader+Design+Improvements+Based+on+User+Testing
>>
>>
>> Here's what to do next:
>>
>> Review personas, use cases, and scenarios for the Uploader
>> Review the results from our user research
>> Determine what persona and scenarios to support primarily
>> Modify design to support the primary scenario
>>
>>
>> Thanks,
>> Erin
>>
>>
>> On 8-Aug-08, at 7:36 PM, Chong, John wrote:
>>
>>> Hi all,
>>>
>>> Actually I am in the process of adding mine so what you see is not  
>>> yet complete. My intent is to fold my results into the page:
>>>
>>> http://wiki.fluidproject.org/display/fluid/File+Uploader+User+Testing+-+Round+2+Results 
>>>  by Tuesday.
>>>
>>> Cheers,
>>>
>>> John Chong
>>> Web Design and Usability Specialist
>>> UBC | Information Technology
>>> 604-822-3395
>>> jchong at exchange.ubc.ca
>>> From: Allison Bloodworth [mailto:abloodworth at berkeley.edu]
>>> Sent: August 8, 2008 4:33 PM
>>> To: Paul Zablosky
>>> Cc: Erin Yu; Chong, John; fluid-work
>>> Subject: Re: Uploader User Testing Results & Redesign
>>>
>>> Hi folks,
>>>
>>> I believe all the Berkeley & Toronto results from the User Testing  
>>> are available at this page: http://wiki.fluidproject.org/display/fluid/File+Uploader+User+Testing+-+Round+2+Results 
>>>  as I've added mine. I see John has posted his results here: http://wiki.fluidproject.org/display/fluid/File+Uploader+User+Testing+-+Round+2+Results+JC 
>>>  so we will probably all want to do a quick review of all of them  
>>> prior to the meeting.
>>>
>>> Cheers,
>>> Allison
>>>
>>> On Aug 8, 2008, at 11:47 AM, Paul Zablosky wrote:
>>>
>>>
>>> Erin,
>>>     That time works for John and me as well.  See you there.
>>> Paul
>>>
>>> Erin Yu wrote:
>>> Hi,
>>>
>>> We''re in the process of documenting the findings and  
>>> recommendations from the Uploader user testing:
>>> http://wiki.fluidproject.org/display/fluid/File+Uploader+User+Testing+-+Round+2+Results
>>> (John at UBC: Feel free to add to this page, so all of our results  
>>> are in one place. Once we do another design iteration and another  
>>> set of user testing, we'll make use of the Round 3 page you've  
>>> created. :)
>>>
>>> It would be great if those of us who sat with the users and anyone  
>>> else interested could meet early next week to discuss the findings  
>>> and ideas for improvements.
>>>
>>>
>>> Here's an overview of the main issues we collectively discovered:
>>>
>>> 1) Discovering multiple upload: We could put a simple text such as  
>>> "Select multiple" to let the users know it's possible. Full  
>>> instructions on how to select multiple files can be included.
>>>
>>> 2) Pause: It is a stretch to expect users to Pause before adding  
>>> ore removing files to/from the upload queue. There are a few  
>>> suggestions regarding this one.
>>>
>>> 3) Progress bar: Some users found the individual progress bar AND  
>>> the total progress bar confusing.
>>>
>>> 4) Errors: If upload is unsuccessful, we display a warning message  
>>> but don't allow users to take any actions. Instead of displaying  
>>> the warning sign and no options to take any actions, we could  
>>> provide [Try again] and [Remove] buttons.
>>>
>>>
>>> How does next Tuesday at 2pm EST/ 11am PST sound for everyone?
>>>
>>> Erin
>>>
>>>
>>> _______________________________________________
>>> fluid-work mailing list
>>> fluid-work at fluidproject.org
>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>>
>>>
>>> _______________________________________________
>>> fluid-work mailing list
>>> fluid-work at fluidproject.org
>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>>
>>> Allison Bloodworth
>>> Senior User Interaction Designer
>>> Educational Technology Services
>>> University of California, Berkeley
>>> (415) 377-8243
>>> abloodworth at berkeley.edu
>>>
>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> fluid-work mailing list
>> fluid-work at fluidproject.org
>> http://fluidproject.org/mailman/listinfo/fluid-work
>
> Daphne Ogle
> Senior Interaction Designer
> University of California, Berkeley
> Educational Technology Services
> daphne at media.berkeley.edu
> cell (510)847-0308
>
>
>
> _______________________________________________
> fluid-work mailing list
> fluid-work at fluidproject.org
> http://fluidproject.org/mailman/listinfo/fluid-work

Allison Bloodworth
Senior User Interaction Designer
Educational Technology Services
University of California, Berkeley
(415) 377-8243
abloodworth at berkeley.edu




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20080813/1179ee35/attachment.html>


More information about the fluid-work mailing list