Restructuring a Genotype Report for Two Audiences
Reorganized a dense genotype report around the questions its readers ask, with one visual language across the charts.
- Role
- Senior Software Engineer & Creative Team Lead
- Stack
- Vue · Express · Highcharts
- Scope
- Report IA, visual system, and rendering pipeline
- Year
- 2019
Scientifically correct, but hard to read
The report was dense with accurate genomic data, but its structure made it difficult for readers to extract meaning.
Two audiences read the same document (scientists validating results and customers making decisions from them) and the existing structure served neither well.
Accuracy checked at every step
Every value, confidence interval, and marker had to survive the redesign untouched, reviewed by the science team at each step. The report also had to render identically on screen and in print, since printed copies were part of the delivery.
Restructure the narrative without softening the science
I reorganized the report around the questions readers were actually asking, introduced consistent visual encodings for the data, and rebuilt the rendering pipeline so charts and layout stayed precise across output formats.
Every design change was validated against the underlying data to ensure nothing was simplified into inaccuracy.
One visual language for the data
A single encoding system, with consistent color, scale, and annotation rules across every chart, replaced per-chart styling, so readers learn the language once and apply it everywhere. The Vue rendering layer was split from the data layer so the same report definition could drive both the interactive and print versions.
A report both audiences can read
The interactive and print versions are generated from one report definition, so they cannot drift apart. Every value and confidence interval survived the redesign unchanged.
Figures
Screens, diagrams, and documents from the work.