Summer Milestone 8 TeamTrojans

From crowdresearch
Jump to: navigation, search


Users

Usability test was performed on :

1. A 35 year old female who has prior turking experience. She was a member of Mechanical Turk.

2. A 25 year old male who has no prior experience of crowdsourcing.

Task Description

1. The first user chose a task of proofreading/editing a paragraph.

2. The second user chose a task of translating a document.


Observations

The following observations were made based on user experiences:

Login Page:

1) Username and password fields must have labels.

2) The placeholders on username and password fields must disappear on user inputs.

3) The Create Account button must be placed below or in the vicinity of the Sign In button

4) There must be a Forgot password button to aid users recover passwords

5) After Sign Up users must be automatically logged in without requiring them to sign in again


Create Project


Project Category

1) Progress Bar : Users expected the 6 sub task headings at the top as a progress bar. The points can be presented as a bulleted sub list when a user clicks on “Create project”. A progress bar, instead, can be provided at the top.

2) “Other” checkbox : A textbox must appear on selecting the “other” option to allow users to specify the Project Category. Also, on selecting “other”, the remaining options must be disabled.

Project Details

1) “Summarize your end goals” textbox: The textbox has no validation regarding the number of allowed characters. Also, the cursor placement is not aligned with the text box placement. Instead, users can be provided with a text area with a predefined number of rows and columns to restrict the user input. Rephrase the radio button options for better user understandability.

Milestones

1) The message on top repels users.Users would not want to read so much information. The text can be minimized to include only the first paragraph and exclude the examples.

2) “What do you expect from this milestone?” : The textbox has no validation regarding the number of allowed characters. Also, the cursor placement is not aligned with the text box placement. Instead, users can be provided with a text area with a predefined number of rows and columns to restrict the user input.

3) “Google Drive” and “No spreadsheet, use my own webpage” radio buttons : The two options are similar except for the URL. They can be combined into one option. Also, the text boxes that appear on an option selection clutter the screen. These options must appear at the end of the radio buttons in a consistent fashion so as to not confuse the user. The URL field lacks validation and the placeholders must disappear on user input rather than moving on top and turning blue.

4) “Amount of time a worker should spend to finish the task” : The field must be a numeric input type with unit options.

5) The message that appears at the end regarding “NEXT” button must appear on all pages or appear on none.

Design Task

1) The way users are allowed to edit widgets are obfuscate and not consistent. Users tend to remain confused regarding the various options available on “Properties” tab.

2) Allow users to edit widgets by double clicking on the screen rather than having the “Properties ” tab.

Payment

1) “How many different people should do the prototype task?”: The field must be a numeric input type with unit options rather than a plain text box.

2) “How much will you pay per task ?” and “Service Fee” fields : The field must be a numeric input type with unit options rather than a plain text box. Also, the currency type must be specified, if applicable.

3) There is no mention regarding the required and optional fields. Instead, a “Please fill fields above” error message appears in an odd position on the screen.

4) There is a “Payment” word that appears without any functionality.

5) There must be a mechanism to collect payment information, such as

   Method of payment
   Card details/Bank account details from users.

Summary

1) The dollar symbol appears without a default price value.

2) The Submit button is placed inconsistently with respect to the remaining pages with a completely different design and layout.


In addition to the above points, some general observations were made:

1) The “Back” button should be designed consistently with respect to the “Next” button. the positions of the “Back” and the “Next” buttons are not consistent.

2) Some of the input fields show the “This field is required” message by default. Instead, an asterisk must be used to indicate necessary and optional fields with display of error messages when necessary after submission.

3) The “Milestones” and “Design Task” pages have a lot of navigation bars that can be avoided with efficient space utilization.

4) No page has a RESET button nor a SAVE button to save entered information temporarily.

5) The textbox for “Title ” in comparison with “Summarize your end goals” is very small. All text boxes must be of equal length.

6) There must be a CANCEL button at the “Summary” page.