Overview
Miro is an online whiteboarding tool helping teams collaborate remotely or in person. As part of an immersive UX/UI bootcamp, I was tasked with iterating on the current whiteboard experience.
Lead UX Researcher at Miro, Eduardo Gomez Ruiz, supplied a brief highlighting the challenge Miro faced to remain relevant in the current global climate when facilitating workshops with both hybrid and remote participants.
Role
User research • UX design • UI design • Prototyping • Usability testing
Tools
Miro • Typeform • Figma • Maze
Challenge
It became apparent from my initial research that the current experience of using the app during remote collaboration, provided limited communication methods during meetings which in turn caused a potential lack of connection within the teams.
Solution
User interviews highlighted that limited communication methods made meetings difficult to follow. Therefore, I focused on improving these methods both during and after the sessions.
I added voice and video commenting to help communication during sessions. For post-session I reorganised files in the dashboard adding extra information for edited date, contributors and board type.
Outcome
My proposed solution focussed on staying connected to colleagues by providing a wide range of communication methods to mitigate the limitations of only verbal communication.
The scope of the case study did not include testing my proposed solution. If scope had allowed it, I would liked to have gathered feedback to validate the direction I chose to take.
Discovery
Usability review
I started my research by carrying out a usability review on two screens within Miro — the dashboard and the on-canvas view once a board is created. For comparison a usability review was also carried out in Figjam, Figma's whiteboard tool which is a competitor to Miro.
Questions & Observations
To better define the problems I identified from my usability review, I formed some observations about the app documenting these using the structure [situation], [response], [problem to business or user experience].
Observation No. 1
When [participating in hybrid virtual group work], users [unconsciously prioritise the opinions of those in the room with them], which causes [remote team members to feel like they are disconnected and not listened to
Observation No. 2
When [working remotely as a team], users [lack a means of non verbal communication], which causes [a lack of human connection and miscommunication with colleagues].
Observation No. 3
When [whiteboarding as a team remotely], users [don't know where their focus their attention], which causes [a lack of comprehension and difficulty contributing during meetings].
User interviews
I created an interview script and carried out interviews with representative users of the app to help me ascertain what the core challenges were when using the software and while working remotely. The information from these interviews allowed me to validate my initial thoughts about the app ensuring my hypothesis was being based upon feedback from users.
Interview goal
How do hybrid remote workers feel when collaborating in Miro and what do they feel are the biggest challenges with working with a mix of office and remote workers?
Interview script
Definition
Affinity map
I used annotation software Otter.ai to automatically create a transcript of my user interviews in order to document key insights and observations. These insights were then organised using an affinity map to identify the patterns and trends that would help me form a hypothesis.
Customer Journey Map
A customer journey map was created by combining the data in my affinity map with the observations from my usability review. From this I was able to identify the board creation phase and collaboration stage once a whiteboard had been created as the areas of the customer journey that would provide opportunity for most improvement.
User flow
To further understand the challenge, I created a user flow for creating a new collaborative whiteboard. This helped me clarify specifically where any improvements or simplifications could be made to improve the user experience
Validated observations
Patterns and trends identified in my affinity map and customer journey map helped to validate my earlier observations. By prioritising user frustrations, I had a primary frustration that I selected on the basis of what I felt would provide the greatest user and business gains.
Primary Frustration
When [whiteboarding as a team remotely], users [don't know where their focus their attention], which causes [a lack of comprehension and difficulty contributing during meetings].
Secondary Frustration
When [working remotely as a team], users [lack a means of non verbal communication], which causes [a lack of human connection and miscommunication with colleagues]
When [participating in hybrid virtual group work], users [unconsciously prioritise the opinions of those in the room with them], which causes [remote team members to feel like they are disconnected and not listened to]
How might we statement
Following on from the synthesis of my research and defining what I felt was the primary user frustration, I formed a how might we statement to guide the generation of ideas that I would develop into a final solution.
HMW statment
How might we… help remote teams better communicate with their colleagues when collaborating so they feel more connected.
Development
Scamper
Hypothesis
Once my ideas had been prioritised, I wrote a hypothesis to help frame the problem around user and business goals.
Hypothesis
We believe that [giving users improved means of communicating with their teammates when using the platform [ would help users collaborate better and feel more engaged ], thus [ result in increased satisfaction, connection, and overall adoption of the platform.]
[ ] User goal [ ] Business goal
Delivery
Feedback gained from user interviews highlighted a difficultly in following the flow of a collaborative whiteboard session exacerbated by limited communication methods. To alleviate these problems, I expanded the functionality of the existing commenting tool. In addition to this I didn't want context to then be lost post-session/meeting. I reorganised the UI of the dashboard, adding additional information to files letting users know when a file was edited, its contributors and the board type.
Outcome
As approximately 70% of inter-personal communication is non-verbal my solution focussed on keeping users connected to their colleagues both during and after any collaboration with Miro by providing a variety of non verbal communication methods, including audio and video.
The scope of the case study did not include testing my proposed solution in the limited timeframe available during the bootcamp which this case study was worked on. If further time had been spent on this case study, gathering feedback to validate the direction I chose to take would have been my next activity on the project.