This project centered on translating complex genetic sequencing data into something the general public could understand and engage with. The goal was to support a consumer DNA initiative that allowed individuals to submit a DNA sample, receive their results, and explore their ancestral migration story through an interactive digital experience.
The core challenge was not simply building a website. It was designing and engineering a system that could transform raw haplogroup and sequencing data into a meaningful narrative. Users were not scientists. They needed clarity, trust, and a sense of discovery.
At the time, I was serving as CTO at Riser, and my role was to lead the experience and technical execution, working across stakeholders, scientists, designers, and engineers to bring the platform to life.
Understanding the Problem
Much of the scientific groundwork had already been completed. The sequencing methodologies were established, and there was existing data from global indigenous populations. What did not exist was a consumer-facing system that could responsibly present that data in a way that was engaging, accurate, and secure.
I spent signifiant time in direct conversations with the scientific team to understand how the data was structured, what it actually meant, and where simplification was appropriate versus where precision was critical. In parallel, we gathered input from internal stakeholders about expectations for branding, storytelling, and long-term maintainability.
Before we began designing or building, we were provided with extensive research material, scientific documentation, visual assets, and historical context around the broader initiative. As a team, we invested time up front consuming that material so everyone involved understood not just the feature requirements, but the mission and scientific integrity behind the project. That shared context was critical. It aligned design, engineering, and leadership around the same objective rather than fragmenting the work into isolated tasks.
Because this was a novel consumer product at the time, there was no obvious template to follow. We conducted secondary research into interactive educational tools and data visualization experiences to understand what users were already familiar with, then adapted those patterns to a scientific context.
Team Structure and Leadership
At any given time, this initiative involved a team of roughly 8 to 12 contributors, the majority of whom were senior-level designers and engineers. My responsibility was not to execute in isolation but to coordinate, align, and guide that group toward a coherent outcome.
As CTO, managing a team of experienced professionals required clarity more than control. My role was to remove ambiguity, make informed tradeoffs, and ensure the scientific intent, technical feasibility, and user experience remained aligned.
Key Decisions
Several early decisions shaped the outcome of the project.
First, the experience needed to feel immersive. The migration journey was visual and geographic. Static maps were not sufficient. At the time, high-resolution animated maps with smooth transitions required technology that could handle complex vector graphics and interactive states. We selected Flash for the front-end experience, which allowed us to deliver dynamic storytelling layered over detailed historical map assets.
Second, the system had to be secure. Even though the product did not deal with medical diagnoses, it involved personal genetic information. We built the backend on a LAMP stack, aligning with the engineering team’s strengths to ensure stability and maintainability.
Third, we separated the marketing-facing components from the authenticated experience. The public site introduced the product and explained the science at a high level, while the secure login area delivered each user’s individualized migration journey.
Throughout the build, I made a deliberate effort to balance ambition with practicality. Where appropriate, I trained designers to work directly within the interactive layer, allowing backend engineers to focus on architecture and data integrity.
Technical and Organizational Challenges
The most significant technical challenge was data translation. The sequencing outputs were scientifically structured but not optimized for narrative presentation. We had to map raw endpoints into a story framework without distorting the science.
That required me to deepen my own understanding of genetic ancestry models. I spent time independently researching haplogroups, migration theory, and data structures so I could ask better questions and make informed decisions about representation.
Another challenge was scope clarity. In complex, multi-stakeholder environments, it is easy for ideas to evolve midstream. Early in my career, I sometimes moved forward before fully resolving ambiguities. This project reinforced a critical leadership lesson for me: never leave a room without clarity. If something is not fully understood, slow the process down and resolve it before engineering begins.
Looking back, I would prototype faster. We spent longer than necessary in design cycles before testing interaction assumptions. Today, I push for early functional prototypes to eliminate what does not work as quickly as possible.
Those lessons shaped how I lead projects now.
Launch and Handoff
Success for this initiative meant delivering a stable, secure platform that could support kit purchases, account creation, and personalized ancestry exploration. The system was launched, operational, and ready to scale within its intended lifecycle.
The engagement concluded with a structured handoff. The long-term maintenance model was aligned with internal capabilities, and we ensured documentation and architectural clarity so the platform could continue evolving beyond our involvement.
What This Project Taught Me
This project was one of the first large-scale initiatives I led that blended science, storytelling, and engineering. It forced me to operate beyond interface design and into systems thinking.
I learned to:
- Translate highly technical data into usable structures
- Align technical architecture with team strengths rather than idealism
- Ask better questions when complexity is present
- Protect engineering teams from ambiguity by pushing for earlier clarity
- Prototype earlier and test assumptions before over-investing in polish
Most importantly, it reinforced something that still defines how I work: clarity is leadership. When the science is complex, the technology is constrained, and expectations are high, the responsibility is not to move faster. It is to think more clearly.
This project marked an early step in my transition from design-heavy execution into systems-oriented engineering leadership.