Maze Testing Analysis

I hosted a Maze study that invited users to come test WeCan's onboarding process, including the login, signup and error processes. Here are my findings after concluding the testing.

Maze Analysis:

After hosting my Maze study and encouraging users to navigate through the onboarding process, I am ready to share my results. To start, I had six participants take part in the study and spend time on WeCan. While this number is small, I did do my best to encourage others to take part in usability testing. I understand we live in a busy world and everyone’s time is valuable, so while I was hoping for a higher number of participants, I value each of the ones I received individually and am happy to report my findings from this group size.

The first thing for me to note is that the average time each user spent navigating through the WeCan UI is approximately 65.5 seconds, the shortest being 7.73 seconds and the longest being 207. 7 seconds. I believe there are multiple factors involved in this average number. I do believe the 7.73 seconds may have been a user having technical error or deciding against finishing the testing fully, and I know that happens sometimes. I’ve kept in consideration that users were testing the onboarding flow of WeCan instead of the main source of content. Due to the fact that Onboarding is supposed to be quick and simple, I conclude that the shorter visit times are actually a positive rather than a negative. Users want to get through the tedious tasks quickly so they can enjoy the content, and I believe that is something I showed successfully.

Here is the onboarding screens area where 5 out of 6 users hit skip on the first screen. The heat map shows this tap in the 'skip' area.

Here is the onboarding screens area, where 5 out of 6 users hit skip on the first screen. The heat map shows this tap in the 'skip' area.

This is a brief overlook at how the users navigated through the UI. One user exited the testing when they finished logging in, which is the user that was only testing for 7.73 seconds. Whether or not that was a choice or an accident, they were able to successfully get through the login phase before leaving. Looking at this testing gives me confirmation that onboarding was able to be navigated (or skipped) through and that login was also able to be navigated through successfully. The prototype for both of these actions was built correctly in Figma, informational and easy to understand.

This area is where I believe the design started to show weakness. This is the 'daily quote' page which users are taken to after successfully logging in.

I believe the main issue with this as the landing area is that users are not sure what to do. While our main screen is supposed to be the first thing they see after logging in, I imagine that they are looking at this and saying 'okay, what's next?' Underneath the quote you see the option to like or share the daily quote, but other than that every other feature is at the bottom. From the bottom menu the user is able to go to their personal jots (journal), calm section, settings and other content. I don't believe the ability to do so is as outwardly visible as I had believed, and I think users will need a big more context right from this page to know what to do from here. The bottom navigation does a good job at covering the activities a user can do, but focus needs to be drawn there at least the first time a user logs in.

My suggestion to myself is to take this information, go back and create a method where attention is brought to where the other activities in the app can be found. Instead of a second menu or second options on this screen, I'd like to create a 'tooltip' that pops up and shows the user where they should look next to see more on the app. I imagine this as showing up at least 1 to 3 times when a user logs on for the first time, as they may miss it the very first time. It may help remove that confusion and 'what next' questioning.

This is the idea I plan to propose on how to help make this area stronger and lead users in the correct direction. When logging on for the first 1 to 3 times, the content will fade out long enough for a tooltip to appear, showing the functionality of the bottom bar. It can be easily clicked away as soon as it's read.

This Maze Analysis was only the first of multiple tests we will be doing with users. I am aiming for a higher testing sample on our next, but I do want to acknowledge that I'm grateful for users who did take the time to complete our first run on Maze. I will be updating this page what any new testing that we complete and will continue adding follow-ups as new information is collected and changes are made. Thank you for following our WeCan journey.

Return to Home