PHASE 3: User Test

 Revisit to the previous 'Discord's Date Dash' Project Journal(s):


/ / /

Usability Test #1 (Week 6)

I created a Microsoft Forms to gather feedback during the usability testing phase and managed to involve a total of six participants. The questions were designed based on the tasks I wanted users to complete while testing my project. This structured approach ensured I gathered focused feedback on usability and task completion. This method was efficient and beneficial, allowing me to assess how well users navigated the project and identify areas for improvement. 

Once the data was collected, I tabulated all the the data from the forms and my personal observation of their user test.




Beyond constructive feedback and suggestions, users also highlighted aspects they enjoyed. Some mentioned engaging interactions, while others appreciated the intuitive design. This positive feedback was valuable, as it reaffirmed what worked well in the project. Understanding both strengths and weaknesses helped me refine the experience while maintaining elements that users found enjoyable.

Below is my analysis of some that is considered as main pain points from the participants, and my action plan for each of them:




Originally, the plan was to introduce 5 characters per day, allowing players to interact with a wide range of characters in each session. However, users found this pace overwhelming and felt it might be too much things to read due to dialogue heavy.

Taking this feedback into account, I decided to revise the pacing of the game by reducing the number of characters per day. Instead of five, players will now interact with only three characters per day. This change will make the interactions feel more manageable and less overwhelming.

Below are some of the characters that I will be removing from each categories:



/ / /

Usability Test #2 (Week 12)

For my second usability test, I continued using Microsoft Forms and gathered feedback from six users, in which two of them had participated in the previous test. This allowed me to compare insights from returning users while collecting fresh perspectives from new ones.

This time, I asked users to navigate my project independently without specifying their tasks. This approach tested the intuitiveness of the design and revealed how users naturally interacted with the interface. It was beneficial in identifying usability gaps and ensuring that key features were discoverable without guidance.

Compared to the previous usability test, this time all users successfully completed the tasks without assistance. This was a positive indicator of improved usability. However, there were still areas that could be refined. 




Some users encountered minor confusion in navigating the checklist feature, while others suggested enhancing certain features for better clarity. These insights were crucial in identifying the final adjustments needed to optimize the user experience.

Some mentioned that the sizing of the texts used are a bit too small, however this happened due to prototype not being in a fullscreen window during the test, which affects the text size. Moreover, this project will be displayed on a bigger monitor than a laptop's screen during the gradshow. Hence, I will be not taking this feedback into my action plan.






Below is my analysis of some that is considered as main pain points from the participants, and my action plan for each of them:




Refinements based on these usability test #1 & #2 will be further explain HERE.

Comments

Popular posts from this blog

PHASE 2: Project Prototyping & Development

PHASE 1: Project Research and Pitching

Project Prototyping & Development (Formative)