Simplifying a Complex Search Menu for Genetics Researchers

Project Brief
An internal-use web application for genetics researchers to better understand and visualize complex data sets.
Objective
Redesign the app interface so that it could be used more easily by lab researchers not trained in bio-informatics
Role
UX/UI Design

background

The Center for Spatial and Functional Genomics is a collaborative group at the Children’s Hospital of Philadelphia (CHOP) consisting primarily of Andrew Wells’ lab and Struan Grant’s lab. The center uses next generation sequencing technology to study the 3D configurations of genes and their interactions. Through bio-informatic analysis, the group is able to use these genetic libraries to uncover novel disease related mutations with the long term goal of understanding and treating auto-immune disorders and other conditions.

context

An internal web-app to search through mountains of complex genetic data.

The kinds of assays needed to do this kind of research (ATAC-Seq, RNA-Seq, Hi-C, etc) create a large output of data that becomes very difficult to sort through. While the group has several very talented bio informaticists, it still leaves a lot of data that is under explored and under utilized.  Bio-informatician Chun Su created two different data exploration web applications to enable researchers not trained in bioinformatics to be able to use this data to inform their studies and create figures for their research papers. Over a year after their creation however, the applications were not being used by the staff not trained in bioinformatics as they had intended to be. After Chun left CHOP, the project was handed over to Zachary Thompson, who asked me to help with the redesign.

Problem

Researchers not trained in bio-informatics are underutilizing the app.

Objective

Simplify the interface so all researchers are more likely to use the app.

Research and Analysis

In order to understand what needed to be changed about the app I created a flow chart of the existing processes and I did a heuristic design analysis of the existing interface.  

Additionally, I observed 2 of my non-bioinformatics coworkers using the app. They were getting stuck at the LDLink API Token stage and one of their searches failed because they had the wrong input at the second search type selection input.

In revising this app, it was also important to remember the organization's higher level goal of eventual turning this internal app into a web resource for researchers around the world. Any ambiguous terminology needed to be clearly explained for potential students and researchers less familiar with genomic research.

Revision and Ideation

Many of my recommendations could be achieved simply with the addition of some spacing, consistent typography, and some explainers. The problem that inspired the most design possibilities has problem #1 from my SNP menu analysis. This easily missed radio input was essential to executing a successful search but it was buried all the way at the bottom. During my observations, one of my users missed this button and had to try the search again. It was both very important but also completely redundant, since users make the choice of SNP vs GENE long before reaching the end of the crammed menu.

primary pain point

Switching from the SNP menu to the GENE menu requires correctly responding to a badly placed input at the bottom of a complicated menu.

Solution #1

Separating the two menu options into different pages

  • Gene and SNP menu options are separated into different pages within the menu with a back button to give the user control if they want to start over with the other search option.
  • Removal of the plot and table to make the system status clearer. Results including the containers for them now only appear when the search is complete.
  • Space on right is utilized for an explanation.
Solution #2

Removal of Radio Buttons entirely

  • Minimize clicks by removing the radio button entirely and turning the menu selections into separate buttons
  • Con: cell type is not saved if you want to go back and switch the search type.
Solution #3

Tab Separation

  • Use tabs in the side menu to keep the cell type clearer while making the search type clearer.
  • Con: Still too crowded.
Solution #4

Blue Sky Option: Something Familiar to Researchers

  • Make the most of the space but having search options take up whole of start page and collapse up to top after searching. That way the explanation can take up as much as it needs.
  • More similar to Google or NCBI's BLAST
Final version

Meeting the Developer Where They're at

The developer I worked with on the design for the app was primarily a bioinformaticist with a limited coding skill set in R-studio. While he was enthusiastic about the designs I’d proposed, they didn’t line up clearly with his technical abilities. For the final version as of the last time we worked together, we landed on a compromise design that worked with what he was able to create before ultimately leaving the lab. Presented below is the final version that was passed along to the person taking over the project.

Final Thoughts

As someone who worked in the center on the creation of many genetic libraries, I was often curious about how I could see the fruit of my labor. Making this data accessible to the researchers who work in the center and ideally beyond is the ultimate goal in helping progress of congenital disease research. The product is out of my hands now and hopefully with a developer with greater R-studio capacity and time availability to apply the usability suggestions I prepared.

More case studies

Contact

© Margot Field 2024