Jell is a desktop and mobile standup meeting alterantive for remote teams. The founders of Jell were working at a software company that was struggling with the challenges of a growing team. They started working on Jell as a side-project to help improve communication and align teams.
Understanding the Product
The usability test was conducted by a team of 4 and we needed to understand who the product was made for and what does it help them accomplish. We set up a Hangouts meeting with Jon Izquierdo, the UX Designer at Jell, to get our questions answered.
Expert Evaluation Insights
The team evaluated the web tool by performing a Cognitive Walkthrough and Heuristic Evaluation individually and then comparing the results to identify the major issues with the tool.
Experience with similar applications
- Have used similar application: 4 (Slack, WebEx, Visual Studio, Asana, Basecamp)
- Never used any such application : 6
Teamwork type experience
- Same location as team members: 7
- Working remotely with teams members: 3
The participants were asked to recall the last/current project they were/are working on with a group and complete the tasks using those details to fill into Jell. The test started from https://jell.com/
Task 1 Sign up for an account with Jell and set a goal for your project.
Task 2 Set a deadline for your goal.
Task 3 Write down the tasks you wish to accomplish today.
Task 4 Write down what you wish to accomplish in the near future.
A pilot test was conducted to ensure that the tasks themselves were easy to understand or if they needed to be explained more in detail or need more context.
Setting a Goal
Setting a Deadline
“It should be under Goals... Yes! under Goals... No, it is not Goals... Frustrating... I think it is Goals.” - P8
8 out of 10 participants completed the task but they experienced a lot of frustration while doing it because of the lack of guidelines and multiple Goal tabs for individual and organization goals that did not have clear differentiation
"What is Q1, Q2, Q3, Q4? Why can't I just set a date with like a calendar pop-up?" - P5
This was the easiest task since it went along the flow of setting a goal but participants expressed their frustration when they weren't able to customize their metrics for completion or deadline date.
Writing what to accompish today
Writing what to accomplish in near future
"Okay, so I think that means my to-do? I'll add this under to-do"
7 out of 10 participants completed this task but most participants first added their tasks to To-do first and then changed it to plans after trying to complete Task 4 and realizing that Plans was the right option.
"Oh wait! It says Post your status, but how is that related to what I'm planning to do? Shouldn't that be what I already did?"
Even with task 4, 7 out of 10 participants completed this task but a different 3 participants didn't complete it. The terminologies used confused participants even though eventually they ended up filling the right information under the right tab.
Post-test Questionnaire Results
1. Confusion with “Plans”, “Goals”, and “To-do”
Nearly half of the participants selected a wrong function when they were supposed to add a plan or a todo. The confusion was present not only between “plans” and “todo” but also between “plans” and “goals”. Since this is part of the main tasks on Jell, it was ranked as a high-priority issue.
Alternative names for “Goals”, “Plans”, and “To-do”
Displaying a brief description of the terms beside their headings or as you hover over them.
2. Lack of feedback
While the system was providing feedback after submitting a form or when having a problem, many participants did not notice the feedback or complained that they did not receive any feedback. The success messages disappear quickly after displaying and the participants did not consider some system actions as feedback. On the other hand, one person was very satisfied with feedback from the system. Lack of feedback even led to loss of data, when participants were adding to either “Plans” or “To-do”, as the data does not save automatically for those two functions and so it was ranked as high priority.
Providing consistent and easy to perceive system feedback, either have submit buttons everywhere or just have users press the enter key and show changes in the UI to indicate that the action has been completed.
3. Confusion with navigation
Some participants were struggling with finding out where they can find a certain function, and they were clicking every menu available in Jell. One participant also stated that it is hard to know what functions they would be able to perform under each menu and the participant would like to have it laid out as sidebars. "It appeared good, design, layout is good but functionality is confusing.”
4. Confusion with team goal and individual goal
Participants entered a team goal when they were supposed to enter an individual goal because they thought it was an individual goal. They also had problem finding out where they can add or view an individual goal.
Integrate all goals under one page, preferably the home page and have clear demarkation for which goal stands for what, with appropriate subheadings, tags or colours.
5. Lack of customizability of deadline or metrics
Some participants did not understand a quarter system. On the other hand, the participants who have worked or are working as developers did not have any problem with setting a deadline by a quarter. For metrics for measuring success of a goal, some participants did not understand how to set such criteria with numbers. They did not understand what the numbers represented.
Alternative way of setting a deadline in “goals”
Since Jell also wants to cater to non-working professionals doing team work, avoiding industry jargons and using widely accepted practices like setting deadline by the date, month and year would help all users.
6. Missing "Goals" in Home Page
Some participants did not realize they can add goals in the home screen because they did not scroll enough to see the whole page.
Keeping all important information above the fold.
User Feedback and Suggestions
What They Liked About Jell
What They Disliked About Jell
Suggestions on existing features
Suggestions on additional features they would like to use
We were unable to test team collaboration
Jell is a team reporting tool, so it is essentially an app that relies on different users interacting with it simultaneously. Unfortunately, we could not test this aspect of the application since we did not find a group ready to spare some time for it. We were only able to test users running through the system individually.
No current users as participants
We only tested first-time users so we got the general first impression of Jell and how users navigate through it the first time they use it. However, we didn’t test what current users are doing with Jell, and if they have any trouble using it.
No Project Managers as participants
Project Managers are a significant target audience for Jell and their functionalities are different. Unfortunately, we were only able to recruit participants who have experience working in teams in an organization and graduate/undergraduate students.
As we communicated the findings to the designer, changes were already being made even as we were conducting usability tests.