Galileo Test Finder

 

Duration

4 Months, Ongoing

Project Type

Company’s project

Team

Galileo Team

Description

Galileo is a system based on the platform called ATI (Assessment Technology Incorporated). which is an Imagine Learning product. Product manager, and I were given a project to re-create a page called Test Builder, which was a page to build tests, find tests, schedule tests, and more. Test Builder is now recreated as Test Finder.

My Role

I have led the design process from the beginning to the present time, while interacting with engineers and a product manager daily.

Success Metric

The final product increased search bar click-through by 20% compared to the original version. Furthermore, we received surveys result from 57 individuals providing feedback on the revamped 'Test Finder,' resulting in an outstanding average rating of 5 out of 5.

Final Product

 

User Research

I started this project by identifying existing problems and establishing the goal with the product manager.

The problems were:

  • Users encounter significant difficulty in locating tests due to confusing interaction

  • There are limitations in test discovery, particularly when utilizing filters

  • The page's title does not accurately reflect its intended purpose

The goal was:

How might we make the page more intuitive for users to find tests that they want to find?

This is how the original Test Builder looked like:

Methods

  • Interview

In my research, I interviewed four people from different user levels. Apart from the main problem identified in the beginning, I discovered more detailed issues they faced. This included specific challenges in their interactions and reasons behind survey results and main problem we defined.

  • Survey

The product manager and I created a pop-up guide on the Test Finder page to let users know about a survey. We received 97 responses in total. This helped us identify which buttons and features users liked and used the most, as well as those they used less

  • Secondary Research

I've searched platforms with search and filtering capabilities that filters list formats. Through this exploration, I've identified intuitive features that can enhance the project.

Affinity Mapping

Key Insights

Based on the affinity mapping, I have found several key points that would apply to the project:

  • Convey exactly what Test Builder page is

  • Onboarding system to learn new features

  • Filtering with essential categories

  • Search bar

  • Sort sorting within the list

  • Recent/Past accessed tests history

  • Separate section for Pre-Built and Own-Built Tests for faster search

Ideation

Following numerous discussions with the product manager and developers, I proposed the addition of a left menu bar to the interface. This feature aimed to provide users with quick access to specific test categories without the need for extensive filtering. Identified as high-priority by users, categories like 'All Tests', 'Pre-Built Tests', and 'Own-Built Tests' were prioritized for immediate access.

 

We also thoroughly discussed and organized the content for the menu bar, determined the appropriate categories for the catalog list, and identified features to add or remove based on survey results.

User Persona

As we transitioned to mid-fidelity prototypes, our team focused on defining access limitations for each user level within the new Test Finder page.

UI Design

The color scheme had already been established in the Galileo platform. I adhered to their UI patterns when creating the Test Finder page. Unfortunately, Galileo did not support accessibility features.

Mid-Fidelity Prototype

During the mid-fidelity prototype process, I got to interact with multiple employees ranging from user researcher, product managers, developers, and design managers. I searched out for design patterns across different products for consistency is design system. This was a process where features were added, deleted, re-arranged, and re-created. Several categories in side menus were constantly discussed whether to put them in “More Option” section in the list.

High Fidelity Prototype

This represents the final iteration of the project that has been developed. With this version, I conducted user testing with a total of four users, each representing a different user level. Their reactions were overwhelmingly positive, expressing excitement about using Test Finder in the future. Over the course of two months, the high-fidelity process involved constant iteration, refinement, and collaborative interaction with users, developers, designers, and product managers

Finally…

What could I have done better

  • I would apply accessibility

  • Look into past tickets that has been raised for Test Builders and organize them into google sheet for easy access

  • Develop a comprehensive design system for Galileo to serve as a reference for other designers within Imagine Learning

 Thanks for reading!