An internal software application currently only allows the analysis of Next-Generation Sequencing (NGS) files. A bioinformatics team wants to add a new Sanger sequencing data pipeline so that users can analyze and visualize both NGS and Sanger sequencing files. For this project, I have used the established company style guide and reiterated the previous application design in order to implement a new feature and enhance the user experience. For privacy and NDA purposes, the name of the company, software and application have been omitted.

Next-Generation Sequencing is an innovative DNA sequencing technology that allows scientists to sequence an entire human genome in one day. Before NGS, scientists have used Sanger sequencing to conduct genomic research by sequencing a single DNA fragment at a time. Biotechnology companies use instruments, such as HiSeq and MiSeq from Illumina, to conduct high throughput sequencing, and create CSV output files that can be analyzed in various ways. Although NGS is now commonly used in genomic research for its high throughput capabilities, Sanger sequencing continues to be used as a cost-effective method for lower sequencing volumes.

The current application only allows the analysis of NGS files in the New Analysis page. In order to implement a new data pipeline and allow the analysis of Sanger sequencing files, it is important to understand the types of output files required. It is also important to identify other pages within the application that can be affected by the implementation of the new Sanger pipeline. This way, creating a userflow shall help identify the MVP that needs to be designed.

With a defined userflow, I started to look at competitor products and conducted an analysis on three heuristics that I wanted to enhance for this design project:

1. User control and freedom
2. Aesthetics and minimalism
3. Recognizing, diagnosing, and recovering from errors

With a userflow and heuristic analysis in place, I started creating wireframes that I could use to discuss with my team. Originally, the section "Pipeline" did not exist. I added the "Pipeline" section so that users could choose the type of sequencing analysis they would like to perform. The wireframes laid the foundation for my mockups that I would be putting through a guerrilla usability testing.

Using my wireframes in combination with the established company colors and style guide, I prepared my mockups for usability testing.

Usability testing was limited to internal users, therefore, I reached out to five prospective users within the company in order to gather feedback on my mockups. 

Major feedbacks:
1. It was helpful highlighting the corresponding sections that needed to be fixed in both the left and right (Validation Summary) panels. 
2. It would be helpful to have a “Help” section or button in the Validation Summary that provides a guide for users about the error and warning messages.
3. Does the left and right panel scroll if there is large number of data inputted?
4. The placement of the three buttons at the bottom can be improved.
5. Users who conduct Sanger sequencing create a CSV export file. The company should also provide a Sanger Sample Sheet so that the application can configure which data points should be analyzed in the Sanger export files.

Keeping the MVP in mind and time constraints, I was only able to frame both the left and right panel so that they can be scrollable when large amount of data are entered.

The MVP was to enable users to analyze both Sanger sequencing and NGS files. Other elements of the application that need to be adjusted in the future involve appropriate edge case messages that appear when insufficient data are uploaded. Messages were defined, but they could be improved with the help of technical writers within the company. The design format that I created could be used to add additional pipelines as needed. Lastly, adding a new data pipeline affects the Analysis List Page that showcase the datasets that a user uploaded into the application. Therefore, I included a new column, "Type", in the Analysis List Page that allowed users to distinguish between analysis file types. 

Other features to be worked on are:
1. Allow column widths to be adjusted in the Analysis List Page.
2. Allow sort functions for specific columns in the Analysis List Page.
3. Adding a "Help" or "Information" button in the Validation Summary for the New Analysis page so that users understand the error or warning messages.
4. Improve the placement of the three buttons at the bottom of the New Analysis page.