I tested my prototype at a stage where I was happy with all of the features and the way the screens looked, but still had time to make changes before the final submission.
This was the team page that I used as the main workspace. At this point in wireframing, I wasn’t sure whether to keep labels on the widgets or not, so I used the version without labels to see if the user would be confused at all or understand the purpose of each widget within that team.
However, when presenting this to the user they did express confusion and weren’t sure what the widgets were immediately, therefore I realised that the variation with labels would be the most user-friendly and intuitive, the user will know what the widget is straight away and not have to wonder. This will be particularly useful for the older range of the target audience.
The action that I asked the user to undertake was checking for any updates from the team within the team screen, this would entail checking messages, calls, files and the workspace for any changes within the widgets.
The user managed to find the chat and call screens very easily and had no issue navigating within those, however they seemed confused at the lack of activity on the workspace, as I had no exmaples of users utilising the widgets.
This is something I will change for the next and final set of wireframes, I will add examples of widgets in use by the users in the team.
I also asked the user to change between teams and back again to see if that interaction was intuitive.
I observed that the user spent a bit of time looking for how to do this, after eventually finding the arrow beside the “team 1” title at the top of the page with some guidance. This is a clear indicator that this needs to be altered in a way to increase efficiency for new users, and make it faster for everyday users too.
I asked the user to also carry out some some tasks one after the other to see if they were easy to figure out or if I needed to alter the experience.
These included-