Surgo Health
UX research and a proof-of-concept web app that helped Surgo win a major pharmaceutical contract on its move from nonprofit to for-profit.

Surgo Ventures wanted to turn its health data into a commercial product for pharmaceutical research teams. As Lead UI Designer and UX Researcher, I led 20+ user interviews and a market study, then designed a map-first proof-of-concept web app. Surgo presented it to its major clients and won a major contract with a leading global pharmaceutical company.
The challenge
Surgo Ventures, a nonprofit known for its health and social data, wanted to move to a for-profit model. Surgo Health was the product that would make that possible: a platform helping pharmaceutical research teams see where health risks are concentrated across the United States, combining medical conditions with social factors like access to care, environment and socioeconomic status.
Before building the full product, Surgo needed proof that pharma companies would value it. They asked us to run UX research and a market study, then build a proof-of-concept web app they could put in front of their major clients.
The design challenge sat inside that business one: the data was rich but overwhelming, so the POC had to make complex health and social data readable at a glance, without losing the depth experts rely on.
My role
I was the Lead UI Designer and UX Researcher in a four-person team. I led the research and market study, and designed the proof-of-concept web app from first wireframes to final UI, working closely with Surgo throughout the six months.
- 01Planned and ran 20+ user interviews and the market study
- 02Defined role-based information architecture and user flows
- 03Led wireframing, data visualisation and visual design
- 04Ran usability testing and iterated on the findings
- 05Partnered with developers to build the POC web app
How I approached it
Because the work had to persuade both users and buyers, I combined user research with a market study, then turned the findings into a working POC.
20+ interviews and a market study
Personas, affinity mapping, priorities
Role-based IA and user flows
Wireframes, data visualisation, UI
Usability testing, then client demos
What users told us
I interviewed more than 20 public health analysts, healthcare leaders and research professionals to understand how they explore health data and share what they find. Three insights shaped the product:
- 01People think geographically. They wanted to start from a place, then sort and filter by country, state and condition.
- 02Raw data overwhelms; summaries get used. Complex tools slowed analysts down. They wanted summarised results first, with detail on demand.
- 03Insights have to travel. Findings were only useful once shared with stakeholders, ideally filtered by time (weekly, monthly or custom dates).
Market study
Alongside the interviews, I ran a market study to understand where Surgo Health could compete as a commercial product, mapping it against Verato, HolMusk, Clarify and ZeOmega. Most tools were either powerful but hard to read, or simple but shallow. That gap became Surgo’s positioning: expert-level health and social data that anyone on a research team can read.

From insights to priorities
I created two personas from the research. Sarah, a public health analyst in Toronto, is overwhelmed by complex data tools and loses time interpreting results for stakeholders. Charlotte, who leads a Center of Excellence in Ohio, needs to track diseases geographically and turn insights into strategic decisions.


I then ran affinity mapping on feedback from two groups: everyday users and admins. Users asked to view medical conditions, sort by geography and disease, and see summarised results. Admins wanted to spot potential epidemics early, filter by time period, and an accessible, easy-to-read interface. These clusters became the product priorities.

Key decisions
These were the calls that shaped the product most.
Map first, detail on demand
We could open on tables and charts, the way most analytics tools did, or on a map. Because users think geographically, I made a vulnerability map the starting point: pick a score from the left panel, adjust the 0–1 vulnerability slider, and drill down from country to state to county. Hovering a region shows a quick summary, and a demographics panel opens alongside. Trade-off: maps hide exact numbers, so precise views like the clinical trial sites table and Index Explorer charts sit one step away.
Designed around two roles
Analysts and leaders needed very different things from the same data. Rather than one interface for everyone, I designed separate structures: analysts get dashboards, action items and Auto Insights they can accept, reject or group, keeping people in control of automated findings. Leaders get population vulnerability, analytics, alerts and predictive modelling. Trade-off: two structures to maintain, so a shared component system kept them consistent.
A POC built to make the business case
The POC had one job: show Surgo’s clients what the product could do for their research teams. Instead of building every feature thinly, we prioritised the screens that told that story best: the vulnerability map, demographics, state-level insights and clinical trial site planning, which shows disease prevalence, population and distance from existing sites. Trade-off: deeper features like real-time integrations and trend updates were left for the full product, so the POC stayed focused and could be demoed with confidence.
Structure and flows
The information architecture reflects the two roles. The HEPA Analyst works from Home (their dashboards, action items and search), a dashboard library, and Auto Insights. The VP of HEPA works from a Dashboard of population vulnerability and visualisations, an Analytics area for statistical analysis and predictive modelling, and Settings for accounts, data sources and system configuration.

I mapped flows for both the end client and the administrator, including secure sign-in with two-factor authentication, first-time profile and organisation setup, and the admin’s routes to data management, custom reports, real-time analytics and the notification centre.

Design and UI
I started with grayscale wireframes to agree on structure before adding colour: the national map with score filters, a state-level insights summary with city tabs, a clinical trial sites table, and the Index Explorer for charts.

I built a design system so the team could move quickly without the POC looking inconsistent. It uses Libre Franklin for clarity in tables, numbers and small text, a calm palette of deep greens and teals with colour reserved for data, and components built for analytics: KPI cards, map and graph modules, sidebar KPIs, tooltips, ratings and menu buttons. Every chart can be exported or shared, because findings are only useful once they reach stakeholders.
Built on Microsoft's Fluent UI components and design language, customised to the product's brand, so designers and developers worked from the same component foundation and could build faster.
Colour, typography, spacing, radius and elevation defined once as tokens and reused across every component.
Tokens set up as Figma variables, so one change updates every component and screen consistently.
Documented components, states and spacing rules, giving designers and developers one shared reference.

The final product
Every screen follows the same idea: start from a place, see the pattern, then open the detail.



In context
The final screens shown in everyday working settings.


Designed for Sarah and Charlotte
Every POC feature traces back to a pain point from research. Here is how the design answers each persona.
- Complex data tools causing overwhelmMap-first view with detail on demand
- Time-consuming data interpretationHover summaries and Auto Insights
- Inefficient communication to stakeholdersExport and share on every chart
- Needs an intuitive analytics interfaceScore panel and a simple 0–1 vulnerability slider
- Better tracking of diseasesCondition scores mapped down to county level
- Easy geographical medical insightsDrill-down from country to state to city
- Monitoring hospitals and servicesProvider and clinical trial site views
- Insightful software for decisionsAnalytics, alerts and predictive modelling for leaders
The POC focused on the core value: making health vulnerability data readable and shareable. These needs were identified in research and planned for the full product:
- Real-time data integration for analysts, beyond admin-level analytics
- Continuous updates on industry and technology trends
- Market and marketing attribution insights for commercial teams
- Tools to support funding decisions for medical research
Testing and iteration
We ran task-based usability tests on the vulnerability map and demographics panel, using click heatmaps to see where people looked first. 86% of tasks were completed successfully, 84.6% of clicks landed accurately, and the average tester navigated in about 24 seconds.
The weaker number was the path: 70.3% of testers followed the expected route. That told us the map invites exploration, so people reached answers in different ways, and it shaped where we placed shortcuts and the demographics panel.

The outcome
Surgo presented our research and the POC web app to its major clients, and won a major contract with a leading global pharmaceutical company. The project helped Surgo Health prove its commercial value and supported Surgo’s move from a nonprofit to a for-profit model.
What I learned
The biggest lesson was that UX research can be a business asset, not just a design input. Showing Surgo’s clients what real users needed, inside a working app, made the business case far more convincing than a slide deck could.
In data products, the hardest design work is deciding what not to show first. The map only worked because we held back the tables and charts until people asked for them.
Testing also showed that a map invites exploration: success was high, but fewer people followed the expected path than on simpler screens. If I did it again, I’d design for multiple valid routes from the start, with clearer signposts toward the most common tasks.
Finally, with a six-month timeline and two user roles, setting up a shared component system early let us give analysts and leaders different experiences without building two separate products.