Dean Heasman Tassomai Case Study Header.

tassomai

tassomai

Timeline

4 weeks, Winter 2019

Role

Senior Product Designer

an intelligent multiple choice learning app for students 

Tassomai is an intelligent online learning program helping students at all levels achieve outstanding results. Tassomai builds knowledge, boosts confidence and reduces exam stress via daily multiple-choice questions.

The challenge

Every day is a school day

Tassomai has always allowed students to see how many correct questions they have to answer each day. Our goal was to create an experience which would allow students to see their goals (homework) for a given day and week, for a given subject and across multiple subjects and for them to know when this was due.

My Role

I was senior product designer at Tassomai between Feburary 2019 and February 2020. I Ied the UX, UI, visual design and branding during this time. In regards to this particular feature, I delivered all research and design assets.

dean-heasman-tassomai-quiz-view-image.pn
dean-heasman-tassomai-daily-goals-image.
dean-heasman-tassomai-weekly-goals-image

Kick off

Understanding the problem

To get a full understanding of the current problem, I went through Hotjar to look at comments that users had made relating to this user problem. There were very evidently a lot of issues causing frustration.

Dean-Heasman-Tassomai-Person.png

"It doesn't let me choose between different subjects of which to take a quiz"

"It’s not easy for me to track my progress over homeworks"

"When is my homework is due?"

Dean-Heasman-Tassomai-Hotjar.png

The story behind the story

We also had storyboarding to draw upon for context. I put this storyboard together by going into schools and carrying out interviews and workshops with students to find out about what their typical day looks like. As you can see from a student's day, it's very busy and it's no wonder knowing when their Tassomai homework is due for each subject is tricky.

Dean-Heasman-Tassomai-Story-Boarding.png
Dean-Heasman-Tassomai-Feature-Prioritiza

We had confidence that this feature should be worked on not only from students but also teachers and the rest of the team when I arranged a feature prioritization workshop. Each person was given $300 Tasso-dollars 🙈 . There were eight features to choose from. We were allowed to spend our tasso-dollars on any feature we felt was most "important". Daily & weekly goals across multiple subjects received the most mular.

Know that we are designing the right thing

Working backwards from imperfection

I also carried out an analysis of the current quiz selection screen to further understand the problem.

Dean-Heasman-Tassomai-Screen-Audit-Image

1

XP & Level Bar

There was a lot of information on one screen which compromised the screen real estate going forward if more content was going to be introduced. This issue was compounded by the fact that we didn’t want any vertical scrolling, it was a web app also (includes the status bar) and that, because it is an app for students, 10% of users were using a iPhone 5SE (1136 x 640 pixel resolution).

2

Daily Goal Wheel

There was a lot of information on one screen which compromised the screen real estate going forward if more content was going to be introduced. This issue was compounded by the fact that we didn’t want any vertical scrolling, it was a web app also (includes the status bar) and that, because it is an app for students, 10% of users were using a iPhone 5SE (1136 x 640 pixel resolution).

3

One subject design

There was a lot of information on one screen which compromised the screen real estate going forward if more content was going to be introduced. This issue was compounded by the fact that we didn’t want any vertical scrolling, it was a web app also (includes the status bar) and that, because it is an app for students, 10% of users were using a iPhone 5SE (1136 x 640 pixel resolution).

Framing the solution

Putting pen to paper

Before getting into any designs I outlined some top level user stories to ensure that the solution considered users needs entirely.

• As a user I want to be able to see when my homework is due

• As a user I want to be able to see my correct question completion across individual subjects and across all subjects for today and this week

• As a user I want to be able to see my states for current and past homeworks

To get an abstract view of this feature I sketched out a story board of the student's potential journey.

Dean-Heasman-Tassomai-Story-Board-Sketch

Developing a solution

The monochrome bit

Outlining some features that would be needed:

• The ability to see statistic for homeworks (question accuracy, time spent, daily goals completed)

• The ability to switch between information for today and for the week

• The ability to select different subjects

• The ability to see when homework is due

Dean-Heasman-Tassomai-Lo-Fi-V1.png

V1

This first design explored having the subject and quiz selection on a card. Switching between subjects could be achieved by swiping left and right. As you can see, switching between day and week was placed at the top literally and in terms of hierarchy due to it’s global nature.

The issue with this design is that some users might not know that they can swipe left and right to access other subjects. The second issue is that getting to subjects could mean swiping left and right a few times. With more and more subjects being added in the future, this was not a scalable design. Finally, in this design, there was no indication of progress for a given subject.

Dean-Heasman-Tassomai-Lo-Fi-V2.png

V2

In this second lo-fi design, the date picker allowed for greater granular control - the user can see any date or date range. Once more, the bars for each subject indicate the progress the user is making in each subject.

One of the issues with this design is that firstly the screen is starting to look a little cluttered. Furthermore, what metric should the progress bar represent? Plus, more detail of metrics would be needed so where would this info go? Would it not be better to have a separate screen for metrics? Finally, although the date picker allows for any date/date range, after liaising with the engineering lead and head of product, such a feature would be out of scope cause too many extreme edge cases in the future.

Dean-Heasman-Tassomai-Lo-Fi-V3.png

V3