BIODEPOT LLC
DURATION
8 Weeks
TOOLs
Figma
Role
UX Designer & Researcher
Methods
Project Overview
BioDePot is a biotech startup from the University of Washington Tacoma developing the BioDepot Nanopore Mobile App in collaboration with the Fred Hutchinson Cancer Center. This bioinformatics tool analyzes Nanopore sequencing data to detect DNA fusions.
I designed an intuitive file management system that addresses scientists' need to efficiently manage hundreds of analysis sessions, with tailored file descriptors, organization, and filtering capabilities.
Design artifacts
Project Background
BioDepot is a biotech startup from the University of Washington Tacoma committed to developing innovative cloud-based solutions for processing complex biological data. In collaboration with the Fred Hutchinson Cancer Center, BioDepot is developing the BioDepot Nanopore Mobile App, a bioinformatics tool that analyzes Nanopore sequencing data to detect DNA fusions, making advanced genomic analysis more accessible to researchers.
How to onboard and contribute in a specialized domain?
Initially, I was concerned about designing without prior knowledge of bioinformatics. To get up to speed, I proactively scheduled meetings with the CEO, CTO, engineers, and designers to review past work and existing documentation. These conversations helped me understand the project's context and identify design opportunities.
DNA Fusion Finder Workflow
Target Audience
Lab Technicians
Bioinformaticians
Conduct advanced computational analysis
Lab Managers
Oversee data generation and processing timelines
Investigators
Create visualizations for grants and publications
Problem Statement
Scientists need an efficient way to help them monitor, manage and navigate through hundreds of DNA sequencing data analysis sessions.
Proposed Solution
An intuitive file management system that conceptualizes each analysis session as a file, providing powerful organization, filtering, sorting, and search capabilities tailored for DNA sequencing data analysis workflows.
How to test design assumptions with real user feedback?
I first developed the concept of a file management system.
While stakeholder discussions and documentation review provided some context, they lacked specific insights into scientists’ potential workflows with the app. I implemented an Agile process with iterative design and testing cycles to validate assumptions.
User Interview
I coordinated interviews with two scientists from Fred Hutchinson Cancer Center who represented different user perspectives. This direct engagement revealed workflow patterns and needs that significantly influenced the interface design.
User Feedback
Design Decisions
Usability Testing
Scenarios
#1 You just finished a week of sequencing runs and need to review your recent work. Navigate to the home screen and locate all sessions from the past week.
#2 You’re starting a new research project and need to organize related sessions together. Create a new project.
#3 You need input from a colleague on a complex sequencing result. Invite them to collaborate on the session and set appropriate permission levels.
#4 You’ve received a new patient sample that requires sequencing as part of your ongoing research. Create a new session for this sample and assign it to your recently created project.
User Feedback
“When I create a new session or folder, I’d like to have a sharing option right away so I can manage who has access.” (P1)
Design Decision
Integrated a sharing and permissions setting directly into the session/folder creation flow.
“Just the email is enough to recognize another user on the ‘Share and Manage Access’ screen, but having their name too would make it clearer.” (P1)
Design Decision
Maintained the display of both name and email address in the sharing interface.
“There should be a ‘Details’ field in the session description for adding workflow information, since the same workflow can be used across different projects. A filter that lets users type in the workflow as free text would make it easier to find relevant sessions.” (P2)
Design Decision
Added a "Workflow" field in the session descriptor to capture workflow information. Implemented a free-text workflow filter to support flexible, cross-project search.
Final Design
Dashboard Overview
Quick access to sort, filter, and search capabilities
Session Management
Session Organization
Customizable folder system to group related work together
Session Creation
Start new analysis sessions with specialized identifiers
Design System
Reflection
This project was challenging due to the requirements for specific domain knowledge. Nonetheless, reviewing prior research and design documentation, as well as early communication with stakeholders, helped build contextual understanding, clarify expectations, and establish trust.
Research was essential to understand scientists' needs and validate design assumptions, which helped identify and prioritize the right features early in the development process. In future iterations, hosting co-design sessions would help reveal hidden needs and ensure stronger alignment with their workflows.
Scientists and clinicians often have limited availability, so flexible scheduling, timely reminders, and follow-ups helped sustain collaboration. A small sample limited the range of insights, and expanding recruitment would improve inclusivity and better reflect diverse requirements.