Run an unmoderated usability test on Userlytics to validate the some of the UX updates proposed as part of the Scope Iteration 2 FY24/25 tickets in this Epic.

Goal

The goal of this test is to ensure that the new options/copy in the release right steps meets the following criteria:

• Help uploaders understand what constitutes as own work and what as not own work and make the correct choice as a result so that the changes to be proposed in T370103 are validated
• Help uploaders understand the process required for uploading on behalf of someone else so that the changes to be proposed in T370106 are validated

• Work on design solutions to test
• Construct the tasks and activitites for the test
• Set up test on Userlytics
• Watch recordings and review results
• Repeat the above steps until satisfactory test results are achieved
• Summarize results

Methodology:

30+ unmoderated tests were conducted on Userlytics. Designs were revised multiple times during the course of a test, incrementally improving them based on what was observed in the test. Participants were given the following 4 scenarios for uploading photos to Commons and asked to follow the Figma prototype.

• Scenario 1: Upload a photo they took of their collection of Asian magazines with beautiful cover design. Example photo
• Scenario 2: Upload a photo they took on their travels. Example photo
• Scenario 3: Upload a photo of the interior of the hotel that their employer gave them to upload. Example photo
• Scenario 4: Upload a logo so that it can be used on the wikipedia page. Example photo

Test results

Own vs Not own work

The present design for choosing own work and not own work had the following issues:

• Users not choosing the correct option at this level led them to incorrect path right from the start e.g. in a scenario where someone was uploading on behalf of someone else would think it is their own work because they are doing the work of uploading or doing it as part of their work/job.
• The examples do not cover all the use cases and many people do not read extra text.
• The introductory explanation was not emphasizing that anyone on internet or off internet can use it, not just on wikipedia as some would believe.

• The above changes to the copy for the “own work” and “not own work”, greatly improved participants selecting the right option at the start and as a results were shown the right questions that further clarified things for them.

Uploading on someone else’s behalf

• The present approach does not accommodate the use case that was discovered in one of the research i.e. users uploading a photo on behalf of someone else
• Also, while the present design is an improvement over what was, user’s do not understand this question that well due to their lack of knowledge on what creative commons license is. They assume this is something legal they don’t know and they end up choosing “I do not have this information” and decide to not upload. It is good that they chose to not upload, however, we lose an opportunity to educate users on this step.

• The new copy seems more educational because people understand what is being asked for and why. When the new scenario of uploading on someone else’s behalf was presented, everyone who saw this question, correctly chose “I have permission option...”

• The warning that was shown upon selection of that option, was understood by most people and stopped them from proceeding without getting the consent.
• Some users who decided to proceed despite the warning, had either chosen to not read the warning or did not understand it clearly due to the UI not in their native language in the test.
• However, based on the results, the introduction of this option should greatly reduce the number of uploads without VRT verification.

Other findings

• There were cases where people assumed that things like magazines and logos are free to share and confidently chose a public domain option.
  • People in some countries may have a very different mindset of what is allowed to share…the concept of copyright may not be very prevalent and they may feel confident in their assumptions of what is free to share.
  • For what we can do in the UI, one of the assumption is that "public" in public domain is misinterpreted as anything available to public as also found in previous test. Reverting to copy similar to what is used presently plus adding examples may help clarify things.
    
  • We may not be able to prevent this for all cases, however, we can flag such uploads if the user has not provided any concrete information e.g. if they indicate having found this on internet without providing any evidence of why its in public domain.
• There were also a few instances of people assigning a randomly chosen free license under “not own work”. Adding “I don’t know” option among the list of license proved to be a good addition at allowing people to indicate the correct information rather than choosing a random license.