Case · 03
Finding the product underneath the science
Defining the shared product model across a growing set of clinical and research capabilities.
As BrainSightAI expanded, the product risked becoming a collection of individual capabilities organised around disorders, algorithms and customer requests.
I helped define the common product model underneath them.
The problem
The company was working across clinical brain mapping, functional metrics, tract metrics, normative comparison, longitudinal analysis, group research, TMS and DBS-related workflows, and stroke, TBI, dementia and surgical planning.
Each could become its own product. That would create duplicated workflows, inconsistent interaction models and a roadmap driven by the latest scientific capability rather than a coherent user model.
The strategic question
What remains the same across these use cases?
The answer was not a particular disorder or algorithm. It was the user’s need to understand a derived result, compare it with trusted context, adjust how it was inspected and reach a conclusion.
This led to a shared model:
Confirm → Modify → Conclude
How it shaped the portfolio
VoxelBox
A guardrailed clinical product designed for repeatable review, reporting and decision support. The interface needed to limit ambiguity and make the approved workflow clear.
VoxelVault
A more exploratory research product supporting group analysis, longitudinal change, normative comparison and advanced metrics. The interface could expose greater flexibility because the goal was investigation rather than routine clinical reporting.
My contribution
I used this model to connect seemingly separate feature requests, distinguish shared foundations from product-specific workflows, clarify where clinical guardrails were necessary, create a more coherent direction for the viewer, support prioritisation across clinical and research use cases, and give teams a common language for discussing the roadmap.
Why this work matters
Scientific companies often have many valuable capabilities before they have a clear product structure.
Design can help determine which capabilities belong together, which require different levels of freedom and what the user is actually trying to accomplish across them.