The Problem
A next-generation sequencing platform entered development without alignment across hardware, software, bioinformatics, and operations.
This led to:
- Fragmented priorities and conflicting assumptions
- Unclear MVP boundaries
- Poorly defined user needs
- Gaps between lab workflows and digital systems
Left unresolved, this would have resulted in delays, increased cost, and downstream usability issues.
What Was Breaking
The system was not failing technically. It was failing structurally:
- No shared definition of the end-to-end workflow
- No clear connection between lab processes and software systems
- Feature scope expanding without alignment to real user needs
- Cross-functional teams optimizing in isolation
System level approach
Led end-to-end system architecture and workflow definition across assay, automation, software, and data systems.
Key actions:
- Mapped the full workflow from sample to answer
- Defined system architecture across lab, automation, and software
- Established metadata and run planning strategy
- Reframed user needs around real-world workflows
- Aligned cross-functional requirements
- Descoped non-critical features to protect MVP timeline
Outcomes
- Aligned 18+ product-defining architecture decisions
- Defined 16 features to mitigate assay failure and user error
- Descoped 11 non-critical features to reduce cost and complexity
- Established a clear MVP architecture across lab, software, and data systems
- Secured executive phase-gate approval to proceed
Why This Worked
The focus was not on optimizing individual components, but on aligning the system end-to-end early in development. This prevented downstream rework, reduced risk during validation, and ensured the platform was designed for real-world use from the start.