User Testing

Sprint 2: User Testing

Testing Agenda

The purpose of this session is to help us understand how users utilize our system, which in return enables us to create and perform solutions in designing our system with a higher user satisfaction. We aim to assess and collect feedback from users on the usability of CultureConnect's interface. This test was conducted with five users and follows the process of a typical scenario-based user test. Following the collecting and analyzing of the results of this test, we aim to improve our prototype design in terms of user experience (UX), satisfaction and usability.

The form of this prototype will be through our website.

Date: 15/10/2017

Participants (Users)

Five participants were selected for this user testing session.

Type

International and local students from UQ.

Age Group

18 - 30 years old.

Procedure:

Preparation

The user tests will be conducted in facilitated sessions. This means the user undergoes the test concurrently with the facilitator. The user will not have seen the app before, but is briefed on the app’s purpose and content. The facilitator has precise knowledge of the app but is careful not to affect the user’s behaviour.

The tasks were printed on an A4 paper as a guide for users to avoid any delays. The prototype via our website zone will be prepared prior to the testing session.

Introduction

The participant will be greeted and explained the concept behind CultureConnect. The purpose of the session is explained to the participant and that the session is only for educational purposes only, and that they are able to withdraw at any time if they wish.

Process

The user works through every task in turn, explaining their approach, reasoning and expectations to the facilitator. While the user does this, the facilitator takes notes and prompts the user if any further detail is required. The following paragraphs this methodology in more detail.

Users will be presented with the prototype and asked to perform the following tasks:

• Navigate through the ‘Institution’, ‘Insights’ and ‘Events’ sections in home and communities page (left to right).
• Navigate to the communities page.
• Choose a channel from ‘Institution’ community.
• Sign in with a default username and password.
• Choose a channel from ‘The University of Queensland’ community.
• Choose a channel from the channel selected above.
• Join the channel.
• Type in the chat section.
• Navigate to the communities page.
• Choose any channel.
• Navigate to ‘My Account’.
• Change and save profile settings.
• Log Out.

Once the session starts, users will be monitored while they complete the tasks and the facilitators take down notes and comments of their actions. The participants will be encouraged to 'think aloud'. If users are struggling with a step we will allow them to explain their struggles and then move onto the next step.

Closing

Participants were asked if there were any questions that they would like to ask. Then to end the test, the participants were reminded that their data is confidential, thanked for their participation and escorted out.

Raw Data

Raw Data and Results can be viewed here

Evaluation

The raw data from the user testing was collected, reviewed and analyzed. These evaluations found that:

• 60% of the participants were confused as to why they had to sign in upon viewing the channels in the 'Institution' community. However, after reading the heading 'Sign in for a more personalized experience tailored to your institution.', they understood the purpose of signing in. They also thought that the customized institution feature made their experience in using the prototype feel more personalized.
• 100% of the participants chose to view channels in the 'Insights' and 'Events' community.
• 100% of the users liked the concept of CultureConnect and understood the purpose of it.
• 100% of the users would like to add their own channels in the default communities.

Final Decisions

Based on the results from Sprint 2's user testing session, improvements and additions for the next sprint are as follows:

• Indicate that users have to be signed in for a more personalized experience tailored to their institution on the home/community page.
• Enable users to add their own channel in the default communities.