JOG.AI

OVERVIEW

MY ROLE

In this project my role included: research & user testing, IA, IxA, content strategy, animation, and prototyping.
Other team members: Amanda Smith & Sara Wingfield

CHALLENGE

JOG.AI is a SaaS that hosts conference calls, and allows seamless, intelligent note taking. Until this point, the product hadn't had a lot of use, but abandonment was already an issue. Our product owner, Sam Gaddis, was looking for an easy onboarding process, so they can begin to scale their product. Our redesign had to be completed in 2.5 weeks. 

TOOLS

• Pen & Paper
• Sketch
• Invision
• Principle

PROCESS

DISCOVERY

WHAT IS JOG?

 There were plenty of amazing features within the site, but it took a few days of evaluative user testing, as well as a lot a of trial and error to discover all affordances. 

INTERVIEWS TO PROTO PERSONAS

I sought to further understand our potential users, and understand the motivation behind both business, meeting participants, as well as people potentially already using transcription services. Using the data from these interviews, we were able to synthesize two proto-personas. Ultimately we opted for the use case of a businessman

APPROACH

Given our time constraint, we decided to iterate as much as possible and started by:

• Tackling visibility of system status.
• Improving signifiers.
• Centralizing information through a dashboard.

DESIGN & ITERATION

A/B TESTING NEW DASH

We began sketching as a team early on, while our best sketcher, Amanda Smith, did the actual drawing. It quickly became clear, that a new dashboard could solve a lot of our problems. 

I charged myself with A/B testing our two mid-res dashboard mock-ups (created by our other Amanda). Interestingly enough, we found a fairly even split between the sexes, with men preferring the design on the left, and women preferring the on on the right. As the distribution didn't hold a majority, we opted to combine the best elements of both into a new dash.

Additionally, we began user testing the key frames from our flow which were created simultaneous to our first two versions of the dash. 

USER TESTING ITERATION 2 PROTOTYPE

Taking key insights from our first round of testing, we redesigned a number of features to better reinforce system status, as well as help eliminate confusion with regards to the product. I created a scripted user test with the options of both mobile or desktop options.

KEY INSIGHTS:
Users still did not understand product, specifically the markers aspect.
Desktop version was unanimous favorite.
Landing page was text heavy but still confusing.

CONTENT STRATEGY

In order to address the main issues of overwhelming text & full understanding of product I:
Removing rhetorical questions to reduce cognitive load.
educing word count
Updated the hierarchy of the content.
Adapting content strategy for markers & conference lines

MARKER EVOLUTION

In the active call page, solving for status indication was really important, based on our testing.. Initially there was no feedback mechanism to know if your markers were placed. After several versions, we ended with the final version you may view in the animation.

TYING IT ALL TOGETHER

By reducing the cognitive load, creating a simpler understanding of the product and its features, as well as centralizing the product through a dashboard, we were able to create our final prototype, along with the remainder of our deliverables. 

RETROSPECTIVE

Overall we were very successful in terms of increasing system status in the onboarding experience. We were able to increase signifiers throughout the targeted flow, allowing the users to navigate seamlessly throughout the site. 

FUTURE FEATURES

• Below is a list of the features which remained in our backlog:
• Local contacts
• Easy “share call” feature
• Schedule calls
• Wizard for 1st time user
• Building and designing statistics